On Tue, Feb 24, 2009 at 2:28 PM, Adam Williamson <awilliam@xxxxxxxxxx> wrote: > > Oh, and thanks to Dan for reminding me that using 'autoreconf -i' is the > best way to do it. Some of the tools fail by default if certain > 'required' files are missing. autoreconf -i just creates any missing > files automatically. No problem. The issue that showed when libtool-2.2 was being introduced is that running bare autoreconf will not run libtoolize since it will "install" files into the source directory. autoreconf thinks you don't want to do that unless you specify -i|--install. This, of course, breaks hard since the libtool m4 macros have been replaced, but the libtool script has not. I'm going to attempt upstreamable patches for autoreconf and libtoolize to at least error in that situation, but I haven't had much luck with the autotools people yet. -- Dan -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
