public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/36443] [4.3/4.4 Regression]: HOSTCC doesn't work with installed gcc Date: Thu, 12 Jun 2008 12:34:00 -0000 [thread overview] Message-ID: <20080612123312.6625.qmail@sourceware.org> (raw) In-Reply-To: <bug-36443-682@http.gcc.gnu.org/bugzilla/> ------- Comment #26 from hjl dot tools at gmail dot com 2008-06-12 12:33 ------- Don't we need the same workaround in ./objc.dg/gnu-encoding/gnu-encoding.exp:set status [remote_exec host "$HOSTCC $HOSTCFLAGS $generator_cmd"] -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36443
next prev parent reply other threads:[~2008-06-12 12:34 UTC|newest] Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-06-05 21:31 [Bug testsuite/36443] New: HOST_CC doesn't work with --disable-bootstrap hjl dot tools at gmail dot com 2008-06-05 21:33 ` [Bug testsuite/36443] " pinskia at gcc dot gnu dot org 2008-06-05 21:35 ` hjl dot tools at gmail dot com 2008-06-05 21:42 ` Andrew Pinski 2008-06-05 21:42 ` pinskia at gmail dot com 2008-06-05 21:58 ` [Bug testsuite/36443] [4.3/4.4 Regression]: " hjl dot tools at gmail dot com 2008-06-06 21:03 ` [Bug testsuite/36443] [4.3/4.4 Regression]: HOSTCC doesn't work with unstalled gcc hjl dot tools at gmail dot com 2008-06-06 21:10 ` hjl dot tools at gmail dot com 2008-06-06 23:00 ` mmitchel at gcc dot gnu dot org 2008-06-07 1:07 ` hjl dot tools at gmail dot com 2008-06-08 20:24 ` mark at codesourcery dot com 2008-06-08 20:46 ` hjl dot tools at gmail dot com 2008-06-08 21:13 ` mark at codesourcery dot com 2008-06-08 22:55 ` hjl dot tools at gmail dot com 2008-06-09 0:06 ` mark at codesourcery dot com 2008-06-09 2:29 ` hjl dot tools at gmail dot com 2008-06-09 6:59 ` jakub at gcc dot gnu dot org 2008-06-09 14:16 ` hjl dot tools at gmail dot com 2008-06-09 21:17 ` [Bug testsuite/36443] [4.3/4.4 Regression]: HOSTCC doesn't work with installed gcc mark at codesourcery dot com 2008-06-09 23:58 ` hjl dot tools at gmail dot com 2008-06-10 0:39 ` mark at codesourcery dot com 2008-06-10 1:46 ` hjl dot tools at gmail dot com 2008-06-10 5:03 ` mark at codesourcery dot com 2008-06-10 5:50 ` hjl dot tools at gmail dot com 2008-06-11 11:14 ` jsm28 at gcc dot gnu dot org 2008-06-12 11:18 ` jakub at gcc dot gnu dot org 2008-06-12 11:40 ` jakub at gcc dot gnu dot org 2008-06-12 11:41 ` jakub at gcc dot gnu dot org 2008-06-12 12:34 ` hjl dot tools at gmail dot com [this message] 2008-07-15 14:41 ` pinskia at gcc dot gnu dot org 2008-07-17 5:14 ` hjl at gcc dot gnu dot org 2008-08-27 22:09 ` jsm28 at gcc dot gnu dot org 2009-01-24 10:24 ` rguenth at gcc dot gnu dot org 2009-01-26 18:14 ` hjl at gcc dot gnu dot org 2009-01-27 15:48 ` hjl dot tools at gmail dot com 2009-01-27 15:54 ` hjl dot tools at gmail dot com 2009-01-27 16:06 ` hjl dot tools at gmail dot com 2009-01-27 18:46 ` janis at gcc dot gnu dot org 2009-01-27 21:12 ` rob1weld at aol dot com 2009-01-27 21:27 ` rob1weld at aol dot com 2009-01-27 21:32 ` rob1weld at aol dot com 2009-01-28 3:08 ` rob1weld at aol dot com 2009-01-28 13:52 ` rob1weld at aol dot com 2009-01-29 15:01 ` rob1weld at aol dot com 2009-01-29 18:32 ` janis at gcc dot gnu dot org 2009-01-29 22:36 ` janis at gcc dot gnu dot org 2009-01-29 23:12 ` rob1weld at aol dot com 2009-01-31 22:13 ` rob1weld at aol dot com 2009-02-02 22:00 ` mmitchel at gcc dot gnu dot org 2009-02-05 4:06 ` rob1weld at aol dot com 2009-02-06 18:35 ` mark at codesourcery dot com 2009-02-06 19:16 ` hjl dot tools at gmail dot com 2009-02-06 19:22 ` mark at codesourcery dot com 2009-02-06 19:31 ` janis at gcc dot gnu dot org 2009-02-07 6:00 ` rob1weld at aol dot com 2009-02-09 17:22 ` janis at gcc dot gnu dot org 2009-08-04 12:40 ` [Bug testsuite/36443] [4.3/4.4/4.5 " rguenth at gcc dot gnu dot org 2010-05-22 18:24 ` [Bug testsuite/36443] [4.3/4.4/4.5/4.6 " rguenth 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=20080612123312.6625.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).