From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16630 invoked by alias); 31 Mar 2004 02:50:05 -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 16621 invoked from network); 31 Mar 2004 02:50:05 -0000 Received: from unknown (HELO bluesmobile.specifixinc.com) (64.62.200.227) by sources.redhat.com with SMTP; 31 Mar 2004 02:50:05 -0000 Received: from localhost.localdomain (bluesmobile.corp.specifixinc.com [10.0.0.1]) by bluesmobile.specifixinc.com (Postfix) with ESMTP id 55A11164DC; Tue, 30 Mar 2004 18:50:04 -0800 (PST) Subject: Re: fixing vs WARN_CFLAGS vs cross builds From: Jim Wilson To: DJ Delorie Cc: gcc@gcc.gnu.org In-Reply-To: <200403310143.i2V1hFA0014438@greed.delorie.com> References: <200403292112.i2TLC2xB002927@greed.delorie.com> <406A1FA1.1090602@specifixinc.com> <200403310143.i2V1hFA0014438@greed.delorie.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Wed, 31 Mar 2004 07:53:00 -0000 Message-Id: <1080701413.1213.25.camel@leaf.tuliptree.org> Mime-Version: 1.0 X-SW-Source: 2004-03/txt/msg01739.txt.bz2 On Tue, 2004-03-30 at 17:43, DJ Delorie wrote: > Yes. BUILD_CC is 3.2.3, and does not support these: > cc1: unrecognized option `-Wno-variadic-macros' > cc1: unrecognized option `-Wold-style-definition' There is still an unanswered question here. Why is this failing for BUILD_CC but not CC or HOST_CC? This needs further investigation. I see that these options are in STRICT2_WARN which is not used except in POSTSTAGE1_FLAGS_TO_PASS, which is only used for stage2 and stage3 builds. Thus we only use the flags when we know that we are building ourselves, in which case these options are always safe. So I still don't see why you are having a problem. You need to better explain why your build is failing. What exactly are you doing that is causing the failure? > I have a patch which tests for build!=host and disables WARN_CFLAGS, > but should fixinc *ever* be built with WARN_CFLAGS? We could in stage2 and stage3 builds, in which case we know that CC_FOR_BUILD must be a compiler built from the current sources, as we can only reach here for native builds. That seems to be how it currently works. Are you perhaps trying to bootstrap a cross compiler somehow? I don't see how this can work, but this seems to be the only way to trigger this failure. -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com