All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rudolf J Streif <rudolf.streif@ibeeto.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Yocto <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Force binary package install
Date: Tue, 7 Jun 2022 15:48:10 -0700	[thread overview]
Message-ID: <9bd2408c-3309-11e6-2bba-37f69d90e4e2@ibeeto.com> (raw)
In-Reply-To: <CANNYZj8=dJ2Eiabx6FEykafYgSUzokg08sPiLW6X-=uJAeZnvA@mail.gmail.com>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 6863 bytes --]


On 6/7/22 3:12 PM, Alexander Kanavin wrote:
> Can you drop insane_skip for a moment and show what errors then happen?


Yes, thank you.

ERROR: xxx-single-group-0.1-r0 do_package_qa: QA Issue: 
/opt/binstuf/linux-allwinneryocto-armle-opengles_2.0-obj/lib/libfbxsdk.so 
contained in package xxx-single-group requires 
libpthread.so.0(GLIBC_2.2), but no providers found in 
RDEPENDS:xxx-single-group? [file-rdeps]

There are many more of these errors.


Objdump on libfbxsdk.so:

Version References:
   required from libgcc_s.so.1:
     0x0b792650 0x00 12 GCC_3.0
   required from libpthread.so.0:
     0x0d696912 0x00 10 GLIBC_2.2
     0x09691972 0x00 07 GLIBC_2.3.2
     0x0d696911 0x00 05 GLIBC_2.1
     0x0d696910 0x00 03 GLIBC_2.0
   required from libc.so.6:
     0x0d696912 0x00 11 GLIBC_2.2
     0x0d696917 0x00 09 GLIBC_2.7
     0x0d696911 0x00 08 GLIBC_2.1
     0x0d696913 0x00 06 GLIBC_2.3
     0x09691f73 0x00 04 GLIBC_2.1.3
     0x0d696910 0x00 02 GLIBC_2.0

Objdump on libpthread.so.0:

Version definitions:
1 0x01 0x0e2f2c50 libpthread.so.0
2 0x00 0x06969197 GLIBC_2.17
3 0x00 0x06969198 GLIBC_2.18
         GLIBC_2.17
4 0x00 0x06969188 GLIBC_2.28
         GLIBC_2.18
5 0x00 0x069691b0 GLIBC_2.30
         GLIBC_2.28
6 0x00 0x069691b1 GLIBC_2.31
         GLIBC_2.30


The versions don't match hence dnf throws an error. I guess I can defer 
the error with INSANE_SKIP += "file-rdeps" but then it comes up again 
when installing.


>
> Alex
>
> On Tue 7. Jun 2022 at 22.57, Rudolf J Streif <rudolf.streif@ibeeto.com 
> <mailto:rudolf.streif@ibeeto.com>> wrote:
>
>
>     On 6/7/22 12:44 PM, Alexander Kanavin wrote:
>     > Can you show the recipe that you wrote for the blob?
>
>     Not exactly as is because of customer names, but below is a sanitized
>     version:
>
>
>     SUMMARY = "Binary Stuff"
>
>     LICENSE = "CLOSED"
>
>     SRC_URI = "file://binary_installer.tgz \
>                "
>
>     do_install() {
>
>          install -d -m 0755 ${D}/opt/binstuff
>
>          tar cf - -C ${WORKDIR}/opt/binstuff . | tar xf - -C ${D}/binstuff
>
>     }
>
>     FILES:${PN} = "/opt/binstuff"
>
>
>     RDEPENDS:${PN} += "libsystemd libudev libgpiod wayland"
>     INSANE_SKIP:${PN} += "ldflags file-rdeps arch staticdev"
>
>     The recipe itself builds just fine and creates the RPM package.
>     However,
>     the some of the binaries inside the package have been built against
>     shared libs of older versions. The libs are there of course but
>     with the
>     wrong version. Adding file-rdeps to INSANE_SKIP addresses this at
>     build
>     time. But when installing the package in the rootfs dnf does a
>     dependency check which then fails.
>
>     I don't know if there is an elegant way of overriding dnf to force
>     installation of the package.
>
>
>     >
>     > Alex
>     >
>     > On Tue, 7 Jun 2022 at 20:59, Rudolf J Streif
>     <rudolf.streif@ibeeto.com <mailto:rudolf.streif@ibeeto.com>> wrote:
>     >> I have been handed a binary package that I am integrating into
>     a Yocto
>     >> build.
>     >>
>     >> When dnf runs it complains about missing dependencies. These are
>     >> standard libraries of course but the culprit is the incompatible
>     >> version. The software runs fine when I install it on the target
>     using
>     >> the script/tar installation it comes with. Needless to say that YP
>     >> packaging QA complains about this already when assembling the
>     package.
>     >> However, there I can silence the complaints with INSANE_SKIP.
>     >>
>     >> Unfortunately I have not found a method doing the same when the
>     package
>     >> is installed by the image class.
>     >>
>     >> Is there an elegant way around it?
>     >>
>     >>
>     >> Error:
>     >>    Problem: conflicting requests
>     >>     - nothing provides libdl.so.2 needed by
>     >> xxx-single-group-0.1-r0.cortexa53_crypto
>     >>     - nothing provides libdl.so.2(GLIBC_2.0) needed by
>     >> xxx-single-group-0.1-r0.cortexa53_crypto
>     >>     - nothing provides libdl.so.2(GLIBC_2.1) needed by
>     >> xxx-single-group-0.1-r0.cortexa53_crypto
>     >>     - nothing provides libgcc_s.so.1 needed by
>     >> xxx-single-group-0.1-r0.cortexa53_crypto
>     >>     - nothing provides libgcc_s.so.1(GCC_3.0) needed by
>     >> xxx-single-group-0.1-r0.cortexa53_crypto
>     >>     - nothing provides libm.so.6 needed by
>     >> xxx-single-group-0.1-r0.cortexa53_crypto
>     >>     - nothing provides libm.so.6(GLIBC_2.0) needed by
>     >> xxx-single-group-0.1-r0.cortexa53_crypto
>     >>     - nothing provides libm.so.6(GLIBC_2.1) needed by
>     >> xxx-single-group-0.1-r0.cortexa53_crypto
>     >>     - nothing provides libpthread.so.0 needed by
>     >> xxx-single-group-0.1-r0.cortexa53_crypto
>     >>     - nothing provides libpthread.so.0(GLIBC_2.0) needed by
>     >> xxx-single-group-0.1-r0.cortexa53_crypto
>     >>     - nothing provides libpthread.so.0(GLIBC_2.1) needed by
>     >> xxx-single-group-0.1-r0.cortexa53_crypto
>     >>     - nothing provides libpthread.so.0(GLIBC_2.2) needed by
>     >> xxx-single-group-0.1-r0.cortexa53_crypto
>     >>     - nothing provides libpthread.so.0(GLIBC_2.3.2) needed by
>     >> xxx-single-group-0.1-r0.cortexa53_crypto
>     >>     - nothing provides librt.so.1 needed by
>     >> xxx-single-group-0.1-r0.cortexa53_crypto
>     >>     - nothing provides librt.so.1(GLIBC_2.2) needed by
>     >> xxx-single-group-0.1-r0.cortexa53_crypto
>     >> (try to add '--skip-broken' to skip uninstallable packages)
>     >>
>     >>
>     >> --
>     >> Rudolf J Streif
>     >> CEO/CTO ibeeto
>     >> +1.855.442.3386 x700
>     >>
>     >>
>     >> -=-=-=-=-=-=-=-=-=-=-=-
>     >> Links: You receive all messages sent to this group.
>     >> View/Reply Online (#57296):
>     https://lists.yoctoproject.org/g/yocto/message/57296
>     <https://lists.yoctoproject.org/g/yocto/message/57296>
>     >> Mute This Topic:
>     https://lists.yoctoproject.org/mt/91607892/1686489
>     <https://lists.yoctoproject.org/mt/91607892/1686489>
>     >> Group Owner: yocto+owner@lists.yoctoproject.org
>     <mailto:yocto%2Bowner@lists.yoctoproject.org>
>     >> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
>     <https://lists.yoctoproject.org/g/yocto/unsub>
>     [alex.kanavin@gmail.com <mailto:alex.kanavin@gmail.com>]
>     >> -=-=-=-=-=-=-=-=-=-=-=-
>     >>
>     -- 
>     Rudolf J Streif
>     CEO/CTO ibeeto
>     +1.855.442.3386 x700
>
-- 
Rudolf J Streif
CEO/CTO ibeeto
+1.855.442.3386 x700


[-- Attachment #1.1.1.2: Type: text/html, Size: 10913 bytes --]

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 1717 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2022-06-07 22:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 18:59 Force binary package install Rudolf J Streif
2022-06-07 19:44 ` [yocto] " Alexander Kanavin
2022-06-07 19:57   ` Rudolf J Streif
2022-06-07 22:12     ` Alexander Kanavin
2022-06-07 22:48       ` Rudolf J Streif [this message]
2022-06-07 23:36         ` Chuck Wolber
2022-06-08  1:17           ` Rudolf J Streif
2022-06-08 15:54             ` Richard Purdie
2022-06-13 20:08               ` Rudolf J Streif
2022-06-13 21:32                 ` Richard Purdie
2022-06-14  0:09                   ` Rudolf J Streif
2022-06-08  9:59         ` Alexander Kanavin

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=9bd2408c-3309-11e6-2bba-37f69d90e4e2@ibeeto.com \
    --to=rudolf.streif@ibeeto.com \
    --cc=alex.kanavin@gmail.com \
    --cc=yocto@lists.yoctoproject.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.