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: Thu, 08 Aug 2013 18:04:00 -0000 [thread overview] Message-ID: <bug-42955-4-RryYDJ0wmd@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 --- Comment #8 from Brooks Moses <brooks at gcc dot gnu.org> --- FWIW, there was some interesting discussion of this on http://sourceware.org/bugzilla/show_bug.cgi?id=15823. In particular, Joseph Myers argues that "the bug is installing the files in $target/bin/ at all ... That directory contains executables from binutils for internal use by GCC; that's its sole purpose. The files installed by GCC there aren't used by GCC (rather, the public installed copy of the driver gets used when collect2 needs to call back to the driver), so shouldn't be installed." Given the attention this bug has received in the past three years, and the fact that this was broken for at least three years before the bug was filed, I'm inclined to agree. (There are two or three references online to making the $target/bin/gcc programs work by setting PATH variables to the relevant libexec subdirectory, so they're not _completely_ unused. But nothing ever is.)
next prev parent reply other threads:[~2013-08-08 18:04 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 2013-08-08 18:04 ` brooks at gcc dot gnu.org [this message] 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-RryYDJ0wmd@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: linkBe 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).