Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Xulin Sun <xulin.sun@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: xulin.sun@windriver.com
Subject: [meta-oe][PATCH] openssl: fix multilib file install conflicts
Date: Fri, 18 Jan 2019 10:22:48 +0800	[thread overview]
Message-ID: <20190118022248.17108-1-xulin.sun@windriver.com> (raw)

To avoid issue like below if run "bitbake lib32-wrlinux-image-glibc-std"
with series userspace packages(LAMP,krb5...) added:

Error: Transaction check error:
  file /usr/bin/c_rehash conflicts between attempted installs of
  lib32-openssl-bin-1.1.1-r0.armv7at2hf_neon and openssl-bin-1.1.1-r0.aarch64

Signed-off-by: Xulin Sun <xulin.sun@windriver.com>
---
 meta/recipes-connectivity/openssl/openssl_1.1.1a.bb | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1a.bb b/meta/recipes-connectivity/openssl/openssl_1.1.1a.bb
index 5c4e69cfb7..21359fa68a 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.1.1a.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.1.1a.bb
@@ -206,3 +206,7 @@ RREPLACES_openssl-conf = "openssl10-conf"
 RCONFLICTS_openssl-conf = "openssl10-conf"
 
 BBCLASSEXTEND = "native nativesdk"
+
+inherit multilib_script
+
+MULTILIB_SCRIPTS = "${PN}:${bindir}/c_rehash"
-- 
2.18.1



             reply	other threads:[~2019-01-18  2:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18  2:22 Xulin Sun [this message]
2019-01-21 23:00 ` [meta-oe][PATCH] openssl: fix multilib file install conflicts Randy MacLeod
2019-01-22 14:25   ` Peter Kjellerstedt
2019-01-23  9:31     ` Xulin Sun
2019-01-22  3:03 ` [meta-oe][PATCH v2] " Xulin Sun
2019-01-26 23:15   ` Richard Purdie
2019-01-28  1:41     ` Xulin Sun
2019-01-29  7:31 ` [meta-oe][PATCH v3] " Xulin Sun

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=20190118022248.17108-1-xulin.sun@windriver.com \
    --to=xulin.sun@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