Am 05.02.2018 um 18:17 schrieb aotto:
Am 05.02.2018 um 15:17 schrieb Eric Blake:
On 02/04/2018 04:58 PM, aotto wrote:
the following line create a BUG in autoconf
# if 'CFLAGS' is NOT set, than macro 'AC_PROG_CC' set 'CFLAGS=-g -O2'
in seems that a M4-MACRO in COMMENT is a problem.
# if 'CFLAGS' is NOT set, than macro 'AC_PROG_CC' set 'CFLAGS=-g -O2'
CFLAGS="-Wall -Wcast-align"
CXXFLAGS=""
#> autoconf
configure.ac:79: error: possibly undefined macro: AC_PROG_CC
If this token and others are legitimate, please use
m4_pattern_allow.
See the Autoconf documentation.
You are correct that autoconf's detection of unexpanded macros is
unaware of comment syntax. Would you like to prepare a patch to the
post-processing pass that looks for unexpanded macros to first filter
out all comment lines?
the problem is not only the comment… today I had a "string" with
macroname inside in the file
acinclude.m4… and "aclocal --force -I m4" run "forever" and eat all my
memory… example:
AC_DEFUN([SC_ENABLE_DEBUG], [
AS_IF([test "x$config_site" = "xyes"], [
AC_MSG_NOTICE(["ENABLE_DEBUG: using 'config.site' defaults"])
…
if you switch ENABLE_DEBUG to SC_ENABLE_DEBUG… then you have a really
BIG problem… :-)
mfg AO
