[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gcc 3.2's cpp breaks configure scripts

From: Nix
Subject: Re: gcc 3.2's cpp breaks configure scripts
Date: 03 Aug 2002 21:36:04 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Informed Management (RC1))

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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]