Re: autoconf 2.63b: wrong macro expansion order

[Andreas Schwab]

Eric Blake <address@hidden> writes:

> I'm looking into it now.  So you changed the two lines:
>
> m4_expand_once([_AC_COMPILER_EXEEXT])[]dnl
> m4_expand_once([_AC_COMPILER_OBJEXT])[]dnl
>
> in AC_PROG_CC and things improved?  Did you just delete the m4_expand_once
> and do a direct call to those two macros,

Yes.  Of course, the warning will remain and everything is duplicated.
But autoconf 2.63 did the right thing here.

> or did you delete the entire line?
>
> Meanwhile, does it fix things to change the definition of BAR to be:
>
> AC_DEFUN([BAR], [AC_REQUIRE([AC_PROG_CC])
> FOO])

It does fix this case, but would not be an option for the original test
case, where additional text is expected to be emitted before the
expansion of AC_PROG_CC.  This was extracted from the KDE3 autoconf
macros (with BAR == AC_CHECK_COMPILERS and FOO ==
KDE_CHECK_FOR_BAD_COMPILER).

Andreas.

-- 
Andreas Schwab, address@hidden
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."