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 8:55 AM, Mark Hatle <[email protected]> wrote:

From: "Roy.Li" <[email protected]>

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 applicable to the upstream as they do not
use libunwind.

Signed-off-by: Roy.Li <[email protected]>
Signed-off-by: Jeff Polk <[email protected]>
Signed-off-by: Mark Hatle <[email protected]>
---
meta/recipes-devtools/gcc/gcc_4.7.bb | 2 +-
meta/recipes-devtools/gcc/gcc_4.8.bb | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-devtools/gcc/gcc_4.7.bb 
b/meta/recipes-devtools/gcc/gcc_4.7.bb
index 9954375..f68c67a 100644
--- a/meta/recipes-devtools/gcc/gcc_4.7.bb
+++ b/meta/recipes-devtools/gcc/gcc_4.7.bb
@@ -2,4 +2,4 @@ require recipes-devtools/gcc/gcc-${PV}.inc
require gcc-configure-target.inc
require gcc-package-target.inc

-ARCH_FLAGS_FOR_TARGET += "-isystem${STAGING_INCDIR}"
+ARCH_FLAGS_FOR_TARGET += "-isystem${STAGING_INCDIR} -I${B}/gcc/include/ "
diff --git a/meta/recipes-devtools/gcc/gcc_4.8.bb 
b/meta/recipes-devtools/gcc/gcc_4.8.bb
index 9954375..f68c67a 100644
--- a/meta/recipes-devtools/gcc/gcc_4.8.bb
+++ b/meta/recipes-devtools/gcc/gcc_4.8.bb
@@ -2,4 +2,4 @@ require recipes-devtools/gcc/gcc-${PV}.inc
require gcc-configure-target.inc
require gcc-package-target.inc

-ARCH_FLAGS_FOR_TARGET += "-isystem${STAGING_INCDIR}"
+ARCH_FLAGS_FOR_TARGET += "-isystem${STAGING_INCDIR} -I${B}/gcc/include/ "
--
1.8.3.rc1.25.g423ecb0

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core


_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to