public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot 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, 22 Apr 2010 20:17:00 -0000 [thread overview] Message-ID: <20100422201657.30552.qmail@sourceware.org> (raw) In-Reply-To: <bug-42955-18744@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from hp at gcc dot gnu dot org 2010-04-22 20:16 ------- I've seen this too, for e.g. crisv32-axis-linux-gnu configured with /absolute/path/toplevel/configure --target=crisv32-axis-linux-gnu. Andrew: Isn't this a duplicate report even? IIRC you were talking on IRC about entering one, though I guess neither of us did? -- hp at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hp at gcc dot gnu dot org Last reconfirmed|0000-00-00 00:00:00 |2010-04-22 20:16:57 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42955
next prev parent reply other threads:[~2010-04-22 20:17 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 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 [this message] 2010-04-22 20:18 ` hp at gcc dot gnu dot org 2010-04-22 20:21 ` hp at gcc dot gnu dot org [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 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
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=20100422201657.30552.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: 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).