From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14083 invoked by alias); 11 Jun 2002 23:11:57 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 14076 invoked from network); 11 Jun 2002 23:11:56 -0000 Received: from unknown (HELO disaster.jaj.com) (66.93.20.253) by sources.redhat.com with SMTP; 11 Jun 2002 23:11:56 -0000 Received: (from phil@localhost) by disaster.jaj.com (8.11.4/8.11.4) id g5BNBmh24720; Tue, 11 Jun 2002 18:11:48 -0500 Date: Tue, 11 Jun 2002 16:25:00 -0000 From: Phil Edwards To: Alexandre Oliva Cc: Marc Espie , gcc@gcc.gnu.org Subject: Re: New cpp0 warning in 3.1 breaks configure (autoconf) Message-ID: <20020611191148.A24620@disaster.basement.lan> References: <20020606204404.GA17526@bort.dtek.chalmers.se> <200206112233.g5BMXmM30365@quatramaran.ens.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from aoliva@redhat.com on Tue, Jun 11, 2002 at 07:58:54PM -0300 X-SW-Source: 2002-06/txt/msg00750.txt.bz2 On Tue, Jun 11, 2002 at 07:58:54PM -0300, Alexandre Oliva wrote: > On Jun 11, 2002, Marc Espie wrote: > > In article <200206112213.g5BMDp3L044244@latour.rsch.comm.mot.com> you write: > >> 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. > > > Of course, this does assume the compiler and fixincludes are always right. > > -I/usr/include is always wrong. -isystem /usr/include might be > acceptable. Let me throw out an idea: Ignore -I/usr/include. Silently, even. Warn only if -Wfoo is given (for whatever value of foo). More generally, ignore -I's of STANDARD_INCLUDE_DIR ("/usr/include" by default). Or maybe, anything in the cpp_include_defaults array. Give a diagnostic only if the user asks for one, because otherwise there is nothing the user can do about it. We can recover from parsing errors and continue. Why can't we recover from command-line user errors and continue? Phil -- If ye love wealth greater than liberty, the tranquility of servitude greater than the animating contest for freedom, go home and leave us in peace. We seek not your counsel, nor your arms. Crouch down and lick the hand that feeds you; and may posterity forget that ye were our countrymen. - Samuel Adams