public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nbi at wideopenwest dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/48378] gcc 4.6.0 fails to build from source
Date: Sun, 03 Apr 2011 02:48:00 -0000 [thread overview]
Message-ID: <bug-48378-4-bd9Av4SpNx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48378-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48378
--- Comment #19 from nbi at wideopenwest dot com 2011-04-03 02:48:01 UTC ---
(In reply to comment #18)
> because x86_64 builds a multilib compiler by default, which is what most people
> want.
>
> use CONFIGARGS=--disable-multilib if you don't want that, or install the 32buig
> glibc headers and libs if you want a compiler that can produce 32bit or 64bit
> output
>
> I think you should continue this on the gcc-help mailing list, there's no gcc
> bug here
After installing the 32 bit headers it built cleanly. Thanks for your help.
I'll let the Debian folks know that they need to give the packaging a look.
prev parent reply other threads:[~2011-04-03 2:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 0:36 [Bug other/48378] New: " nbi at wideopenwest dot com
2011-03-31 10:02 ` [Bug other/48378] " rguenth at gcc dot gnu.org
2011-03-31 11:06 ` redi at gcc dot gnu.org
2011-03-31 17:59 ` nbi at wideopenwest dot com
2011-04-01 3:12 ` nbi at wideopenwest dot com
2011-04-01 8:36 ` redi at gcc dot gnu.org
2011-04-02 21:16 ` nbi at wideopenwest dot com
2011-04-02 21:25 ` redi at gcc dot gnu.org
2011-04-02 21:26 ` redi at gcc dot gnu.org
2011-04-02 22:24 ` nbi at wideopenwest dot com
2011-04-02 22:52 ` redi at gcc dot gnu.org
2011-04-02 23:18 ` nbi at wideopenwest dot com
2011-04-02 23:26 ` redi at gcc dot gnu.org
2011-04-02 23:32 ` redi at gcc dot gnu.org
2011-04-02 23:40 ` redi at gcc dot gnu.org
2011-04-02 23:42 ` nbi at wideopenwest dot com
2011-04-02 23:44 ` redi at gcc dot gnu.org
2011-04-03 0:14 ` nbi at wideopenwest dot com
2011-04-03 0:21 ` redi at gcc dot gnu.org
2011-04-03 2:48 ` nbi at wideopenwest dot com [this message]
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-48378-4-bd9Av4SpNx@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).