public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/49741] make -k check-c++0x not multilib aware
Date: Fri, 15 Jul 2011 05:32:00 -0000 [thread overview]
Message-ID: <bug-49741-4-lTZ7hL39ry@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49741-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49741
--- Comment #5 from Jack Howarth <howarth at nitro dot med.uc.edu> 2011-07-15 05:31:40 UTC ---
(In reply to comment #4)
> Created attachment 24772 [details]
> Patch to use --zadditional_options instead of --tool_opts
>
> Does this work better?
Yes. This eliminates the failures at -m32 for the x86_64-apple-darwin11
multilib build. Thanks.
next prev parent reply other threads:[~2011-07-15 5:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 1:04 [Bug testsuite/49741] New: " howarth at nitro dot med.uc.edu
2011-07-14 21:07 ` [Bug testsuite/49741] " jason at gcc dot gnu.org
2011-07-15 2:53 ` howarth at nitro dot med.uc.edu
2011-07-15 3:45 ` jason at gcc dot gnu.org
2011-07-15 4:01 ` jason at gcc dot gnu.org
2011-07-15 5:32 ` howarth at nitro dot med.uc.edu [this message]
2011-07-15 10:55 ` howarth at nitro dot med.uc.edu
2011-07-15 21:30 ` jason at gcc dot gnu.org
2011-08-01 20:42 ` jason 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=bug-49741-4-lTZ7hL39ry@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).