Justin Erenkrantz <jerenkrantz_at_apache.org> writes:
> 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
>
> Index: configure.ac
> ===================================================================
> --- 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"
> -sh_libtool="`$apr_config --apr-libtool`"
> +AC_ARG_WITH(custom-libtool,
> +AS_HELP_STRING([--with-custom-libtool=PATH],
> + [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`" ])
> LIBTOOL="$sh_libtool"
> SVN_LIBTOOL="$sh_libtool"
> AC_SUBST(SVN_LIBTOOL)
If it were that simple I would not be complaining, I would have made a
similar change. The problem is that I don't have a suitable libtool
script to use. The libtool script that I want to use is the one that
was created by the "muckin' around" and that script no longer gets
created. The generic /usr/bin/libtool isn't the same as the script
that used to be created.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1250141
Received on 2009-03-01 13:26:54 CET