From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/6] Fixes for mutilib SDK
Date: Tue, 15 Sep 2015 19:04:08 -0700 [thread overview]
Message-ID: <cover.1442311946.git.liezhi.yang@windriver.com> (raw)
* This fixed:
MACHINE = "qemux86-64"
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
$ bitbake core-image-minimal -cpopulate_sdk
Install poky-glibc-x86_64-core-image-minimal-core2-64-toolchain-1.8+snapshot.sh,
then source environment-setup-core2-64-pokymllib32-linux or
environment-setup-core2-64-poky-linux, both of them will compile hello.c
well. (The 32bit was broken in the past)
$ bitbake lib32-core-image-minimal -cpopulate_sdk
Install poky-glibc-x86_64-lib32-core-image-minimal-core2-64-toolchain-1.8+snapshot.sh,
then source environment-setup-core2-64-poky-linux or
environment-setup-core2-64-pokymllib32-linux, both of them will compile
hello.c well (neither of them worked in the past)
This also fixed the problem that not all dependencies mutilib packages
are installed, please see:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4408
Tested:
$ bitbake core-image-minimal core-image-sato -cpopulate_sdk && bitbake core-image-sato-sdk world core-image-minimal core-image-sato
// Robert
The following changes since commit f0189829498e30231d826c9f55aad73e622d076e:
qemu: Update to upstream patches (2015-09-14 11:22:02 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/sdk
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/sdk
Robert Yang (6):
toolchain-shar-extract.sh: remove checkbashism
oe-pkgdata-util: avoid returning skipped packages
package_manager.py: make rpm install mutilib pkgs corectly
multilib.bbclass: install all bits toochains when populate mlprefix
SDK
populate_sdk_base.bbclass: fix SDKTARGETSYSROOT when populate
mlprefix SDK
meta-environment.bb: fix environment-setup* when populate mlprefix
SDK
meta/classes/multilib.bbclass | 15 +++++
meta/classes/populate_sdk_base.bbclass | 6 +-
meta/files/toolchain-shar-extract.sh | 4 +-
meta/lib/oe/package_manager.py | 83 +++++++++++++++++++++++++++-
meta/recipes-core/meta/meta-environment.bb | 4 ++
scripts/oe-pkgdata-util | 5 +-
6 files changed, 111 insertions(+), 6 deletions(-)
--
1.7.9.5
next reply other threads:[~2015-09-16 2:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 2:04 Robert Yang [this message]
2015-09-16 2:04 ` [PATCH 1/6] toolchain-shar-extract.sh: remove checkbashism Robert Yang
2015-09-16 2:04 ` [PATCH 2/6] oe-pkgdata-util: avoid returning skipped packages Robert Yang
2015-09-16 2:04 ` [PATCH 3/6] package_manager.py: make rpm install mutilib pkgs corectly Robert Yang
2015-09-16 2:04 ` [PATCH 4/6] multilib.bbclass: install all bits toochains when populate mlprefix SDK Robert Yang
2015-09-16 2:04 ` [PATCH 5/6] populate_sdk_base.bbclass: fix SDKTARGETSYSROOT " Robert Yang
2015-09-16 2:04 ` [PATCH 6/6] meta-environment.bb: fix environment-setup* " Robert Yang
2015-09-16 2:08 ` [PATCH 0/6] Fixes for mutilib SDK Robert Yang
2015-09-22 2:45 ` Robert Yang
2015-09-23 22:00 ` Richard Purdie
2015-09-24 6:29 ` Robert Yang
2015-09-24 9:18 ` Richard Purdie
2015-09-24 11:29 ` Robert Yang
2015-09-24 16:31 ` Burton, Ross
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.1442311946.git.liezhi.yang@windriver.com \
--to=liezhi.yang@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.