Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Xulin Sun <xulin.sun@windriver.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
	Randy MacLeod <randy.macleod@windriver.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] openssl: fix multilib file install conflicts
Date: Wed, 23 Jan 2019 17:31:28 +0800	[thread overview]
Message-ID: <f28ea34b-b4b2-d850-d6cf-6ebb8eeec732@windriver.com> (raw)
In-Reply-To: <4693588ff8f849cfac2242d5323e9012@XBOX04.axis.com>



On 01/22/2019 10:25 PM, Peter Kjellerstedt wrote:
>> -----Original Message-----
>> From: openembedded-core-bounces@lists.openembedded.org <openembedded-
>> core-bounces@lists.openembedded.org> On Behalf Of Randy MacLeod
>> Sent: den 22 januari 2019 00:01
>> To: Patches and discussions about the oe-core layer <openembedded-
>> core@lists.openembedded.org>; Xulin Sun <xulin.sun@windriver.com>
>> Subject: Re: [OE-core] [meta-oe][PATCH] openssl: fix multilib file
>> install conflicts
>>
>> Xulin,
>>
>> Thanks for sending this patch.
>>
>> On 1/17/19 9:22 PM, Xulin Sun wrote:
>>> To avoid issue like below if run "bitbake lib32-wrlinux-image-glibc-
>> std"
>>
>> For future oe-core commits, please use a core-image-minimal
>> example that will be more familiar to people outside of Wind River.
>>
>>> 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
>> Also, while your commit log explains what you fixed, it
>> doesn't describe the issue for those who don't know what c_rehash is so
>> something like:
>>
>>     Add multilib_script support for openssl's c_rehash which is
>>     a perl script.
>>
>> Followed by the example failure log that you showed.
>>
>>
>> Since this hasn't been merged to master/master-next,
>> it would be nice if you sent a v2.
>>
>> Thanks,
>> ../Randy
>>
>>> 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"
> Shouldn't that be:
>
> MULTILIB_SCRIPTS = "${PN}-bin:${bindir}/c_rehash"
>
> given that openssl inherits lib_package and ${bindir}/c_rehash thus
> ends up in the ${PN}-bin package?

It is verified that both these two modification method ( ${PN}  or 
${PN}-bin ) are all working and can fix the building error issue.
Seems that after update to openssl 1.1.1, the file /usr/bin/openssl is 
packaged into openssl-bin.

Thanks
Xulin
>
> //Peter
>
>



  reply	other threads:[~2019-01-23  9:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18  2:22 [meta-oe][PATCH] openssl: fix multilib file install conflicts Xulin Sun
2019-01-21 23:00 ` Randy MacLeod
2019-01-22 14:25   ` Peter Kjellerstedt
2019-01-23  9:31     ` Xulin Sun [this message]
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=f28ea34b-b4b2-d850-d6cf-6ebb8eeec732@windriver.com \
    --to=xulin.sun@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.com \
    --cc=randy.macleod@windriver.com \
    /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