From: JonY <jon_y@users.sourceforge.net>
To: gcc-help@gcc.gnu.org
Subject: Re: trunk build error after revision 189603
Date: Tue, 21 Aug 2012 13:35:00 -0000 [thread overview]
Message-ID: <503363A7.4000405@users.sourceforge.net> (raw)
In-Reply-To: <CAMPTgK0GctwQk5nefiYZ4FN=pn2v+BwpKCcdebuvyD6su9rCqA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
On 8/21/2012 18:01, niXman wrote:
> 2012/8/21 JonY:
>> BTW, leaving --enable-sjlj-exceptions or --disable-sjlj-exceptions
>> should leave you sjlj EH build for win32 target, I'm not getting those
>> errors you described.
>>
>
> Prompt to me please, with what arguments you run configure?
>
>
>
gcc-trunk/configure --prefix=/opt/mingw64_64_48 --with-sysroot=/opt/mingw64_64_48 --with-build-sysroot=/opt/mingw64_64_48 --enable-multilib --enable-targets=all --disable-win32-registry --enable-languages=c,ada,c++,fortran,objc,obj-c++ --enable-fully-dynamic-string --enable-libgomp --enable-version-specific-runtime-libs --with-dwarf2 --enable-decimal-float=bid --enable-lto --enable-graphite --enable-long-long --enable-c99 --enable-wchar_t --with-gnu-ld --with-gnu-as --with-arch=corei7-avx --with-tune=corei7-avx --with-gmp=/opt/support --with-mpfr=/opt/support --with-isl=/opt/support --with-cloog=/opt/support --with-mpc=/opt/support --enable-version-specific-runtime-libs --enable-cloog-backend=isl --enable-checking=no --build=i686-pc-cygwin --host=i686-pc-cygwin --target=x86_64-w64-mingw32 -C
No errors in the win32 part, it uses SJLJ as usual. So omit the
x86_64-w64-mingw32 parts for their equivalent and disable multilib
if you want to use a simple win32 only target GCC.
The only hack I needed is to use a linker script to fix up some
static support libs.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 196 bytes --]
next prev parent reply other threads:[~2012-08-21 10:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 3:18 niXman
2012-08-20 5:47 ` JonY
2012-08-20 13:25 ` niXman
2012-08-21 2:13 ` niXman
2012-08-21 10:02 ` JonY
2012-08-21 11:30 ` niXman
2012-08-21 13:35 ` JonY [this message]
2012-08-21 17:41 ` niXman
2012-08-22 11:11 ` JonY
2012-08-22 13:06 ` niXman
2012-08-22 13:44 ` JonY
2012-09-05 9:15 ` niXman
2012-09-05 9:31 ` JonY
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=503363A7.4000405@users.sourceforge.net \
--to=jon_y@users.sourceforge.net \
--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).