public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alexandre.nunes at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/43328] multilib bootstrap broken.
Date: Sun, 30 Oct 2011 11:21:00 -0000 [thread overview]
Message-ID: <bug-43328-4-pJ2bffK7FR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43328-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43328
Alexandre Pereira Nunes <alexandre.nunes at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexandre.nunes at gmail
| |dot com
--- Comment #21 from Alexandre Pereira Nunes <alexandre.nunes at gmail dot com> 2011-10-30 11:20:11 UTC ---
Building gcc 4.6.2 as a cross-compiler on ix86 targetting arm-elf fails for me
w/ --enable-multilib explicitly passed on, w/ zlib barking about trying to
compile a 64-bit version. gcc 4.6.1 used to work w/ same directives, so I
suspect I'm seeing a regression.
removing --enable-multilib from args passed to gcc seems to make the issue go
away.
next prev parent reply other threads:[~2011-10-30 11:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43328-4@http.gcc.gnu.org/bugzilla/>
2010-11-21 8:23 ` pluto at agmk dot net
2010-11-21 8:38 ` rwild at gcc dot gnu.org
2010-11-21 9:23 ` pluto at agmk dot net
2011-10-30 11:21 ` alexandre.nunes at gmail dot com [this message]
2012-08-29 23:48 ` jmesmon at gmail dot com
2012-08-29 23:49 ` jmesmon at gmail dot com
2021-08-26 6:04 ` pinskia at gcc dot gnu.org
2021-08-26 6:12 ` pinskia at gcc dot gnu.org
2021-08-26 6:15 ` pinskia at gcc dot gnu.org
2010-03-10 22:33 [Bug bootstrap/43328] New: " pluto at agmk dot net
2010-03-10 22:37 ` [Bug bootstrap/43328] " pinskia at gcc dot gnu dot org
2010-03-11 15:46 ` rwild at gcc dot gnu dot org
2010-03-11 16:02 ` pluto at agmk dot net
2010-03-11 16:06 ` rwild at gcc dot gnu dot org
2010-03-11 18:11 ` pluto at agmk dot net
2010-03-11 18:15 ` Andrew Pinski
2010-03-11 18:15 ` pinskia at gmail dot com
2010-03-11 18:21 ` pluto at agmk dot net
2010-03-11 18:33 ` rwild at gcc dot gnu dot org
2010-03-11 19:28 ` pluto at agmk dot net
2010-03-11 19:29 ` pluto at agmk dot net
2010-03-11 19:33 ` pluto at agmk dot net
2010-03-12 18:10 ` rwild at gcc dot gnu dot org
2010-03-12 18:11 ` rwild at gcc dot gnu dot org
2010-03-16 7:57 ` rwild at gcc dot gnu dot org
2010-03-31 5:44 ` rwild at gcc dot gnu dot org
2010-04-01 13:17 ` rguenth at gcc dot gnu dot org
2010-04-01 16:33 ` rwild at gcc dot gnu dot org
2010-06-27 0:19 ` rwild 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=bug-43328-4-pJ2bffK7FR@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).