AC_TRY_CPP too strict? (Was: grep -E)

[Pavel Roskin]

Hello again!

> However, I'm still curious how this warning (not error) drove the
> configure script into believing that ncurses in not installed at all. I'll
> appreciate if you send me config.log privately.

Sorry, I posted my reply too early. No need to send me anything. It's
obvious from the definition of AC_TRY_CPP that warnings in headers are not
tolerated. This can be reproduced by this configure.in:

AC_INIT
AC_CHECK_HEADERS(ncurses/curses.h)
AC_OUTPUT

$ autoconf
$ CC="gcc -Wundef -I../../../../../usr/include" ./configure
checking how to run the C preprocessor...
   gcc -Wundef -I../../../../../usr/include -E
checking for ncurses/curses.h... no
creating ./config.status

It remains an open question whether Autoconf should be so strict.

Regards,
Pavel Roskin