This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: New cpp0 warning in 3.1 breaks configure (autoconf)
- From: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
- To: gcc at gcc dot gnu dot org
- Cc: neil at daikokuya dot demon dot co dot uk
- Date: Tue, 11 Jun 2002 17:13:51 -0500 (CDT)
- Subject: Re: New cpp0 warning in 3.1 breaks configure (autoconf)
- Organization: Networks and Infrastructure Lab (IL02/2240), Motorola Labs
- References: <20020606204404.GA17526@bort.dtek.chalmers.se>
In article <20020610060256.GA3949@daikokuya.demon.co.uk> you write:
>> > Why is it on by default?
>> Nobody knows.
> Since this appears to be causing pain to many people, and no-one seems
> to be willing to defend the warning when people ask about it on the
> mailing lists, I suggest this is the best course of action for the
> mainline source too.
Well, I was a day late but I attempted to defend it over in gcc-bugs
before I saw this gcc list traffic.
I think the current behavior is worth defending since skipping fixed
system headers can cause serve cascading problems that are hard to
debug by the user.
The warning be improved to only report when a wrong header was
actually found due to the user-provided change to the search path.
However, I don't know if "randomly" kicking in (depending on exact
port and system header, etc) is better than an absolute warning.
Regards,
Loren
--
Loren J. Rittle
Senior Staff Software Engineer, Distributed Object Technology Lab
Networks and Infrastructure Research Lab (IL02/2240), Motorola Labs
rittle@rsch.comm.mot.com, KeyID: 2048/ADCE34A5, FDC0292446937F2A240BC07D42763672