From: JonY <jon_y@users.sourceforge.net>
To: gcc-help@gcc.gnu.org
Subject: Re: trunk build error after revision 189603
Date: Mon, 20 Aug 2012 05:47:00 -0000 [thread overview]
Message-ID: <5031AC50.3020604@users.sourceforge.net> (raw)
In-Reply-To: <CAMPTgK3TYd4i0_Sc-z1PfZNKDjNCR+d97nz6tKoLSdOaJLbC1g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
On 8/20/2012 00:16, niXman wrote:
> Hi,
>
> I regularly build MinGW within the MinGW-builds project [1].
> I build releases, brunches and snapshots.
> I have a problem with the building of trunk. Last successfully built
> revision was 189603.
>
> Now, when trying to build trunk, I get the following error:
>> gcc-trunk/libgcc/unwind-c.c: In function '__gcc_personality_seh0':
>> gcc-trunk/libgcc/unwind-c.c:242:14: error: '__gcc_personality_imp' undeclared (first use in this function)
>
> The arguments / configuration options - were not changed. Trunk simply
> stopped to build. The brunches are built successfully.
>
> I suppose that the error had appeared due to the use of this [2] patch.
>
> Any ideas?
>
>
>
> [1] http://sourceforge.net/projects/mingwbuilds/
> [2] http://gcc.gnu.org/ml/gcc-patches/2012-07/msg00512.html
>
>
Are you building for win64 target? If so, you can remove the
--enable-sjlj-exceptions or --disable-sjlj-exceptions option.
win32 target builds should be unaffected.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 196 bytes --]
next prev parent reply other threads:[~2012-08-20 3:18 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 [this message]
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
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=5031AC50.3020604@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).