[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
libtool.m4 option to use installed libtool
From: |
Greg Hudson |
Subject: |
libtool.m4 option to use installed libtool |
Date: |
Thu, 31 Mar 2005 16:56:51 -0500 |
Periodically, I face situations like this: libtool fails in some
situation on a new operating system. The problem is already fixed
upstream or can be fixed easily, but most of the packages I build are
packaged with an old version. Recent examples include the DESTDIR bug
with relinking in 1.4.x and the Solaris 10 issues with convenience
libraries and "-z defaultextract".
In such situations, I think my current options are to:
1. Hack ltmain.sh or aclocal.m4 in all the affected packages.
2. Install a fixed libtool and build with "make LIBTOOL=libtool".
Option 2 isn't so bad, but it would be somewhat more convenient for me
if I could specify the path to libtool in config.site or in the
configure environment. I've included a candidate patch.
(Sorry if this comes up a lot. I couldn't find an easy way to search
the mail archive, and browsing it is hard since it's full of spam.)
--- 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'
AC_SUBST(LIBTOOL)dnl
# Set options
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- libtool.m4 option to use installed libtool,
Greg Hudson <=