public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "scovich at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/43301] top-level configure script ignores ---with-build-time-tools
Date: Tue, 09 Mar 2010 01:04:00 -0000 [thread overview]
Message-ID: <20100309010436.13300.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43301-14600@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from scovich at gmail dot com 2010-03-09 01:04 -------
(In reply to comment #0)
> Let's just say this led to extremely frustrating behavior until I decided to
> start digging...
To be more specific, the gcc/as wrapper is generated with:
ORIGINAL_AS_FOR_TARGET=""
ORIGINAL_LD_FOR_TARGET=""
ORIGINAL_PLUGIN_LD_FOR_TARGET=""
ORIGINAL_NM_FOR_TARGET=""
Which causes the building of libgcc to fail later on at gcc/as line 83 with a
message about "exec: not found"
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43301
next prev parent reply other threads:[~2010-03-09 1:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 1:00 [Bug bootstrap/43301] New: " scovich at gmail dot com
2010-03-09 1:04 ` scovich at gmail dot com [this message]
[not found] <bug-43301-4@http.gcc.gnu.org/bugzilla/>
2022-05-24 15:04 ` [Bug bootstrap/43301] " egallager at gcc dot gnu.org
2022-07-31 20:58 ` egallager at gcc dot gnu.org
2022-08-02 23:05 ` iains at gcc dot gnu.org
2022-08-04 2:20 ` egallager at gcc dot gnu.org
2022-12-02 6:27 ` egallager at gcc dot gnu.org
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=20100309010436.13300.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).