From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26424 invoked by alias); 1 Aug 2002 07:15:41 -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 26417 invoked from network); 1 Aug 2002 07:15:40 -0000 Received: from unknown (HELO hotmail.com) (216.33.236.128) by sources.redhat.com with SMTP; 1 Aug 2002 07:15:40 -0000 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 1 Aug 2002 00:15:40 -0700 Received: from 129.78.64.17 by lw7fd.law7.hotmail.msn.com with HTTP; Thu, 01 Aug 2002 07:15:39 GMT X-Originating-IP: [129.78.64.17] From: "Gareth Pearce" To: gcc@gcc.gnu.org Bcc: Subject: Re: gcc 3.2's cpp breaks configure scripts Date: Thu, 01 Aug 2002 00:15:00 -0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 01 Aug 2002 07:15:40.0276 (UTC) FILETIME=[3DC91340:01C2392B] X-SW-Source: 2002-08/txt/msg00002.txt.bz2 > >On Thu, Aug 01, 2002 at 07:03:43AM +0000, Gareth Pearce wrote: > > but only with files which are fixincluded right? (not rhetorical) > >This has nothing to do with fixinclude. #include_next is used e.g. >to include gcc's include header of the same name, or by libstdc++-v3 >headers to include C headers, etc. >Also, -I/usr/include changes the status of /usr/include headers from >system headers to user headers, thus you may get warnings (or errors >with -Werror) where you otherwise would not get any. Hmmm I think the lights starting to seep into my brain... But just to be sure, your saying that adding -I/usr/include (or similar) can cause libstdc++ headers to break due to the way they use #include_next? If so then I guess its the rough road or no road...(too many special cases for my liking) hmmm time to bug someone else then I guess :) Gareth _________________________________________________________________ Join the world’s largest e-mail service with MSN Hotmail. http://www.hotmail.com