All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH v2] gcc: add build directory to include directories
@ 2013-05-31 15:55 Mark Hatle
  2013-06-11  2:21 ` Khem Raj
  0 siblings, 1 reply; 5+ messages in thread
From: Mark Hatle @ 2013-05-31 15:55 UTC (permalink / raw)
  To: openembedded-core

From: "Roy.Li" <rongqing.li@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 applicable to the upstream as they do not
use libunwind.

Signed-off-by: Roy.Li <rongqing.li@windriver.com>
Signed-off-by: Jeff Polk <jeff.polk@windriver.com>
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
---
 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



^ permalink raw reply related	[flat|nested] 5+ messages in thread

* Re: [PATCH v2] gcc: add build directory to include directories
  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
  0 siblings, 1 reply; 5+ messages in thread
From: Khem Raj @ 2013-06-11  2:21 UTC (permalink / raw)
  To: Mark Hatle; +Cc: openembedded-core

what happens if you use --disable-libunwind-exceptions

On May 31, 2013, at 8:55 AM, Mark Hatle <mark.hatle@windriver.com> wrote:

> From: "Roy.Li" <rongqing.li@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 applicable to the upstream as they do not
> use libunwind.
> 
> Signed-off-by: Roy.Li <rongqing.li@windriver.com>
> Signed-off-by: Jeff Polk <jeff.polk@windriver.com>
> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
> ---
> 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
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH v2] gcc: add build directory to include directories
  2013-06-11  2:21 ` Khem Raj
@ 2013-06-11 16:13   ` Mark Hatle
  2013-06-11 17:11     ` Khem Raj
  0 siblings, 1 reply; 5+ messages in thread
From: Mark Hatle @ 2013-06-11 16:13 UTC (permalink / raw)
  To: Khem Raj; +Cc: openembedded-core

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 <mark.hatle@windriver.com> wrote:
>
>> From: "Roy.Li" <rongqing.li@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 applicable to the upstream as they do not
>> use libunwind.
>>
>> Signed-off-by: Roy.Li <rongqing.li@windriver.com>
>> Signed-off-by: Jeff Polk <jeff.polk@windriver.com>
>> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
>> ---
>> 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
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH v2] gcc: add build directory to include directories
  2013-06-11 16:13   ` Mark Hatle
@ 2013-06-11 17:11     ` Khem Raj
  2013-06-11 22:42       ` Peter Seebach
  0 siblings, 1 reply; 5+ messages in thread
From: Khem Raj @ 2013-06-11 17:11 UTC (permalink / raw)
  To: Mark Hatle; +Cc: openembedded-core


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.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH v2] gcc: add build directory to include directories
  2013-06-11 17:11     ` Khem Raj
@ 2013-06-11 22:42       ` Peter Seebach
  0 siblings, 0 replies; 5+ messages in thread
From: Peter Seebach @ 2013-06-11 22:42 UTC (permalink / raw)
  To: Khem Raj; +Cc: openembedded-core

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.


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2013-06-11 22:42 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.