public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/25672] [4.3/4.4?/4.5 regression] cross build's libgcc picks up CFLAGS
Date: Sun, 26 Sep 2010 19:36:00 -0000 [thread overview]
Message-ID: <20100926193600.AF31IGWLtur0szE428nfkqxWeyXDSpeiCSKjuFA_Uq8@z> (raw)
In-Reply-To: <bug-25672-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25672
Pawel Sikora <pluto at agmk dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|ppc64-pld-linux |x86_64-pc-mingw32
Known to work| |
Summary|[4.3 regression] cross |[4.3/4.4?/4.5 regression]
|build's libgcc picks up |cross build's libgcc picks
|CFLAGS |up CFLAGS
Known to fail| |4.5.2
--- Comment #27 from Pawel Sikora <pluto at agmk dot net> 2010-09-26 17:21:01 UTC ---
this bug still exists on current 4.5 branch and probably on trunk.
e.g. for mingw64 cross compilation libgcc's configure fails with:
(...)
checking for suffix of object files... configure: error: in
`/home/users/pluto/rpm/BUILD/gcc-4.5.1/BUILDDIR/x86_64-pc-mingw32/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
config.log contains:
(...)
configure:3020: /home/users/pluto/rpm/BUILD/gcc-4.5.1/BUILDDIR/./gcc/xgcc
-B/home/users/pluto/rpm/BUILD/gcc-4.5.1/BUILDDIR/./gcc/
-L/usr/x86_64-pc-mingw32/lib -L/usr/mingw/lib -isystem
/usr/x86_64-pc-mingw32/include -isystem /usr/mingw/include
-B/usr/x86_64-pc-mingw32/bin/ -B/usr/x86_64-pc-mingw32/lib/ -isystem
/usr/x86_64-pc-mingw32/include -isystem /usr/x86_64-pc-mingw32/sys-include
-o conftest -g -O2 -fno-strict-aliasing -fwrapv -march=i686 -mtune=pentium4
-gdwarf-3 -g2 conftest.c >&5
conftest.c:1:0: error: CPU you selected does not support x86-64 instruction set
conftest.c:1:0: error: CPU you selected does not support x86-64 instruction set
configure:3023: $? = 1
as you can see libgcc's configure uses CFLAGS (-O2 -fno-strict-aliasing -fwrapv
-march=i686 -mtune=pentium4 -gdwarf-3 -g2) passed to top-level configure script
:/
next parent reply other threads:[~2010-09-26 17:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-25672-4@http.gcc.gnu.org/bugzilla/>
2010-09-26 19:36 ` pluto at agmk dot net [this message]
2011-06-27 15:05 ` rguenth at gcc dot gnu.org
2012-03-13 15:11 ` [Bug bootstrap/25672] [4.4?/4.5 " jakub at gcc dot gnu.org
2012-03-27 8:40 ` [Bug bootstrap/25672] [4.5 Regression] " rguenth at gcc dot gnu.org
2012-03-27 18:53 ` pluto at agmk dot net
2012-07-02 9:26 ` [Bug bootstrap/25672] [4.6/4.7/4.8 " rguenth at gcc dot gnu.org
2013-01-15 15:03 ` rguenth at gcc dot gnu.org
2013-04-12 15:18 ` [Bug bootstrap/25672] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2014-05-11 12:37 ` [Bug bootstrap/25672] [4.7/4.8/4.9/4.10 " pinskia at gcc dot gnu.org
2014-05-11 18:48 ` olegendo at gcc dot gnu.org
2014-06-12 13:49 ` rguenth at gcc dot gnu.org
2014-12-19 13:33 ` [Bug bootstrap/25672] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-03-09 20:47 ` aldyh at gcc dot gnu.org
2015-03-10 7:59 ` olegendo at gcc dot gnu.org
2015-03-10 16:38 ` aldyh at gcc dot gnu.org
2015-03-10 16:40 ` [Bug bootstrap/25672] [4.8/4.9 " aldyh at gcc dot gnu.org
2015-06-23 8:25 ` rguenth at gcc dot gnu.org
2015-06-26 20:01 ` [Bug bootstrap/25672] [4.9 " jakub at gcc dot gnu.org
2015-06-26 20:31 ` jakub at gcc dot gnu.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=20100926193600.AF31IGWLtur0szE428nfkqxWeyXDSpeiCSKjuFA_Uq8@z \
--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).