apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Orton <...@manyfish.co.uk>
Subject Re: [PATCH] Make buildconf's libtool.m4 detection more robust
Date Thu, 08 Jan 2004 20:40:51 GMT

On Mon, Jan 05, 2004 at 02:54:34AM -0800, Noah Misch wrote:
> I'm building APR CVS HEAD on a recent (no more than three months old) Cygwin
> binary installation.  buildconf fails to find libtool.m4 because
> /usr/bin/libtoolize is actually a shell script that applies some heuristics to
> choose between /usr/autotool/{devel,stable}/bin/libtoolize.
> One can get around this by setting LIBTOOL_M4, of course, but I think this patch
> obviates that need and introduces a better general solution besides.  It parses
> the output from libtoolize, which includes the directory of libtool.m4, and uses
> that.  If this fails (such as if, for example, the output format of libtool
> varies too much), buildconf will fall back on its previous mechanism.

That's pretty ugly... I'm more inclined to say: if you have a really
weird libtool installation, set LIBTOOL_M4.  libtoolize
--where-is-libtool-m4 sounds good :)

> Long-term, maybe I'll ask the libtool people to add a --m4 option that prints
> that directory so scripts like this one can find libtool.m4 without relying on
> fragile transformations like this one.



View raw message