From: Deepak Rathore <[email protected]> Some SDK dependency chains require valgrind to be available as SDK artifacts. The current metadata only partially provides this, which can lead to dependency resolution failures when this recipe is pulled into SDK-oriented builds.
This change does not alter target package behavior; it only enables required nativesdk variant for SDK integration paths. Signed-off-by: Deepak Rathore <[email protected]> --- meta/recipes-devtools/valgrind/valgrind_3.26.0.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-devtools/valgrind/valgrind_3.26.0.bb b/meta/recipes-devtools/valgrind/valgrind_3.26.0.bb index 6f7d67df0e..50421e8621 100644 --- a/meta/recipes-devtools/valgrind/valgrind_3.26.0.bb +++ b/meta/recipes-devtools/valgrind/valgrind_3.26.0.bb @@ -114,3 +114,4 @@ RRECOMMENDS:${PN} += "${TCLIBC}-dbg" # # It needs something like - https://bugs.kde.org/show_bug.cgi?id=369723 TOOLCHAIN:riscv64 = "gcc" +BBCLASSEXTEND += "nativesdk" -- 2.35.6
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#233112): https://lists.openembedded.org/g/openembedded-core/message/233112 Mute This Topic: https://lists.openembedded.org/mt/118327418/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
