[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libtool 2.2.6a unnecessary AC_CONFIG_M4_DIR warning?
From: |
Ralf Wildenhues |
Subject: |
Re: libtool 2.2.6a unnecessary AC_CONFIG_M4_DIR warning? |
Date: |
Mon, 29 Sep 2008 08:32:56 +0200 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
Hi Simon,
* Simon Josefsson wrote on Fri, Sep 26, 2008 at 10:35:50AM CEST:
> libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
> libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
>
> I can't seem to find any difference between using that in configure.ac
> or not, all the same *.m4 files are distributed in m4/.
For 'libtoolize --install', it makes a difference IIRC.
> Note that I have in Makefile.am:
>
> ACLOCAL_AMFLAGS = -I m4 -I gl/m4 -I lib/gl/m4
>
> I recall that some tools already assume the first -I<dir> in
> ACLOCAL_AMFLAGS is the place to put more *.m4 files, so can't libtool
> make this assumption too?
aclocal does this. But we were trying to move away from this rather
arbitrary semantics, esp. as it makes things like this harder:
env ACLOCAL='aclocal -I ...' autoreconf -vi
> I'm trying to avoid having to maintain redundant configuration
> statements in my packages, so fixing this would help with that.
But in that light it's not really a redundant information.
Hope that helps.
Cheers,
Ralf