[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: autoreconf 2.52e failure if aclocal need not be run...

From: Akim Demaille
Subject: Re: autoreconf 2.52e failure if aclocal need not be run...
Date: 05 Nov 2001 10:27:14 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Artificial Intelligence)

>>>>> "Ezra" == Ezra Peisach <address@hidden> writes:

Ezra> Here's the deal...  I like your idea - but I am forced into
Ezra> using shell expansion in AC_CONFIG_SUBDIRS. Why may you ask? The
Ezra> tree I am working on needs for the moment to work with autoconf
Ezra> 2.13 and I am pushing for autoconf 2.5X.

Ezra> In 2.5X, AC_CONFIG_SUBDIRS will DTRT if invoked multiple times
Ezra> in conditionals, etc. - which is the clean fashion. In 2.13,
Ezra> AC_CONFIG_SUBDIRS (if memory serves) - affects a global so that
Ezra> code like:

Ezra> a=1 b=2 if $a = 1; AC_CONFIG_SUBDIRS(TEST1234) fi if $b = 1;

Ezra> Always configure is run in TEST1234 TEST456 a b c Using autoconf
Ezra> 2.52 - configure is only run in (in this case) TEST1234, a, b,
Ezra> c.

ISTR that you are right.  I'm sure at least that 2.50 brought cleaner
things in this area.

Ezra> I suppose in my case - I could push the logic of deciding what
Ezra> to compile into the TEST1234 directories, etc - and run
Ezra> configure there anyways.

Ezra> If I wasn't concerned about backwards compatibility it would be
Ezra> easy - but too many developers working on this tree - autoconf
Ezra> 2.13 is the lowest common denominator.

As a matter of fact, I still don't understand well what the problem
is: why isn't your top configure.ac with 2.52?  There is no problem
with configure 2.50 invoking configure 2.13, so I don't understand
your problem.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]