From 9ad32f5482665ba121e2083c1a1d9cd3a00f3ac4 Mon Sep 17 00:00:00 2001 From: Khem Raj Date: Tue, 20 May 2025 23:19:54 -0700 Subject: [PATCH] valgrind: Use gcc to compile on riscv64 clang does not yet support __builtin_longjmp on riscv64 Signed-off-by: Khem Raj Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie --- meta/recipes-devtools/valgrind/valgrind_3.25.1.bb | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/meta/recipes-devtools/valgrind/valgrind_3.25.1.bb b/meta/recipes-devtools/valgrind/valgrind_3.25.1.bb index 8e27212a0f..a8b0be5767 100644 --- a/meta/recipes-devtools/valgrind/valgrind_3.25.1.bb +++ b/meta/recipes-devtools/valgrind/valgrind_3.25.1.bb @@ -106,3 +106,11 @@ INHIBIT_PACKAGE_STRIP_FILES = "${PKGD}${libexecdir}/valgrind/vgpreload_memcheck- # valgrind needs debug information for ld.so at runtime in order to # redirect functions like strlen. RRECOMMENDS:${PN} += "${TCLIBC}-dbg" + +# Valgrind needs intrinsics which are not provided by clang +# m_signals.c:2213:7: error: __builtin_longjmp is not supported for the current target +# 2213 | VG_MINIMAL_LONGJMP(tst->sched_jmpbuf); +# | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +# +# It needs something like - https://bugs.kde.org/show_bug.cgi?id=369723 +TOOLCHAIN:riscv64 = "gcc" -- 2.47.2