public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/5869: gcc-20020304 bootstrap fails on DEC Alpha OSF/1 4.0 because of gcc-specific compiler flags passed to native compiler
Date: Thu, 07 Mar 2002 09:46:00 -0000 [thread overview]
Message-ID: <20020307174603.31439.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/5869; it has been noted by GNATS.
From: Zack Weinberg <zack@codesourcery.com>
To: "Nelson H. F. Beebe" <beebe@math.utah.edu>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/5869: gcc-20020304 bootstrap fails on DEC Alpha OSF/1 4.0 because of gcc-specific compiler flags passed to native compiler
Date: Thu, 7 Mar 2002 09:37:02 -0800
On Thu, Mar 07, 2002 at 09:54:03AM -0700, Nelson H. F. Beebe wrote:
> >> It should not have attempted to compile f/fini.c at all with the
> >> native compiler. Please mail me (personally) the complete build log.
>
> Here it is (but hostname obscured as XXXXXXXX):
Aha, I see the problem. f/fini is compiled to run during the build,
which means it is compiled with $(HOST_CC); but that should have been
forced equal to $(CC) by configure, since this is a native bootstrap,
and then overridden to use the just-built gcc by the bootstrap logic.
I suspect a Make bug. Can you try again with GNU make, please?
zw
next reply other threads:[~2002-03-07 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-07 9:46 Zack Weinberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-19 1:07 neil
2002-03-07 8:56 Zack Weinberg
2002-03-07 8:06 Nelson H. F. Beebe
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=20020307174603.31439.qmail@sources.redhat.com \
--to=zack@codesourcery.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/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).