Hello, Mathieu!

> I have tried the same code with egcs-2.91.66 and the errors (GCC_* and
> families missing) are not reported. So the problem come from gcc. gcc -v
> reports: 2.96 20000724 (experimental). Oops, I didn't see the experimental
> thing... The difference is in the -Wundef flag given to the preprocessor
> (gcc -E). Without it, the results are the same between the two gcc. The
> strange thing, is that the gcc info page tells:
> `-Wundef'
>      Warn if an undefined identifier is evaluated in an `#if' directive.

My guess is that the experimental version of GCC you are using is less
forgiving to the system headers, at least on the open-source systems.

gcc-2.95.2 and the older versions would not apply -Wundef to the system
headers.

This essentially means that if you want to picky to the code you are
writing or testing (using GRUB from CVS implies testing it) and you are
using GNU/Linux (I hope that GCC is more forgiving on commercial Unices)
you should also be picky to the headers installed on your system, i.e.
report the problem to the ncurses maintainers.

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.

Regards,
Pavel Roskin

Reply via email to