From: niXman <i.nixman@gmail.com>
To: JonY <jon_y@users.sourceforge.net>, gcc-help@gcc.gnu.org
Subject: Re: trunk build error after revision 189603
Date: Tue, 21 Aug 2012 11:30:00 -0000 [thread overview]
Message-ID: <CAMPTgK0GctwQk5nefiYZ4FN=pn2v+BwpKCcdebuvyD6su9rCqA@mail.gmail.com> (raw)
In-Reply-To: <5032EE9B.3040909@users.sourceforge.net>
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?
--
Regards,
niXman
___________________________________________________
Dual-target(32 & 64 bit) MinGW compilers for 32 and 64 bit Windows:
http://sourceforge.net/projects/mingwbuilds/
next prev parent reply other threads:[~2012-08-21 10:02 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 [this message]
2012-08-21 13:35 ` JonY
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='CAMPTgK0GctwQk5nefiYZ4FN=pn2v+BwpKCcdebuvyD6su9rCqA@mail.gmail.com' \
--to=i.nixman@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jon_y@users.sourceforge.net \
/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).