public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brooks at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/42955] undecorated cross-compiler gcc fails to find cc1
Date: Fri, 26 Jul 2013 20:21:00 -0000 [thread overview]
Message-ID: <bug-42955-4-nn7XBnMaUK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-42955-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42955
Brooks Moses <brooks at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2010-04-22 20:17:36 |2013-07-26 20:17:36
CC| |brooks at gcc dot gnu.org
Severity|normal |critical
--- Comment #7 from Brooks Moses <brooks at gcc dot gnu.org> ---
I have reconfirmed this, in the following things, all for different targets:
* A downloaded Sourcery CodeBench Lite Edition 2010.09 (GCC 4.5.1 with patches)
* A downloaded Sourcery CodeBench Lite Edition 2013.05 (GCC 4.7.3 with patches)
* A local build of our google/gcc-4_8 branch.
* A build of current development trunk.
The problem is very straightforward:
The ${target}/bin/gcc is installed from "gcc-cross", which is created by a
simple "cp" command from "xgcc" -- see the "gcc-cross$(exeext):" rule in
gcc/Makefile. (The bin/${target}-gcc is installed from "xgcc".) Thus, the
decorated and undecorated gcc executables are identical.
And, if we run this executable under strace, we will find that it looks for cc1
in things under "../libexec", but not under "../../libexec", which would be the
correct path for the undecorated executable.
next parent reply other threads:[~2013-07-26 20:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42955-4@http.gcc.gnu.org/bugzilla/>
2013-07-26 20:21 ` brooks at gcc dot gnu.org [this message]
2013-08-08 18:04 ` brooks at gcc dot gnu.org
2013-08-08 21:16 ` brooks at gcc dot gnu.org
2013-09-12 23:07 ` brooks at gcc dot gnu.org
2013-09-12 23:09 ` brooks at gcc dot gnu.org
2010-02-04 13:54 [Bug regression/42955] New: " ossman at cendio dot se
2010-02-04 17:17 ` [Bug driver/42955] " pinskia at gcc dot gnu dot org
2010-02-07 20:58 ` pinskia at gcc dot gnu dot org
2010-02-09 9:35 ` ossman at cendio dot se
2010-02-09 9:37 ` ossman at cendio dot se
2010-04-22 20:17 ` hp at gcc dot gnu dot org
2010-04-22 20:18 ` hp at gcc dot gnu dot org
2010-04-22 20:21 ` hp at gcc dot gnu dot 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=bug-42955-4-nn7XBnMaUK@http.gcc.gnu.org/bugzilla/ \
--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).