From: Max Krummenacher <max.oss.09@gmail.com>
To: openembedded-core@lists.openembedded.org,
Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: Max Krummenacher <max.krummenacher@toradex.com>,
Randolph Sapp <rs@ti.com>
Subject: [oe][OE-core][Patch 0/1] Revert "bin_package.bbclass: Inhibit the default dependencies"
Date: Sun, 27 Aug 2023 10:09:52 +0200 [thread overview]
Message-ID: <20230827080953.2005190-1-max.oss.09@gmail.com> (raw)
From: Max Krummenacher <max.krummenacher@toradex.com>
Hi
With commit d1d09bd4d7 ("bin_package.bbclass: Inhibit the default
dependencies") applied I'm getting a lot of these errors, i.e. qa
does miss libc and compiler provided libs:
ERROR: ti-img-rogue-umlibs-23.1.6404501-r2 do_package_qa: QA Issue: /usr/lib/libusc.so.23.1.6404501 contained in package ti-img-rogue-umlibs requires ld-linux-aarch64.so.1(GLIBC_2.17)(64bit), but no providers found in RDEPENDS:ti-img-rogue-umlibs? [file-rdeps]
ERROR: ti-img-rogue-umlibs-23.1.6404501-r2 do_package_qa: QA Issue: /usr/lib/libusc.so.23.1.6404501 contained in package ti-img-rogue-umlibs requires libc.so.6(GLIBC_2.17)(64bit), but no providers found in RDEPENDS:ti-img-rogue-umlibs? [file-rdeps]
ERROR: ti-img-rogue-umlibs-23.1.6404501-r2 do_package_qa: QA Issue: /usr/lib/libufwriter.so.23.1.6404501 contained in package ti-img-rogue-umlibs requires libstdc++.so.6(GLIBCXX_3.4.14)(64bit), but no providers found in RDEPENDS:ti-img-rogue-umlibs? [file-rdeps]
Reverting the commit makes the build pass, alternatively adding
to depends in the recipe which is using the bin_package class
fixes it too:
DEPENDS += " virtual/${TARGET_PREFIX}compilerlibs virtual/libc"
I'd prefer reverting removing the default dependencies over fixing
each of the recipes which do use the bin_package class to actually
install binaries running in the target user space.
Any opinions?
Max
Max Krummenacher (1):
Revert "bin_package.bbclass: Inhibit the default dependencies"
meta/classes-recipe/bin_package.bbclass | 3 ---
1 file changed, 3 deletions(-)
--
2.35.3
next reply other threads:[~2023-08-27 8:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 8:09 Max Krummenacher [this message]
2023-08-27 8:09 ` [oe][OE-core][Patch 1/1] Revert "bin_package.bbclass: Inhibit the default dependencies" Max Krummenacher
2023-10-27 20:13 ` Peter Kjellerstedt
2023-08-27 21:23 ` [oe][OE-core][Patch 0/1] " Peter Kjellerstedt
2023-08-28 15:01 ` Max Krummenacher
[not found] ` <177F942FA4953D34.1521@lists.openembedded.org>
2023-08-28 15:09 ` Max Krummenacher
2023-08-28 16:22 ` [EXTERNAL] " Randolph Sapp
2023-08-28 19:45 ` Randolph Sapp
2023-08-28 19:50 ` Randolph Sapp
2023-08-28 17:10 ` Ryan Eatmon
2023-08-31 17:28 ` Peter Kjellerstedt
[not found] ` <178087E768B3479B.27804@lists.openembedded.org>
2023-10-07 0:10 ` Peter Kjellerstedt
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=20230827080953.2005190-1-max.oss.09@gmail.com \
--to=max.oss.09@gmail.com \
--cc=max.krummenacher@toradex.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--cc=rs@ti.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 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.