>>>>> "Martin" == Martin Buchholz <[EMAIL PROTECTED]> writes:
Martin> Notice that AC_DEFINE seems to get undefined because of its
Martin> appearance in a _comment_ in AC_OUTPUT. Bizarre!
No, you are abused by the error message. The message is triggered
because autoconf.sh saw something which looks very much like a macro
in configure (the output), via an egrep A[CHM]_. And then it reports
to you what it saw pretending it was undefined. This example will
make it clear to you:
/tmp % echo "AC_INIT\n[AC_INIT]" > configure.in nostromo 9:20
/tmp % autoconf nostromo 9:21
autoconf: Undefined macros:
configure.in:1:AC_INIT
configure.in:2:[AC_INIT]
You'll also note it thinks the first occurrence is undefined, which is
dead wrong, it has been expanded. But when it browsed configure for
unexpanded macros, it found AC_INIT, since the user does not care
where AC_INIT appears in the output, but wants to know where it
appeared in the input, it grepped AC_INIT in configure.in, hence the
message you read.
In your case, since the arguments of AC_OUTPUT were quoted, the
unexpanded macro name triggered the problem.
I'll look into the details of your bug report, thanks.
Akim
