bug#13514: [PATCH v2 0/0] AC_CONFIG_MACRO_DIR && non-existent directory

[Pavel Raiskup]

>> Yes, but not if they don't want (or don't necessarily need) to switch
>> macros into different directory than 'm4'?
>
> There might be a misunderstanding here (either from your part, or in
> my understanding of what you are saying).  Are you aware that none of
> the autotools use *any* local m4 directory if it is not explicitly
> instructed to, right?  So there is not "default local m4 directory".
> The 'AC_CONFIG_MACRO_DIR' and 'AC_CONFIG_MACRO_DIRS' macros are not
> used to switch to an alternate name for the local m4 directory, but
> to declare such directory (or directories).
>
>> This is somehow complicated
>> and inconsistent behavior among autotools :( and I'm still not sure what
>> should I suggest to package maintainers which are dependant on autotools
>> for that issue.
>>
>> Should we suggest in general something like this?
>>
>>   configure.ac: AC_CONFIG_MACRO_DIR([*Whatever*])
>>   Makefile.am:  ACLOCAL_AMFLAGS = -I *Whatever*
>>   # but *Whatever* must be the same on both lines
>
> I'd suggest them to either:
>
>  - use AC_CONFIG_MACRO_DIRS if they can/want require cutting-edge
>    versions of the autotools;
>
>  - use ACLOCAL_AMFLAGS otherwise, for the time being (until the
>    now-cutting-edge autotools version have become widespread and
>    "old" enough).
>
> Also notice that proper support for AC_CONFIG_MACRO_DIRS will only
> be present from the *next* versions of autoconf and libtool (2.70
> and 2.6 respectively I think); it is not yet available with the
> current one (2.69 and 2.4.2, respectively).

Aha, ACLOCAL_AMFLAGS is not going to be removed so early :).  All my
previous calls misunderstandings was built on top of this. :)  so it is OK
for me now.

Thanks for your suggestions!  It is clear to me now.

Pavel