Re: AC_BEFORE does not warn when it should

[Gary V. Vaughan]

Hi Bruno,

On 1 Jun 2010, at 17:04, Bruno Haible wrote:
>> If so, then you have the arguments reversed in the second case.
> 
> Oh, I added the AC_BEFORE invocation in the second place only after I got
> no warning from the AC_BEFORE invocation in the first place.

Ah, okay. I had wondered why your example didn't reflect the contents
of gnulib in git master...

>> The idiom I always use to avoid confusing the argument order is this:
>> 
>> AC_BEFORE([$0], [warn-if-this-macro-name-was-already-called])
> 
> This is what I started with: A definition of gl_LIBUNISTRING
> that starts with
> 
>  AC_BEFORE([$0], [gl_LIBUNISTRING_LIB_PREPARE])
>  # XXX gl_LIBUNISTRING starts here
> 
> and a definition of gl_LIBUNISTRING_LIB_PREPARE that starts with
> 
>  # XXX gl_LIBUNISTRING_LIB_PREPARE starts here
> 
> This produced the same effects: an output order that violates the constraint,
> and no warning from autoconf.

Agreed. I can reproduce this with gnulib git master. Unfortunately, even
with the generous commenting of m4_require in autoconf's m4sugar.m4, I
can't figure out why it's happening :(

IIRC Akim wrote the original implementation, and maybe has time to help...

Cheers,
-- 
Gary V. Vaughan (address@hidden)