Re: [PATCH 0/2] AC_CONFIG_MACRO_DIRS: implementation and documentation

[Stefano Lattarini]

On 11/02/2012 06:34 PM, Stefano Lattarini wrote:
> On 11/02/2012 02:36 PM, Nick Bowler wrote:
>> On 2012-11-02 10:46 +0100, Stefano Lattarini wrote:
>>> On 10/23/2012 12:59 AM, Nick Bowler wrote:
>>>> 4) I get a bunch of new warnings from aclocal, of the form:
>>>>
>>>>      configure.ac:42: warning: DX_EXPORTED_SH is m4_require'd but not 
>>>> m4_defun'd
>>>>
>>>>    The invocation comes from an AC_REQUIRE([DX_EXPORTED_SH]) and the
>>>>    DX_EXPORTED_SH macro is expected to be picked up by aclocal -- it is,
>>>>    and things seem to work in the end, but the warnings are annoying
>>>>    (and are printed multiple times).
>>>
>>> And you say they weren't there before these series?  Or is this regression
>>> already present in master?  I'll investigate.
>>
>> It wasn't there before changing the package to use AC_CONFIG_MACRO_DIRS
>> instead of ACLOCAL_AMFLAGS.
>>
>> In previous versions of Automake these same warnings will show up when
>> invoking aclocal without any -I options.  In this case, not passing
>> those arguments would be an error, and the resulting configure sript
>> would probably not work since aclocal can't find the macros in question.
>>
>> But now, aclocal is being called with no -I options intentionally, and
>> it is actually finding the macros (and producing working configure
>> scripts), but these warnings are still being printed.  Adding the -I
>> options again makes the warnings go away.
>>
> OK, I've exposed this issue with the patch below.  Let's see if I'll
> manage to fix it as quickly as the other one...
> 
> [SNIP PATCH]
>
Well, it turns out that such warnings are coming from the autom4te
invocation, so I see no simple, non-hacky way to avoid them, unless
we add a knob to autom4te itself.

So, autoconfers: would be OK with you to add a new warning "category"
to autom4te that would suppress *only* this specific warning?
The warning in question being

    AC_FOO is m4_require'd but not m4_defun'd

that is emitted by the '_m4_require_call' internal macro (defined in
'lib/m4sugar/m4sugar.m4').

Thanks,
  Stefano