When "older" version of autoconf are used (that is, those before commit
v2.69-44-g1ed0548), we have no sane way to prevent the autom4te invocation
issued from aclocal to possibly display warnings "MACRO m4_require'd but
not m4_defun'd". That's not a big deal, because that just means that
people us
On 11/15/2012 06:08 AM, Stefano Lattarini wrote:
>> 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
On 11/15/2012 02:13 PM, Eric Blake wrote:
> On 11/15/2012 06:08 AM, Stefano Lattarini wrote:
>>> Is _AM_EXTRA_RECURSIVE_TARGETS ever traced in any released version of
>>> automake?
>>>
>> No, that's why I wanted to remove it.
>>
More importantly, we'll have to start pre-selecting the
'AM_EXTRA_RECU
On 11/15/2012 01:53 PM, Eric Blake wrote:
> On 11/15/2012 05:46 AM, Stefano Lattarini wrote:
>
* aclocal.in ($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_MAC
On 11/15/2012 05:46 AM, Stefano Lattarini wrote:
>>> * aclocal.in ($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 - does
On 11/15/2012 01:00 PM, Eric Blake wrote:
> On 11/15/2012 03:58 AM, Stefano Lattarini wrote:
>>> As soon as you AC_PREREQ([2.70]), then yes, you can quit tracing
>>> AC_CONFIG_MACRO_DIR.
>>>
>> The below patch should allow our users to employ AC_CONFIG_MACRO_DIRS
>> with autoconf 2.69 as well. It
Hi Eric, thanks for the quick feedback.
First of all, I've noticed this squash-in is necessary to avoid a spurious
testsuite failure:
diff --git a/t/aclocal-acdir.sh b/t/aclocal-acdir.sh
index 59182bb..944604b 100755
--- a/t/aclocal-acdir.sh
+++ b/t/aclocal-acdir.sh
@@ -21,6 +21,9 @@
On 11/15/2012 03:58 AM, Stefano Lattarini wrote:
>> As soon as you AC_PREREQ([2.70]), then yes, you can quit tracing
>> AC_CONFIG_MACRO_DIR.
>>
> The below patch should allow our users to employ AC_CONFIG_MACRO_DIRS
> with autoconf 2.69 as well. It still doesn't work with autoconf 2.68
> and earli
On 11/15/2012 04:52 AM, Stefano Lattarini wrote:
> On 11/15/2012 11:58 AM, Stefano Lattarini wrote:
>>
>> The below patch should allow our users to employ AC_CONFIG_MACRO_DIRS
>> with autoconf 2.69 as well. It still doesn't work with autoconf 2.68
>> and earlier though, due to a bug in autom4te op
On 11/15/2012 11:58 AM, Stefano Lattarini wrote:
>
> The below patch should allow our users to employ AC_CONFIG_MACRO_DIRS
> with autoconf 2.69 as well. It still doesn't work with autoconf 2.68
> and earlier though, due to a bug in autom4te option parsing (fixed by
> autoconf commit v2.68-120-gf4b
[+cc automake-patches]
On 11/14/2012 03:50 PM, Eric Blake wrote:
> On 11/14/2012 07:41 AM, Stefano Lattarini wrote:
>>> If I understand your argument correctly, you are claiming that
>>> AC_CONFIG_MACRO_DIR should _not_ trace into AC_CONFIG_MACRO_DIR_TRACE,
>>> so that case (2) can be distinguishe
11 matches
Mail list logo
