From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: qingtao.cao@windriver.com
Subject: [PATCH V4 0/1]fix native package compile error with gcc 4.3.4 on x86 host
Date: Tue, 5 Mar 2013 10:50:14 +0800 [thread overview]
Message-ID: <cover.1362398320.git.hongxu.jia@windriver.com> (raw)
Change from V3: as Richard suggested, patch sanity.bbclass to test if necessary
to add march to BUILD_CFLAG when the gcc version is older than 4.5
Test case:
:~> bitbake packagegroup-toolset-native
WARNING: Host distribution "SUSE Linux Enterprise Desktop 11" has not been
validated with this version of the build system; you may possibly experience
unexpected failures. It is recommended that you use a tested distribution.
ERROR: OE-core's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker(see sanity.conf).
Following is the list of potential problems / advisories:
Your gcc version is older than 4.5, please add the following param to local.conf
BUILD_CFLAGS_append = " -march=native"
[YOCTO #3563]
The following changes since commit 7ed45239631796086c78546776096f62ea090718:
bitbake: siggen: add quotes around variable values to see whitespace (2013-03-04 11:38:30 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib hongxu/sanity-check-march
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/sanity-check-march
Hongxu Jia (1):
sanity.bbclass:check if necessary to add march to BUILD_CFLAGS
meta/classes/sanity.bbclass | 29 +++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
--
1.7.10.4
next reply other threads:[~2013-03-05 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 2:50 Hongxu Jia [this message]
2013-03-05 2:50 ` [PATCH 1/1] sanity.bbclass:check if necessary to add march to BUILD_CFLAGS 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.1362398320.git.hongxu.jia@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=qingtao.cao@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox