public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/49469] GCC fails to bootstrap when building with embedded zlib on Mac OS X 10.6.7
Date: Tue, 07 Feb 2012 03:35:00 -0000 [thread overview]
Message-ID: <bug-49469-4-CMAJN1C4fo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49469-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49469
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-02-07 03:35:22 UTC ---
/Users/dxy/VCS/GIT/gcc/zlib/configure: line 3225:
/tmp/gcc-build/i386/./prev-gcc/xgcc: No such file or directory
> --enable-multilib \
Don't use that option, zlib is not very friendly to it. And the rest of the
build machinary knows if multilib is enabled or now.
next prev parent reply other threads:[~2012-02-07 3:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 21:22 [Bug bootstrap/49469] New: " manphiz at gmail dot com
2011-07-02 22:54 ` [Bug bootstrap/49469] " hp at gcc dot gnu.org
2011-07-03 4:29 ` manphiz at gmail dot com
2012-02-03 23:23 ` pinskia at gcc dot gnu.org
2012-02-07 3:29 ` manphiz at gmail dot com
2012-02-07 3:35 ` pinskia at gcc dot gnu.org [this message]
2012-02-07 3:58 ` manphiz at gmail dot com
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-49469-4-CMAJN1C4fo@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).