From: Peter Seebach <peter.seebach@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] gcc: add build directory to include directories
Date: Tue, 11 Jun 2013 17:42:36 -0500 [thread overview]
Message-ID: <20130611174236.758b403c@e6410-2> (raw)
In-Reply-To: <2CF72E14-1BCC-4CCC-8F98-8818788D95DA@gmail.com>
On Tue, 11 Jun 2013 10:11:46 -0700
Khem Raj <raj.khem@gmail.com> wrote:
> On Jun 11, 2013, at 9:13 AM, Mark Hatle <mark.hatle@windriver.com> wrote:
>
> >> what happens if you use --disable-libunwind-exceptions
> >
> > As far as I know we have not tried that. Doesn't this change some of the processing though for systems that use unwind as the only way to generate proper back traces?
>
> we already disable it for gcc-runtime and libgcc recipes where it would matter too.
For what it's worth, --disable-libunwind-exceptions doesn't seem to prevent
the failure.
In file included from /home/seebs/tct/t00/bitbake_build/tmp/work-shared/gcc-4.8.
0-r0/gcc-4.8.0/libstdc++-v3/libsupc++/eh_arm.cc:26:0:
/home/seebs/tct/t00/bitbake_build/tmp/work-shared/gcc-4.8.0-r0/gcc-4.8.0/libstdc
++-v3/libsupc++/unwind-cxx.h:92:3: error: '_Unwind_Ptr' does not name a type
[... and many, many, more]
This appears to be identical to what we get without
--disable-libunwind-exceptions. It may be that that isn't fully implemented
for libsupc++.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
prev parent reply other threads:[~2013-06-11 22:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 15:55 [PATCH v2] gcc: add build directory to include directories Mark Hatle
2013-06-11 2:21 ` Khem Raj
2013-06-11 16:13 ` Mark Hatle
2013-06-11 17:11 ` Khem Raj
2013-06-11 22:42 ` Peter Seebach [this message]
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=20130611174236.758b403c@e6410-2 \
--to=peter.seebach@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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