On Fri, Feb 27, 2009 at 1:30 PM, Philip Martin <philip_at_codematters.co.uk> wrote:
> It's a compromise. It creates a libtool file in the build dir but you
> don't have to use it--make will invoke apr's libtool. You get to use
> apr's libtool, I get to use my system's libtool.
As I said, I think a configure option that lets you specify the path
to libtool would make it easier - IOW, the patch below.
If we go and build a custom libtool thru autoconf, then we have to
drag in all of the clumsy code to deal with different libtool
versions. And, we'll be yet again forced to hop on the maddening
libtool train when there is no real need to do so.
I don't know why you think you *need* the autoconf-fu in order to use
GNU libtool. If you installed GNU libtool 2.x yourself, there is a
glibtool or libtool or whatever binary already there - just point to
it. The muckin' with GNU libtool at configure-time has always been
unnecessary. -- justin
--- configure.ac (revision 36180)
+++ configure.ac (working copy)
@@ -168,8 +168,13 @@
[Defined to be the path to the installed locale dirs])
dnl Check for libtool -- we'll definitely need it for all our shared libs!
-echo "using APR's libtool"
+ [Specify the command to run libtool]),
+ [ AC_MSG_NOTICE([using $withval as libtool])
+ sh_libtool="$withval" ],
+ [ AC_MSG_NOTICE([using APR's libtool])
+ sh_libtool="`$apr_config --apr-libtool`" ])
Received on 2009-02-27 23:55:39 CET