public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/41180] can not build gcc 4.4.1 on Snow Leopard Mac OS X 10.6
Date: Fri, 28 Aug 2009 10:19:00 -0000 [thread overview]
Message-ID: <20090828101948.19817.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41180-13994@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from redi at gcc dot gnu dot org 2009-08-28 10:19 -------
(In reply to comment #0)
> #gcc
> cd ../gcc-4.4.1
> ./configure --prefix=/home/dmarkman/Development/GCC/macintel64/mpfr-2.4.1/build
> --with-gmp=/home/dmarkman/Development/GCC/macintel64/gmp-4.3.1/build
is that command right?
I think you will need to attach the libgcc/config.log as that seems to be where
the problem is.
You can use something like --build=i386-apple-darwin10.0.0 when configuring
gmp, mpfr and gcc, to ensure they all agree on what to build.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41180
next prev parent reply other threads:[~2009-08-28 10:19 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 3:13 [Bug c++/41180] New: " dmarkman at mac dot com
2009-08-28 3:17 ` [Bug c++/41180] " dmarkman at mac dot com
2009-08-28 10:19 ` redi at gcc dot gnu dot org [this message]
2009-08-28 10:23 ` [Bug bootstrap/41180] " redi at gcc dot gnu dot org
2009-08-28 13:28 ` howarth at nitro dot med dot uc dot edu
2009-08-28 14:36 ` dmarkman at mac dot com
2009-08-28 14:37 ` dmarkman at mac dot com
2009-08-28 15:02 ` redi at gcc dot gnu dot org
2009-08-28 15:12 ` howarth at nitro dot med dot uc dot edu
2009-08-28 15:32 ` howarth at nitro dot med dot uc dot edu
2009-08-28 16:14 ` mrs at gcc dot gnu dot org
2009-08-28 17:28 ` dmarkman at mac dot com
2009-08-29 1:32 ` howarth at nitro dot med dot uc dot edu
2009-08-29 1:41 ` howarth at nitro dot med dot uc dot edu
2009-08-29 2:19 ` howarth at nitro dot med dot uc dot edu
2009-08-31 17:36 ` mrs at apple dot com
2009-08-31 17:38 ` mrs at apple dot com
2009-08-31 18:04 ` howarth at nitro dot med dot uc dot edu
2009-08-31 20:37 ` mrs at apple dot com
2009-09-01 4:00 ` howarth at nitro dot med dot uc dot edu
2009-09-01 4:23 ` howarth at nitro dot med dot uc dot edu
2009-09-02 20:37 ` mrs at apple dot com
2009-09-02 21:41 ` howarth at nitro dot med dot uc dot edu
2009-09-02 21:44 ` howarth at nitro dot med dot uc dot edu
2009-09-02 22:22 ` howarth at nitro dot med dot uc dot edu
2009-09-02 23:37 ` howarth at nitro dot med dot uc dot edu
2009-09-03 0:20 ` mrs at apple dot com
2009-09-03 0:56 ` howarth at nitro dot med dot uc dot edu
2009-09-03 11:04 ` joseph at codesourcery dot com
2009-09-03 13:00 ` howarth at nitro dot med dot uc dot edu
2009-09-04 1:50 ` mrs at apple dot com
2009-09-09 8:15 ` fxcoudert at gcc dot gnu dot org
2009-09-09 8:47 ` fxcoudert at gcc dot gnu dot org
2009-09-30 19:40 ` pinskia at gcc dot gnu dot org
2009-09-30 19:41 ` pinskia 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=20090828101948.19817.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).