public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/64572] r219477 breaks bootstrap on x86_64 darwin
Date: Wed, 14 Jan 2015 10:50:00 -0000 [thread overview]
Message-ID: <bug-64572-4-7rUFjVc1nO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64572-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64572
--- Comment #12 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> I can confirm these now. Executing 'make -k check' in
> /sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/x86_64-apple-
> darwin14.1.0/i386/libffi doesn't cause -m32 to be passed to the test suite
> but 'make -k check RUNTESTFLAGS="--target_board=unix'{-m32}'"' does.
This is not darwin specific: see
https://gcc.gnu.org/ml/gcc-testresults/2015-01/msg01376.html.
At https://gcc.gnu.org/ml/gcc-testresults/2015-01/msg01372.html, I see
=== libffi tests ===
Running target unix
=== libffi Summary ===
# of expected passes 2204
i.e., no unix/-m32.
Should we open a new PR for that?
next prev parent reply other threads:[~2015-01-14 10:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 20:18 [Bug libffi/64572] New: " howarth at bromo dot med.uc.edu
2015-01-12 20:22 ` [Bug libffi/64572] " howarth at bromo dot med.uc.edu
2015-01-12 20:45 ` rth at gcc dot gnu.org
2015-01-12 22:55 ` howarth at bromo dot med.uc.edu
2015-01-12 23:03 ` howarth at bromo dot med.uc.edu
2015-01-12 23:26 ` rth at gcc dot gnu.org
2015-01-13 0:36 ` rth at gcc dot gnu.org
2015-01-13 3:23 ` howarth at bromo dot med.uc.edu
2015-01-13 9:55 ` dominiq at lps dot ens.fr
2015-01-13 23:53 ` howarth at bromo dot med.uc.edu
2015-01-14 0:32 ` howarth at bromo dot med.uc.edu
2015-01-14 10:50 ` dominiq at lps dot ens.fr [this message]
2015-01-14 19:47 ` howarth at bromo dot med.uc.edu
2015-01-14 20:12 ` rth at gcc dot gnu.org
2015-01-14 23:34 ` dominiq at lps dot ens.fr
2015-01-14 23:54 ` hjl.tools at gmail dot com
2015-01-15 0:47 ` rth at gcc dot gnu.org
2015-01-15 0:54 ` dominiq at lps dot ens.fr
2015-01-15 2:52 ` howarth at bromo dot med.uc.edu
2015-01-15 3:04 ` howarth at bromo dot med.uc.edu
2015-01-15 19:28 ` howarth at bromo dot med.uc.edu
2015-01-15 19:55 ` howarth at bromo dot med.uc.edu
2015-01-15 20:56 ` rth at gcc dot gnu.org
2015-01-15 21:02 ` rth at gcc dot gnu.org
2015-01-15 23:41 ` howarth at bromo dot med.uc.edu
2015-01-16 20:55 ` rth 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-64572-4-7rUFjVc1nO@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).