It seems that we need to be prepared for /usr/local/share/libtool directories which are infected with files from older versions. On my FreeBSD system, there is a ltconfig file dated "Jan 3 2003". That means that it must have been delivered with the OS (FreeBSD 5.0).
It is possible that Automake still looks for ltconfig to determine how it should handle libtool.
Bob
On Thu, 16 Oct 2003, Bob Friesenhahn wrote:
Huh?
With the very latest CVS libtool:
% libtoolize --copy --force --verbose libtoolize: copying file `./ltconfig' <---???? libtoolize: copying file `./config.guess' libtoolize: copying file `./config.sub' libtoolize: copying file `./ltmain.sh' libtoolize: copying file `./libtool.m4' libtoolize: copying file `./ltdl.m4'
I thought that ltconfig was a dead duck.
It is. I guess we need to change the installation to clean up the $prefix/share/libtool directory before installing over the top of an ancient directory. Especially since the new libtoolize copies whatever it finds in that directory.
Also, the files libtool.m4 & ltdl.m4 are now copied.
Yes, that is deliberate. Autopoint installs its macros, and consistency is a good thing. Also, aclocal 1.8 (i.e. CVS HEAD) puts m4_include([m4/libtool.m4]) into aclocal.m4 instead of copying the whole file if it can find it in the source tree. This helps reduce the distribution size if more than 1 aclocal is used... before my patch we had to copy it to acinclude.m4 to make sure the installed libtool.m4 wasn't copied by mistake, aclocal would copy it again into aclocal.m4 and then it was expanded into configure -- so we used have 31 copies of that huge file. Now we have 11.
Cheers,
Gary.
--
())_. Gary V. Vaughan gary@(lilith.warpmail.net|gnu.org)
( '/ Research Scientist http://www.oranda.demon.co.uk ,_())____
/ )= GNU Hacker http://www.gnu.org/software/libtool \' `&
`(_~)_ Tech' Author http://sources.redhat.com/autobook =`---d__/_______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
