Ralf Wildenhues wrote: > Hmm. "Always use our own libtool" sounds a lot like some bug needed > this. But then again, that line has been in there unchanged for six > years. I wonder if it will break setups if we change this, it's like > a rope to save us from stupid errors rather than a necessity. > > Anybody have good reasons against changing this?
Running the tests in an older libtool.m4 and then using a newer installed
libtool seems like a waste. If we want to do this, then we should probably
skip all of the libtool tests at configure time and print a warning that
LIBTOOL has been overridden in the environment.
That said, Greg can change LIBTOOL at make time to get the same effect with:
$ ./configure
$ make LIBTOOL=/usr/local/bin/libtool
>>--- libtool.m4 2005-03-28 04:32:59.000000000 -0500
>>+++ libtool.m4.new 2005-03-31 16:03:13.000000000 -0500
>>@@ -69,8 +69,9 @@
>> # This can be used to rebuild libtool when needed
>> LIBTOOL_DEPS="$ltmain"
>>
>>-# Always use our own libtool.
>>-LIBTOOL='$(SHELL) $(top_builddir)/libtool'
>>+# Use our own libtool unless the path to one is already specified in
>>+# the environment.
>>+test -z "$LIBTOOL" && LIBTOOL='$(SHELL) $(top_builddir)/libtool'
Something like this? (off the top of my head!)
AC_DEFUN([LT_INIT],
[...
# Allow the user to override libtool invocation
case $LIBTOOL in
# Skip libtool configury if the user specifies an alternate libtool
[[\\/$]* | ?:[[\\/]]*) ;;
*)
LIBTOOL='$(SHELL) $(top_buildir)/libtool'
# Set options
_LT_SET_OPTIONS([$1])dnl
_LT_SETUP
;;
esac
AC_SUBST([LIBTOOL])dnl
# Only expand once:
m4_define([LT_INIT])
])# LT_INIT
Cheers,
Gary.
--
Gary V. Vaughan ())_. [EMAIL PROTECTED],gnu.org}
Research Scientist ( '/ http://tkd.kicks-ass.net
GNU Hacker / )= http://www.gnu.org/software/libtool
Technical Author `(_~)_ http://sources.redhat.com/autobook
signature.asc
Description: OpenPGP digital signature
_______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
