public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/38314] multilib bootstrap broken for x86_64-apple-darwin10
Date: Sat, 29 Nov 2008 04:13:00 -0000 [thread overview]
Message-ID: <20081129041208.31553.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38314-11113@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from howarth at nitro dot med dot uc dot edu 2008-11-29 04:12 -------
../gcc/configure --prefix=/Users/howarth/inst_gcc
--enable-languages=c,c++,fortran,java --with-gmp=/sw --with-libiconv-prefix=/sw
--with-system-zlib --x-includes=/usr/X11R6/include
--x-libraries=/usr/X11R6/lib --with-arch=nocona --with-tune=generic
--build=i686-apple-darwin10 --host=i686-apple-darwin10
--target=i686-apple-darwin10
makes it pass stage1 and it appears that the bootstrap will complete with that
triplet.
So the problem appears to be specific to x86_64-apple-darwin* when the system
compiler
generates x86_64 by default. I suspect that both triplets end up passing -m64
for the
x86_64 subdirectory but nothing for the toplevel libgcc build. We need to force
-m32 for
the toplevel libgcc, no?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38314
next prev parent reply other threads:[~2008-11-29 4:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 3:12 [Bug bootstrap/38314] New: gcc trunk doesn't build libjava on x86_64-apple-darwin10 howarth at nitro dot med dot uc dot edu
2008-11-29 3:42 ` [Bug bootstrap/38314] " howarth at nitro dot med dot uc dot edu
2008-11-29 3:46 ` howarth at nitro dot med dot uc dot edu
2008-11-29 3:48 ` howarth at nitro dot med dot uc dot edu
2008-11-29 4:13 ` howarth at nitro dot med dot uc dot edu [this message]
2008-11-29 18:45 ` [Bug bootstrap/38314] multilib bootstrap broken for x86_64-apple-darwin10 howarth at nitro dot med dot uc dot edu
2008-11-29 19:25 ` howarth at nitro dot med dot uc dot edu
2008-11-29 19:32 ` andreast at gcc dot gnu dot org
2008-11-29 20:05 ` howarth at nitro dot med dot uc dot edu
2008-11-29 20:12 ` howarth at nitro dot med dot uc dot edu
2008-11-29 20:26 ` andreast at gcc dot gnu dot org
2008-11-29 20:36 ` howarth at nitro dot med dot uc dot edu
2008-11-29 21:07 ` howarth at nitro dot med dot uc dot edu
2008-11-29 21:10 ` howarth at nitro dot med dot uc dot edu
2008-11-29 21:21 ` andreast at gcc dot gnu dot org
2008-11-29 21:29 ` howarth at nitro dot med dot uc dot edu
2008-11-30 0:59 ` howarth at nitro dot med dot uc dot edu
2008-11-30 8:24 ` andreast at gcc dot gnu dot org
2008-12-08 20:37 ` andreast 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=20081129041208.31553.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: 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).