From: Hongxu Jia <hongxu.jia@windriver.com>
To: Colin Walters <walters@verbum.org>,
Robert Yang <liezhi.yang@windriver.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] glib-2.0-native:add option march to BUILD_CFLAGS
Date: Wed, 9 Jan 2013 16:23:52 +0800 [thread overview]
Message-ID: <50ED2918.1070005@windriver.com> (raw)
In-Reply-To: <1357496896.8239.0.camel@localhost>
On 01/07/2013 02:28 AM, Colin Walters wrote:
> On Sun, 2013-01-06 at 16:34 +0800, Hongxu Jia wrote:
>
>> +# Add option -march to BUILD_CFLAGS in order to let the atomic operations
>> +# ("lock free") be available while using old version GCC on x86 host to
>> +# compile glib-2.0-native
>> +BUILD_CFLAGS += "-march=${@'${BUILD_ARCH}'.replace('_','-')}"
> Shouldn't this be handled more generically for all native recipes?
>
>
Hi Colin,
I have a fully test and the qemu-native has the similar problem, and I will
resend the patch.
It's a bad idea to modify bitbake.conf to add option -march to BUILD_CFLAGS,
because it's global and its side effect is unknown, such as beecrypt-native
do_compile will fail if we do that.
So it's best to test most of the native recipes to have a check about
the similar
problem and fix them separately, and the packagegroup-toolset-native.bb
could work for that.
Regards,
Hongxu
next prev parent reply other threads:[~2013-01-09 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 8:34 [PATCH 0/1] glib-2.0-native:add option march to BUILD_CFLAGS Hongxu Jia
2013-01-06 8:34 ` [PATCH 1/1] " Hongxu Jia
2013-01-06 18:28 ` Colin Walters
2013-01-09 8:23 ` Hongxu Jia [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-20 8:10 [PATCH 0/1]glib-2.0-native:add " Hongxu Jia
2012-12-20 8:10 ` [PATCH 1/1] glib-2.0-native:add " Hongxu Jia
2012-12-20 10:05 ` Burton, Ross
2013-01-05 2:40 ` Hongxu Jia
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=50ED2918.1070005@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=walters@verbum.org \
/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