This is the mail archive of the
mailing list for the GCC project.
Re: gcc 3.2's cpp breaks configure scripts
- From: Neil Booth <neil at daikokuya dot co dot uk>
- To: Phil Edwards <phil at jaj dot com>
- Cc: Joe Buck <Joe dot Buck at synopsys dot com>, Gareth Pearce <tilps at hotmail dot com>,gcc at gcc dot gnu dot org
- Date: Thu, 1 Aug 2002 19:13:39 +0100
- Subject: Re: gcc 3.2's cpp breaks configure scripts
- References: <OE18Cys8qXKypji8il50000ca65@hotmail.com> <200207311645.JAA25032@atrus.synopsys.com> <20020801133156.A17847@disaster.basement.lan>
Phil Edwards wrote:-
> On Wed, Jul 31, 2002 at 09:45:39AM -0700, Joe Buck wrote:
> > 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.
> Yes, please. I'm very annoyed that GCC prints warnings that I cannot disable
> when I /know/ that they are false or harmless.
> I'm wrestling with my development machine at the moment (sysadmin issues),
> but once it is working again, I will work up such a patch if there is a
> consensus that it would be worthwhile. (And if we can agree on option
Please, not more switches. Let's either fix the warning, agree its
correct, or get rid of it.