[Top][All Lists]

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

Re: bug#12845: [PATCH] aclocal: tracing AC_CONFIG_MACRO_DIRS can work wi

From: Stefano Lattarini
Subject: Re: bug#12845: [PATCH] aclocal: tracing AC_CONFIG_MACRO_DIRS can work with older autoconf as well
Date: Thu, 15 Nov 2012 14:08:37 +0100

On 11/15/2012 01:53 PM, Eric Blake wrote:
> On 11/15/2012 05:46 AM, Stefano Lattarini wrote:
>>>> * ($ac_config_macro_dirs_fallback): New global variable,
>>>> contains m4 code to issue a fallback definition of AC_CONFIG_MACRO_DIRS
>>>> as an alias for the private macro _AM_CONFIG_MACRO_DIRS.
>>> Tracing a new private macro - doesn't this imply that autoconf needs to
>>> add another macro to its list of preselections in order to pass the
>>> autoconf testsuite when using the new automake?  But don't let that stop
>>> this patch.
>> Well spotted.  But since I'm soon going to remove the private automake
>> macro '_AM_EXTRA_RECURSIVE_TARGETS' as well (the indirection it provides
>> is no longer needed now that aclocal automatically smashes extra
>> whitespace in the arguments of the traced macros), I'd rather wait and
>> make the autoconf update in a single batch.
> Is _AM_EXTRA_RECURSIVE_TARGETS ever traced in any released version of
> automake?
No, that's why I wanted to remove it.

> If so, you can't remove it from the pre-selections, even if
> newer automake no longer traces it.  Basically, the preselections must
> be the union of anything that any released autotool wants to trace.
I was aware of this.  But thanks for spelling it out explicitly anyway.


reply via email to

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