From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27088 invoked by alias); 31 Jul 2002 16:45:47 -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 27033 invoked from network); 31 Jul 2002 16:45:40 -0000 Received: from unknown (HELO boden.synopsys.com) (204.176.20.19) by sources.redhat.com with SMTP; 31 Jul 2002 16:45:40 -0000 Received: from crone.synopsys.com (crone.synopsys.com [146.225.7.23]) by boden.synopsys.com (Postfix) with ESMTP id B9A3CDAEF; Wed, 31 Jul 2002 09:45:39 -0700 (PDT) Received: from atrus.synopsys.com (localhost [127.0.0.1]) by crone.synopsys.com (8.9.3+Sun/8.9.1) with ESMTP id JAA07230; Wed, 31 Jul 2002 09:45:35 -0700 (PDT) From: Joe Buck Received: (from jbuck@localhost) by atrus.synopsys.com (8.9.3+Sun/8.9.1) id JAA25032; Wed, 31 Jul 2002 09:45:39 -0700 (PDT) Message-Id: <200207311645.JAA25032@atrus.synopsys.com> Subject: Re: gcc 3.2's cpp breaks configure scripts To: tilps@hotmail.com (Gareth Pearce) Date: Wed, 31 Jul 2002 12:44:00 -0000 Cc: gcc@gcc.gnu.org In-Reply-To: from "Gareth Pearce" at Jul 31, 2002 11:15:51 PM MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-07/txt/msg01506.txt.bz2 > > cpp is spitting out a warning about changing the search order of include > > directories, and this is breaking a _ton_ of configure scripts. I found > > this when I started rebuilding Mandrake with gcc-3.2 branch. Gareth Pearce writes: > This, from what little i have seen, seems to be due to the fact that many > configure scripts segments are extremely overly picky. They take any output > at all as to mean that its failed. Really it should seem to me that they > should be looking for errors, or specific warnings rather then just anything > at all. Just the same, it's a lot to ask the distributors of GNU/Linux and BSD systems to fix every configure script in the world. Maybe a workaround for the time being is to have a gcc option that suppresses this one warning; people can then write something like CC="gcc -Wno-check-include-order" ./configure ... to get around the problem. However, if this warning appears, it is likely that the programs in question won't build properly on OSes that ship bad C headers, that have to be fixed by fixincludes. In that case, it may well be that the gcc command lines will wind up with something like -I/usr/include which means that the fixed headers will get bypassed.