From: Robert Yang <liezhi.yang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/6] Fixes for mutilib SDK
Date: Thu, 24 Sep 2015 14:29:42 +0800 [thread overview]
Message-ID: <56039856.3050902@windriver.com> (raw)
In-Reply-To: <1443045619.19044.40.camel@linuxfoundation.org>
On 09/24/2015 06:00 AM, Richard Purdie wrote:
> On Tue, 2015-09-22 at 10:45 +0800, Robert Yang wrote:
>> Hi RP and Ross,
>>
>> These patches are required by multilib's do_rootfs and do_populate_sdk,
>> otherwise they are broken or partly broken. These patches don't affect
>> do_rootfs or do_populate_sdk without multilib are to be installed.
>
> Thanks for these. Patches 1-4 look ok, we can try them in -next however
> I do worry about 5 and 6. Could you confirm if you tested those before
> or after the recent data store changes? Its possible the OVERRIDE fixes
> there may have fixed the issues 5 and 6 were trying to fix so I'd like
> to confirm if they're still needed or not.
>
> If they are, they don't look like the right solution so I'll need to
> look further at the exact issue there.
Hi RP,
I tested on latest master branch without patch 5 and 6, we still have
the issues.
# local.conf
MACHINE = "qemux86-64"
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
# populate sdk for lib32-core-image-minimal
$ bitbake lib32-core-image-minimal -cpopulate_sdk
# Install sdk
$
./tmp/deploy/sdk/poky-glibc-x86_64-lib32-core-image-minimal-core2-64-toolchain-1.8+snapshot.sh
# Check messages on the screen:
SDK has been successfully set up and is ready to be used.
Each time you wish to use the SDK in a new shell session, you need to source the
environment setup script e.g.
$ . /buildarea/lyang1/sdk32/environment-setup-core2-64-pokymllib32-linux
This is incorrect, it should be environment-setup-x86-pokymllib32-linuxm
(core2-64 != x86).
# Check the installed sdk, the sysroots are:
core2-64-pokymllib32-linux x86_64-pokysdk-linux
But SDKTARGETSYSROOT in environment-setup-core2-64-poky-linux and
environment-setup-x86-pokymllib32-linux is /path/to/sysroots/core2-64-poky-linux
, this is incorrect.
// Robert
>
> Cheers,
>
> Richard
>
>
next prev parent reply other threads:[~2015-09-24 6:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 2:04 [PATCH 0/6] Fixes for mutilib SDK Robert Yang
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 [this message]
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=56039856.3050902@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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