[adding autoconf-archive list, as owner of the AX_CFLAGS_GCC_OPTION macro]
On 08/21/2010 07:52 AM, Ralf Wildenhues wrote:
tags + upstream
thanks
[ http://bugs.debian.org/593838 ]
Hi Jerome,
* Jerome BENOIT wrote on Sat, Aug 21, 2010 at 02:58:28PM CEST:
Version: 2.67-2
AX_CFLAGS_GCC_OPTION(-std=c99)
produces a boggus configure script.
Confirmed with upstream git Autoconf:
cat>configure.ac<<\END
AC_INIT
AX_CFLAGS_GCC_OPTION(-std=c99)
END
aclocal -I /path/to/autoconf-archive/m4
autoconf
./configure
[...]
checking CFLAGS for gcc -std=c99... ./configure: line 2493:
ax_cv_cflags_gcc_option__std_c99=no, unknown: command not found
./configure: line 2516: ax_cv_cflags_gcc_option__std_c99=-std=c99:
command not found
I'm wondering if the AX_CFLAGS_GCC_OPTION macro is at fault here, or if
it is a true regression in autoconf.
Because it appeared that the trouble comes
from the equal (`=`) I guess it is an autoconf
issue: line as
AX_CFLAGS_GCC_OPTION(-Wno-unused-function)
works well.
Note that with the previous version of autoconf (2.65-4) everything
was fine. As a matter of fact, I suspect that the issue may be
related to bug #593546 , but I can not confirm this part of the story.
Related yes, but #593546 is about '*' and this is about '='.
I think it is obvious that something changed so that
AX_CFLAGS_GCC_OPTION is no longer transliterating = into _ when creating
the cache variable name. But I don't know where the fault lies without
seeing the implementation of this macro.