All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2]native recipes:add option march to BUILD_CFLAGS
Date: Wed, 9 Jan 2013 16:46:45 +0800	[thread overview]
Message-ID: <cover.1357719953.git.hongxu.jia@windriver.com> (raw)

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.

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. The glib-2.0-native and qemu-native
need to be fixed.

[YOCTO #3563]

The following changes since commit 7e1f8faad0c4b6f490c26f87acc698dd6e002b15:

  perl: Remove bashism from perl-tests.inc (2013-01-07 22:37:37 +0000)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib hongxu/glib-2.0-native
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/glib-2.0-native

Hongxu Jia (2):
  glib-2.0-native:add option march to BUILD_CFLAGS
  qemu-native:add option march to BUILD_CFLAGS

 meta/recipes-core/glib-2.0/glib-2.0_2.34.3.bb |    7 ++++++-
 meta/recipes-devtools/qemu/qemu.inc           |    5 +++++
 2 files changed, 11 insertions(+), 1 deletion(-)

-- 
1.7.10.4




             reply	other threads:[~2013-01-09  9:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09  8:46 Hongxu Jia [this message]
2013-01-09  8:46 ` [PATCH 1/2] glib-2.0-native:add option march to BUILD_CFLAGS Hongxu Jia
2013-01-09  8:46 ` [PATCH 2/2] qemu-native:add " Hongxu Jia
2013-01-09  8:50   ` Burton, Ross
2013-01-09  8:58     ` 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=cover.1357719953.git.hongxu.jia@windriver.com \
    --to=hongxu.jia@windriver.com \
    --cc=openembedded-core@lists.openembedded.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 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.