From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] staging.bbclass: avoid staging native components for target sysroot
Date: Thu, 6 Sep 2018 14:41:54 +0800 [thread overview]
Message-ID: <52ec79b4-4215-827a-2e3e-654fdd2ed722@windriver.com> (raw)
In-Reply-To: <109a0b6ce47245c63976bccef4258160a96197c5.1535359523.git.Qi.Chen@windriver.com>
ping
On 08/27/2018 04:46 PM, Chen Qi wrote:
> In the staging_populate_sysroot_dir function, components are staged
> by pkgarch matching. In case of x86-64 targets, it's possible that
> the native components are also matched, and thus are expectedly installed.
>
> The negative effect is at least unnecessary installation, and in some
> cases is compilation error. For example, when using eSDK and we are trying
> to cross compile some project in lib32 environment, the compilation will
> fail.
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
> meta/classes/staging.bbclass | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta/classes/staging.bbclass b/meta/classes/staging.bbclass
> index 27b012e..1b9803a 100644
> --- a/meta/classes/staging.bbclass
> +++ b/meta/classes/staging.bbclass
> @@ -198,6 +198,9 @@ def staging_populate_sysroot_dir(targetsysroot, nativesysroot, native, d):
> if manifest.endswith("-initial.populate_sysroot"):
> # skip glibc-initial and libgcc-initial due to file overlap
> continue
> + if not native and manifest.endswith("-native.populate_sysroot"):
> + # avoid native components to be installed into target sysroot
> + continue
> tmanifest = targetdir + "/" + os.path.basename(manifest)
> if os.path.exists(tmanifest):
> continue
prev parent reply other threads:[~2018-09-06 6:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 8:46 [PATCH 0/1] staging.bbclass: avoid staging native components for target sysroot Chen Qi
2018-08-27 8:46 ` [PATCH 1/1] " Chen Qi
2018-09-06 6:41 ` ChenQi [this message]
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=52ec79b4-4215-827a-2e3e-654fdd2ed722@windriver.com \
--to=qi.chen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox