@@ -66,9 +66,9 @@ sbindir_progs = "chroot"
# coreutils-stdbuf without getting the rest of coreutils, but make
# coreutils itself pull in stdbuf, so IMAGE_INSTALL += "coreutils"
# always provides all coreutils
-PACKAGE_BEFORE_PN:class-target += "${@bb.utils.contains('PACKAGECONFIG', 'single-binary', '', 'coreutils-stdbuf', d)}"
+PACKAGE_BEFORE_PN += "${@bb.utils.contains('PACKAGECONFIG', 'single-binary', '', 'coreutils-stdbuf', d)}"
FILES:coreutils-stdbuf = "${bindir}/stdbuf ${libdir}/coreutils/libstdbuf.so"
-RDEPENDS:coreutils:class-target += "${@bb.utils.contains('PACKAGECONFIG', 'single-binary', '', 'coreutils-stdbuf', d)}"
+RDEPENDS:coreutils += "${@bb.utils.contains('PACKAGECONFIG', 'single-binary', '', 'coreutils-stdbuf', d)}"
# However, when the single-binary PACKAGECONFIG is used, stdbuf
# functionality is built into the single coreutils binary, so there's
:class-target overrides for PACKAGE_BEFORE_PN and RDEPENDS:coreutils were being appended to with the coreutils-stdbuf, but instead of being an append only for target builds, it was actually overriding those variables. One could replace `:class-target +=` with `:append:class-target =`, but I don't think there is actually any need for this to be :class-target specific. RPROVIDES:coreutils few lines below doesn't use that override. Signed-off-by: Michal Sieron <michalwsieron@gmail.com> --- meta/recipes-core/coreutils/coreutils_9.10.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)