From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6219 invoked by alias); 31 Mar 2004 01:43:17 -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 6211 invoked from network); 31 Mar 2004 01:43:16 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 31 Mar 2004 01:43:16 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i2V1hG1X001852; Tue, 30 Mar 2004 20:43:16 -0500 Received: from post-office.corp.redhat.com (post-office.corp.redhat.com [172.16.52.227]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i2V1hGj05152; Tue, 30 Mar 2004 20:43:16 -0500 Received: from greed.delorie.com (dj.cipe.redhat.com [10.0.0.222]) by post-office.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i2V1hFV28839; Tue, 30 Mar 2004 20:43:15 -0500 Received: from greed.delorie.com (localhost [127.0.0.1]) by greed.delorie.com (8.12.10/8.12.10) with ESMTP id i2V1hFYj014442; Tue, 30 Mar 2004 20:43:15 -0500 Received: (from dj@localhost) by greed.delorie.com (8.12.10/8.12.10/Submit) id i2V1hFA0014438; Tue, 30 Mar 2004 20:43:15 -0500 Date: Wed, 31 Mar 2004 06:40:00 -0000 Message-Id: <200403310143.i2V1hFA0014438@greed.delorie.com> From: DJ Delorie To: wilson@specifixinc.com CC: gcc@gcc.gnu.org In-reply-to: <406A1FA1.1090602@specifixinc.com> (message from Jim Wilson on Tue, 30 Mar 2004 17:32:17 -0800) Subject: Re: fixing vs WARN_CFLAGS vs cross builds References: <200403292112.i2TLC2xB002927@greed.delorie.com> <406A1FA1.1090602@specifixinc.com> X-SW-Source: 2004-03/txt/msg01735.txt.bz2 > The gcc Makefile does not directly call "gcc" anywhere. From a brief > glance, I think you mean CC_FOR_BUILD, which you have set to gcc. Yes. > It isn't exactly clear why you have a problem though. WARN_CFLAGS is > set for a stage1 build only if the build (host?) compiler is gcc, and > your compiler is gcc, so why is there a problem? Is there a particular > option which is the problem? If so, which one? Is this a versioning > problem? I.e. an option is in WARN_CFLAGS that is not supported by an > old gcc version you are using for the bootstrap? Yes. BUILD_CC is 3.2.3, and does not support these: cc1: unrecognized option `-Wno-variadic-macros' cc1: unrecognized option `-Wold-style-definition' > It may be reasonable to remove the WARN_CFLAGS setting in the fixinc.sh > rule. We don't use WARN_CFLAGS anyplace else where we use CC_FOR_BUILD. > This can work in stage2 etc builds, but this is probably not important > enough to worry about. > > It would be nice to have a proper bug report though. I was still trying to figure out what was supposed to happen from a theoretical standpoint. I have a patch which tests for build!=host and disables WARN_CFLAGS, but should fixinc *ever* be built with WARN_CFLAGS?