From: "Ryan Baldwin" <ryan.baldwin@nexusalpha.com>
To: <gentoo-embedded@lists.gentoo.org>
Subject: RE: [gentoo-embedded] C++ Exceptions Call Abort With Toolchain generated by crossdev
Date: Wed, 18 Oct 2006 18:16:49 +0100 [thread overview]
Message-ID: <0c8101c6f2d9$32b7f720$5b01a8c0@LXP0004> (raw)
In-Reply-To: <Pine.LNX.4.44.0610150945270.14269-100000@lnx.bridge.intra>
Hi,
I'll stick with --enable-sjlj-exceptions rather then switch gcc. Thanks for
letting me know.
Ryan
-----Original Message-----
From: Peter S. Mazinger [mailto:ps.m@gmx.net]
Sent: 15 October 2006 08:48
To: gentoo-embedded@lists.gentoo.org
Subject: RE: [gentoo-embedded] C++ Exceptions Call Abort With Toolchain
generated by crossdev
On Mon, 9 Oct 2006, Ryan Baldwin wrote:
> Hi,
>
> Thanks very much for the reply. I had managed to make it work by adding
> --enable-sjlj-exceptions into gcc's configure by adding it in
> toolchain.eclass. I guess then that the default mechanism works again in
> 3.4.6 so I will switch to this and remove --enable-sjlj-exceptions.
Stay with --enable-sjlj-exceptions for all 3.x versions, 3.4.6 needs it
too, it is not even proven, that 4.x versions can go without it.
Peter
--
Peter S. Mazinger <ps dot m at gmx dot net> ID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08 BB6E C389 975E A5F0 59F2
--
gentoo-embedded@gentoo.org mailing list
--
gentoo-embedded@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-18 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 10:35 [gentoo-embedded] C++ Exceptions Call Abort With Toolchain generated by crossdev Ryan Baldwin
2006-10-06 1:38 ` Mike Frysinger
2006-10-09 13:19 ` Ryan Baldwin
2006-10-15 7:47 ` Peter S. Mazinger
2006-10-16 9:13 ` [gentoo-embedded] GNAP & vmware-server-console Janusz Syrytczyk
2006-10-18 17:16 ` Ryan Baldwin [this message]
2006-10-19 18:35 ` [gentoo-embedded] crossdev messes up system headers, etc Christopher Friedt
2006-10-19 22:23 ` Mike Frysinger
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='0c8101c6f2d9$32b7f720$5b01a8c0@LXP0004' \
--to=ryan.baldwin@nexusalpha.com \
--cc=gentoo-embedded@lists.gentoo.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