From: Mark Hatle <mark.hatle@windriver.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: RFC - multilib SDK patches
Date: Wed, 26 Sep 2012 18:21:44 -0500 [thread overview]
Message-ID: <50638E08.8060009@windriver.com> (raw)
I created a patch set to enable multilib userspace in an SDK. I've pushed the
patches to:
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=mhatle/multilib
(they are based on oe-core)
I'd like some comments on them and see if they are reasonable or not. With the
patches I was able to configure my local.conf with:
MACHINE = "qemux86-64"
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
IMAGE_INSTALL_append = ' lib32-eglibc'
TOOLCHAIN_HOST_TASK = "nativesdk-packagegroup-sdk-host"
TOOLCHAIN_HOST_TASK += "packagegroup-cross-canadian-${@'
packagegroup-cross-canadian-'.join(all_multilib_tune_values(d,
'TRANSLATED_TARGET_ARCH').split())}"
---
Then built an SDK using:
bitbake core-image-minimal -c populate_sdk
---
Note, the top patch is a nasty hack to perl. I don't have any idea as to what
is going wrong, but nativesdk-perl has decided to install into the wrong place
on my machine. I was wondering if other people are seeing the same problem or not.
Any comments would be appreciated.
--Mark
reply other threads:[~2012-09-26 23:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50638E08.8060009@windriver.com \
--to=mark.hatle@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.