From: Ian Lance Taylor <ian@zembu.com>
To: schwab@suse.de
Cc: binutils@sourceware.cygnus.com
Subject: Re: ld/configure.host has hardcoded gcc
Date: Wed, 18 Aug 1999 10:29:00 -0000 [thread overview]
Message-ID: <19990818165253.7179.qmail@daffy.airs.com> (raw)
In-Reply-To: <jeiu6de679.fsf@hawking.suse.de>
From: Andreas Schwab <schwab@suse.de>
Date: 18 Aug 1999 12:25:30 +0200
ld/configure.host hardcodes the compiler under the name gcc. Shouldn't
that rather be ${CC}? Background: the default gcc is egcs-2.91.66, but
I'm compiling with /usr/local/i686-linux/bin/gcc, which is gcc 2.96 (the
latest cvs version). The latter requires for C++ a new function from
libgcc (__rethrow), which egcs-2.91.66 doesn't define yet. Thus linking a
C++ program against egcs-2.91.66/libgcc.a fails. This causes spurious
failures in the testsuite.
configure.host uses gcc rather than ${CC} so that it will, in
principle, work on a system which has both gcc and a non-gcc C
compiler. That is, you might run the tests on Solaris with CC set to
the SunPRO cc, with gcc also installed. The tests would then link
against the gcc startup files and libgcc, but that would be OK.
This probably wouldn't really work in practice, though. I think it's
fine to change gcc to ${CC}. It's only for testing anyhow.
Ian
prev parent reply other threads:[~1999-08-18 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-18 3:26 Andreas Schwab
1999-08-18 10:29 ` Ian Lance Taylor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19990818165253.7179.qmail@daffy.airs.com \
--to=ian@zembu.com \
--cc=binutils@sourceware.cygnus.com \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).