[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fri, 3 Jul 2009 18:27:59 -0400
KMail/1.11.4 (Linux/2.6.30; KDE/4.2.4; x86_64; ; )
On Friday 03 July 2009 17:53:30 Sam Thursfield wrote:
> Here's something I've not found really discussed anywhere so far,
> which I find kind of surprising. Would you accept a patch which made
> 'autoreconf' honour an 'ACLOCAL_FLAGS' variable?
> I ask because I'm working on jhbuild (GNOME build script tool). Most
> autogen.sh scripts run 'aclocal $ACLOCAL_FLAGS', and so jhbuild sets
> this environment var - using it so autoconf macros that have been
> installed by packages in its sandbox directory are visible to
> subsequent packages it's building.
> Now some autogen.sh scripts are changing to just run 'autoreconf' and
> that breaks this behaviour. I can't see any easily solutions other
> than what I proposed, modifying autoreconf to take an env var
> 'ACLOCAL_FLAGS' into account .. it's great that autogen.sh scripts are
> becoming wrappers around autoreconf (since otherwise, there's no point
> having autoreconf :) but without an easy way of passing the m4 include
> path there's no point. Running 'autoreconf -I
> /home/sam/prefix/share/aclocal' doesn't work by the way, I assume this
> alters the path for some other components.
does setting ACLOCAL_AMFLAGS in Makefile.am not work ? it seems to work in
all my projects.
Description: This is a digitally signed message part.
- ACLOCAL_FLAGS, Sam Thursfield, 2009/07/03
- Re: ACLOCAL_FLAGS,
Mike Frysinger <=