From: richard.purdie@linuxfoundation.org
To: kai.kang@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] allarch: disable allarch when multilib is used
Date: Fri, 10 Aug 2018 10:24:21 +0100 [thread overview]
Message-ID: <fdafcc6cdd7abfa519ae59df871a844a07103e3f.camel@linuxfoundation.org> (raw)
In-Reply-To: <8aa373833d3e5f54689b8863f864c39dc90e5cab.1533888808.git.kai.kang@windriver.com>
On Fri, 2018-08-10 at 16:14 +0800, kai.kang@windriver.com wrote:
> From: Kai Kang <kai.kang@windriver.com>
>
> Some allarch packages rdepends non-allarch packages. When multilib is
> used, it doesn't expand the dependency chain correctly, e.g.
>
> core-image-sato -> ca-certificates(allarch) -> openssl
>
> we expect dependency chain for lib32-core-image-sato:
>
> lib32-core-image-sato -> ca-certificates(allarch) -> lib32-openssl
>
> it should install lib32-openssl for ca-certificates but openssl is
> still wrongly imported.
>
> Disable allarch when multilib is used.
>
> Signed-off-by: Kai Kang <kai.kang@windriver.com>
> ---
> meta/classes/allarch.bbclass | 4 ++++
> meta/classes/icecc.bbclass | 2 +-
> meta/classes/multilib.bbclass | 3 ++-
> meta/classes/multilib_global.bbclass | 4 +---
> meta/classes/package.bbclass | 9 ++++++---
> meta/classes/staging.bbclass | 2 +-
> 6 files changed, 15 insertions(+), 9 deletions(-)
Looks good at a quick glance, I'll put it in for testing.
Since I just saw it for other reasons, could you also see if we could
remove the ${DEPLOY_DIR_RPM}/noarch/ mentioned as:
# For multilib rpm the allarch packagegroup files can overwrite (in theory they're identical)
SSTATE_DUPWHITELIST = "${DEPLOY_DIR}/licenses/ ${DEPLOY_DIR_RPM}/noarch/"
from sstate.bbclass please?
Cheers,
Richard
next prev parent reply other threads:[~2018-08-10 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 8:14 [PATCH 0/1] allarch: disable allarch when multilib is used kai.kang
2018-08-10 8:14 ` [PATCH 1/1] " kai.kang
2018-08-10 9:24 ` richard.purdie [this message]
2018-08-10 14:20 ` Kang Kai
2018-08-11 16:10 ` richard.purdie
2018-08-14 9:40 ` Kang Kai
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=fdafcc6cdd7abfa519ae59df871a844a07103e3f.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=kai.kang@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