Re: CVS libtoolize uses wrong files

[Ralf Wildenhues]

Hi Bob,

* Bob Friesenhahn wrote on Thu, Dec 29, 2005 at 05:01:18AM CET:
> I configured CVS libtool to use the prefix /usr/local/autotools-devel 
> and autoconf/automake also use that prefix and come first in the PATH. 
> I edited libltdl/Makefile.inc and installed libtool. The file 
> /usr/local/autotools-devel/share/libtool/libltdl/Makefile.inc reflects 
> my changes.  However, the ltdl/Makefile.inc generated by
> 
>   libtoolize --verbose --copy --force --nonrecursive --ltdl=ltdl
> 
> did not include the changes.  So I instrumented 
> func_fixup_Makefile_inc() and discovered that $my_srcdir is 
> /usr/local/share/libtool/libltdl so the wrong (older) files are being 
> used!!!
> 
> I also notice that although as far as I am aware, I have not 
> configured CVS libtool to use the default prefix, but I see that on 
> December 6, the pre-existing content of 
> /usr/local/share/libtool/libltdl was overwritten with newer files 
> (arrgh!).  It is likely that at that time I used Autoconf 2.59 to 
> bootstrap libtool.  I am using CVS autoconf now. Today's files install 
> into /usr/local/autotools-devel/share/libtool/libltdl/.
> 
> What's up with this?

I haven't looked in libtoolize or Makefile.am for looming bugs.  Very
respectfully would I like to suggest that what you are seeing *could*
easily be explained if, on December 6, someone configured and installed
CVS libtool with a (default) prefix of /usr/local, and /usr/local/bin
came earlier in the PATH than /usr/local/autotools-devel/bin.
(Completely independent of Autoconf/Automake versions used.)

Humbly,
Ralf