> Be aware that this message is definitely the sign that something is
> going wrong. If I were you, I'd restore the dnl, and would look for
> it in `configure' itself. It means that somewhere you were relying on
> the broken quotation of 2.13, or maybe that it is 2.50, trying to fix
> these issues, that broke you source.
In my configure.in file, I was doing:
dnl Check for ANSI C exit success/failure values.
AC_EGREP_CPP(yes, [dnl
#include <stdlib.h>
#ifdef EXIT_SUCCESS
yes
#endif], AC_DEFINE(HAVE_EXIT_SUCCESS))
and the resulting output in 2.13 was:
cat > conftest.$ac_ext <<EOF
#line 5424 "configure"
#include "confdefs.h"
dnl
#include <stdlib.h>
#ifdef EXIT_SUCCESS
yes
#endif
EOF
if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
egrep "yes" >/dev/null 2>&1; then
rm -rf conftest*
cat >> confdefs.h <<\EOF
#define HAVE_EXIT_SUCCESS 1
EOF
the output is different, but still contains a dnl, in 2.50:
# Check for ANSI C exit success/failure values.
cat >conftest.$ac_ext <<_ACEOF
#line 7556 "configure"
#include "confdefs.h"
dnl
#include <stdlib.h>
#ifdef EXIT_SUCCESS
yes
#endif
_ACEOF
if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
egrep "yes" >/dev/null 2>&1; then
cat >>confdefs.h <<\EOF
#define HAVE_EXIT_SUCCESS 1
EOF
--keith
