From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2677 invoked by alias); 30 Jul 2004 14:54:09 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 2612 invoked by alias); 30 Jul 2004 14:54:08 -0000 Date: Fri, 30 Jul 2004 14:54:00 -0000 Message-ID: <20040730145408.2611.qmail@sourceware.org> From: "scott dot bailey at eds dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040727192305.16787.scott.bailey@eds.com> References: <20040727192305.16787.scott.bailey@eds.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug bootstrap/16787] NAN constant "(0.0/0.0)" cannot be compiled by Tru64 cc X-Bugzilla-Reason: CC X-SW-Source: 2004-07/txt/msg03567.txt.bz2 List-Id: ------- Additional Comments From scott dot bailey at eds dot com 2004-07-30 14:54 ------- Subject: RE: NAN constant "(0.0/0.0)" cannot be comp iled by Tru64 cc Okay, I was able to get a good bootstrap doing this: CC="cc -ieee" CFLAGS=-O2 /usr/local/bin/make bootstrap The semi-obvious alternative, 'CC=cc CFLAGS="-O2 -ieee" ...' does not work because after the compiler build succeeds, the make process then attempts to build the c++ libraries using gcc with the supplied CFLAGS and then dies because "-ieee" is not a valid gcc argument. Trying STAGE1_CFLAGS didn't seem to do the right thing either, and I didn't have any other decent guesses. :-) Is it possible to teach configure that -ieee is needed when using the native Tru64 cc compiler? (Well, "needed" for 5.1 and, it appears, "harmless" for earlier versions.) I have a couple more observations that I will open separate reports on. Cheers, Scott -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16787