From: Mark Hatle <mark.hatle@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] How to deal allarch packages in dependency chain for multilib rootfs?
Date: Thu, 28 Jun 2018 09:26:42 -0500 [thread overview]
Message-ID: <fcd067d5-aac7-7819-a43b-23a2c5be217f@windriver.com> (raw)
In-Reply-To: <CANNYZj8ta8T25nAvb6tuaxx-==+j3DPCApXnA5JizihT5husJQ@mail.gmail.com>
On 6/28/18 6:20 AM, Alexander Kanavin wrote:
> Maybe the better thing to do would be to name the packages in the
> first place in such a way that openssl is a 32 bit package, and
> lib64-openssl is the 64 bit one. Then any noarch package would pull in
> the correct version automatically. Is that not possible somehow?
For an individual implementation, sure...
But for the general case, it really should not matter if it's 32-bit or 64-bit
version of OpenSSL. Both are 'functionally' equivalent.
--Mark
> Alex
>
> 2018-06-28 13:13 GMT+02:00 Martin Jansa <martin.jansa@gmail.com>:
>> In our build I've removed the openssl runtime dependency
>> (RDEPENDS_${PN}_remove = "openssl"), because we pull the right version of
>> openssl (lib32-openssl in our case) to the image elsewhere.
>>
>> On Thu, Jun 28, 2018 at 10:48 AM Kang Kai <Kai.Kang@windriver.com> wrote:
>>>
>>> Hi all,
>>>
>>> When build 32 bits rootfs with 64 bits bsp, if an allarch/noarch package
>>> is installed to lib32 rootfs, it causes
>>> unexpected 64 bits packages which is required by the allarch package
>>> installed to lib32 rootfs.
>>>
>>> Take ca-certificates as example. ca-certificates rdepends on openssl, so
>>> if ca-certificates is installed to image,
>>> 64 bits package openssl will be installed too no matter what the rootfs
>>> is. But only 32 bits openssl package should
>>> be installed to 32 bits rootfs.
>>>
>>> There are 2 ways to fixed the issue.
>>>
>>> 1 expand allarch/noarch packages with multilib. So if add ca-certificates
>>> to image, lib32-ca-certificates will be
>>> installed to 32bits rootfs. And then also the dependency lib32-openssl
>>> is installed. That is what we expected.
>>>
>>> 2 expand DEPENDS/RDEPENDS of allarch/noarch packages with a prefix
>>> 'noarch-' when multilib is enabled. So then
>>> ca-certificates requires 'noarch-openssl'. And make both lib32-openssl
>>> and openssl provides 'noarch-openssl'.
>>> When do_rootfs, there is only one rpm repo 'oe-rootfs-repo' now. We
>>> will create repos with different priorities
>>> according to different archs/subdirectories. For 32 bits image, make 32
>>> bits rpm repo has higher priority, so lib32-openssl
>>> will be installed to 32 bits rootfs rather than 64bits.
>>>
>>> I know these 2 ways are not perfect, but only possible ways I have in mind
>>> to solve the problem.
>>>
>>> Any comment or suggestion is greatly appreciated. Thanks a lot.
>>>
>>> --
>>> Regards,
>>> Neil | Kai Kang
>>>
>>> --
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
next prev parent reply other threads:[~2018-06-28 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 8:48 [RFC] How to deal allarch packages in dependency chain for multilib rootfs? Kang Kai
2018-06-28 11:13 ` Martin Jansa
2018-06-28 11:20 ` Alexander Kanavin
2018-06-28 14:26 ` Mark Hatle [this message]
2018-07-02 2:05 ` Kang Kai
2018-06-28 14:26 ` Mark Hatle
2018-07-02 8:50 ` Kang Kai
2018-07-17 20:21 ` Mark Hatle
2018-07-23 14:09 ` 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=fcd067d5-aac7-7819-a43b-23a2c5be217f@windriver.com \
--to=mark.hatle@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=martin.jansa@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.