From: niXman <i.nixman@autistici.org>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Error building gcc-5.* with threads=win32
Date: Mon, 03 Aug 2015 11:31:00 -0000 [thread overview]
Message-ID: <bd8a96cc95151bf879faf8320a7a520c@autistici.org> (raw)
In-Reply-To: <6e8b5e8c89fb1f9a051e7625282c3619@autistici.org>
niXman 2015-08-02 14:37:
> niXman 2015-08-01 11:32:
>> Hi,
>>
>> I have successfully built gcc-4.8.*/4.9.* as MinGW-w64 with
>> --enable-threads=win32 but I can't build gcc-5.* with the same
>> options.
>> Error occurs when building libatomic on stage 3.
>>
>> If I change the '--enable-threads=win32' option on
>> '--enable-threads=posix' then it builds successfully.
>>
>>
>> configure: error: in
>> `/c/mingw520/i686-520-win32-sjlj-rt_v4-rev0/build/gcc-5.2.0/i686-w64-mingw32/64/libatomic':
>> configure: error: C compiler cannot create executables
>> See `config.log' for more details.
>>
>>
>> libatomic/config.log:
>> configure:3566: checking for C compiler default output file name
>> configure:3588:
>> /c/mingw520/i686-520-win32-sjlj-rt_v4-rev0/build/gcc-5.2.0/./gcc/xgcc
>> -B/c/mingw520/i686-520-win32-sjlj-rt_v4-rev0/build/gcc-5.2.0/./gcc/
>> -L/mingw32/i686-w64-mingw32/lib -L/mingw32/mingw/lib -isystem
>> /mingw32/i686-w64-mingw32/include -isystem /mingw32/mingw/include
>> -B/mingw32/i686-w64-mingw32/bin/ -B/mingw32/i686-w64-mingw32/lib/
>> -isystem /mingw32/i686-w64-mingw32/include -isystem
>> /mingw32/i686-w64-mingw32/sys-include -m64 -g -O2 -pipe
>> -I/c/mingw520/i686-520-win32-sjlj-rt_v4-rev0/mingw32/opt/include
>> -I/c/mingw520/prerequisites/i686-zlib-static/include
>> -I/c/mingw520/prerequisites/i686-w64-mingw32-static/include
>> -fno-sync-libcalls -march=i486 -mtune=i686 -fomit-frame-pointer
>> conftest.c >&5
>> conftest.c:1:0: error: CPU you selected does not support x86-64
>> instruction set
>>
>> As you can see here are simultaneously used the '-m64 -march=i486
>> -mtune=i686' options.
>>
>>
>> Question is, why and how can I fix it?
>
> This bug is also present in the gcc-trunk.
ping?
next prev parent reply other threads:[~2015-08-03 11:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 8:32 niXman
2015-08-02 11:37 ` niXman
2015-08-03 11:31 ` niXman [this message]
2015-08-03 15:51 ` Jonathan Wakely
2015-08-03 18:42 ` niXman
2015-08-04 9:28 ` Jonathan Wakely
2015-08-04 9:31 ` Jonathan Wakely
2015-08-23 9:39 ` niXman
2015-08-25 18:07 ` niXman
2015-08-27 11:42 ` niXman
2015-08-27 11:52 ` Jonathan Wakely
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=bd8a96cc95151bf879faf8320a7a520c@autistici.org \
--to=i.nixman@autistici.org \
--cc=gcc-help@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).