This is the mail archive of the
mailing list for the GCC project.
Re: gcc 3.2's cpp breaks configure scripts
- From: Nix <nix at esperi dot demon dot co dot uk>
- To: Paul Eggert <eggert at twinsun dot com>
- Cc: dave at hiauly1 dot hia dot nrc dot ca, haible at ilog dot fr, bug-gnu-gettext at gnu dot org, gcc at gcc dot gnu dot org, Zack Weinberg <zackw at stanford dot edu>
- Date: 03 Aug 2002 21:36:04 +0100
- Subject: Re: gcc 3.2's cpp breaks configure scripts
- References: <200208021929.g72JTU7Q009491@hiauly1.hia.nrc.ca><200208022142.g72LgWY12317@green.twinsun.com>
On Fri, 2 Aug 2002, Paul Eggert said:
> If GCC warned only when there was a real problem, a lot of these issues
> would go away.
Alternatively, GCC could simply ignore the -I switches that would
trigger those warnings in situations where those warnings are now
emitted. Is there ever any reason you'd *want* GCC to do that
reordering? I can't think of any occasion when I'd want to avoid
fixincluded headers... they have after all been fixincluded for a
reason (and if the fixincluded headers are broken the solution is
to delete the broken ones and fix fixincludes, not to supply
an extra -I/usr/include switch to everything!)
`There's something satisfying about killing JWZ over and over again.'
-- 1i, personal communication