This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc 3.2's cpp breaks configure scripts
- From: Joe Buck <Joe dot Buck at synopsys dot com>
- To: tilps at hotmail dot com (Gareth Pearce)
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 31 Jul 2002 09:45:39 -0700 (PDT)
- Subject: Re: gcc 3.2's cpp breaks configure scripts
> > cpp is spitting out a warning about changing the search order of include
> > directories, and this is breaking a _ton_ of configure scripts. I found
> > this when I started rebuilding Mandrake with gcc-3.2 branch.
Gareth Pearce writes:
> This, from what little i have seen, seems to be due to the fact that many
> configure scripts segments are extremely overly picky. They take any output
> at all as to mean that its failed. Really it should seem to me that they
> should be looking for errors, or specific warnings rather then just anything
> at all.
Just the same, it's a lot to ask the distributors of GNU/Linux and BSD
systems to fix every configure script in the world.
Maybe a workaround for the time being is to have a gcc option that
suppresses this one warning; people can then write something like
CC="gcc -Wno-check-include-order" ./configure ...
to get around the problem.
However, if this warning appears, it is likely that the programs in
question won't build properly on OSes that ship bad C headers, that have
to be fixed by fixincludes. In that case, it may well be that the gcc
command lines will wind up with something like -I/usr/include which means
that the fixed headers will get bypassed.