From: Mark Hatle <mark.hatle@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 09:13:30 -0700 [thread overview]
Message-ID: <51B74CAA.9060203@windriver.com> (raw)
In-Reply-To: <7FC71AE1-8B85-4A2C-8E5D-A8A29DF05193@gmail.com>
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
>
next prev parent reply other threads:[~2013-06-11 16:13 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 [this message]
2013-06-11 17:11 ` Khem Raj
2013-06-11 22:42 ` Peter Seebach
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=51B74CAA.9060203@windriver.com \
--to=mark.hatle@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 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.