From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24253 invoked by alias); 1 Aug 2002 23:54:40 -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 24246 invoked from network); 1 Aug 2002 23:54:40 -0000 Received: from unknown (HELO hotmail.com) (216.33.236.145) by sources.redhat.com with SMTP; 1 Aug 2002 23:54:40 -0000 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 1 Aug 2002 16:54:40 -0700 Received: from 129.78.64.17 by lw7fd.law7.hotmail.msn.com with HTTP; Thu, 01 Aug 2002 23:54: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 16:54:00 -0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 01 Aug 2002 23:54:40.0161 (UTC) FILETIME=[CCBDB110:01C239B6] X-SW-Source: 2002-08/txt/msg00057.txt.bz2 > > > > The Right Thing to do is not to add -I/usr/include because that can >cause > > > subtle breakage as well. > > > > Or maybe the right thing is to fix autoconf so that it doesn't think a > > warning is a fatal error. > >The problem is that there are very large numbers of GNU and other freeware >packages out there with this defect in their autoconf files. When we >release 3.2, people are going to have a bear of a time building >distributions. It will be seen as a gcc problem, even if a good argument >can be made that it is an autoconf problem. So now would be a good time to be out pushing for projects to upgrade to autoconf 2.5+ (which I am told fixes the problem)? Having had the situation kindly explained to me in another branch of this thread I see 3 options 1. leave it as is, get out there and push (help even!) 2. drop the warning/enable disablement of warning (last option not liked) 3. add a flag which autoremoves any -I which causes the warning. (doubt this is going to go over too well either) 1 = lots of work 2 = back to before with lots of potential breakage... 3 = removes onus to fix the actual problem. Gareth _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx