On 6/10/13 7:21 PM, Khem Raj 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?
--Mark
On May 31, 2013, at
On Jun 11, 2013, at 9:13 AM, Mark Hatle mark.ha...@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
On Tue, 11 Jun 2013 10:11:46 -0700
Khem Raj raj.k...@gmail.com wrote:
On Jun 11, 2013, at 9:13 AM, Mark Hatle mark.ha...@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
what happens if you use --disable-libunwind-exceptions
On May 31, 2013, at 8:55 AM, Mark Hatle mark.ha...@windriver.com wrote:
From: Roy.Li rongqing...@windriver.com
Add build directory to include directories by -I${B}/include which will
be searched before standard system include
From: Roy.Li rongqing...@windriver.com
Add build directory to include directories by -I${B}/include which will
be searched before standard system include directories.
Both libunwind and gcc supply unwind.h, once gcc use libunwind's unwind.h,
the compiling will fail.
This patch is generally not
