From 3952738d083b888e5b898ed3d63a0ed9a4dd3712 Mon Sep 17 00:00:00 2001 From: Khem Raj Date: Thu, 14 May 2020 10:30:09 -0700 Subject: valgrind: Do not use outline-atomics on aarch64 This avoids the __getauxval undefined reference error seen with gcc10 on doing static linking with -nodefaultlibs, which is uncommon usecase anyway, disabling outline-atomics is not a huge deal for OE in terms of performance as we already use -mcpu which is tuned enough to the SOC the code is being generated for Signed-off-by: Khem Raj Signed-off-by: Richard Purdie --- meta/recipes-devtools/valgrind/valgrind_3.15.0.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-devtools/valgrind/valgrind_3.15.0.bb b/meta/recipes-devtools/valgrind/valgrind_3.15.0.bb index 7954437a1a..25837e4b44 100644 --- a/meta/recipes-devtools/valgrind/valgrind_3.15.0.bb +++ b/meta/recipes-devtools/valgrind/valgrind_3.15.0.bb @@ -74,6 +74,8 @@ EXTRA_OECONF += "${@['--enable-only32bit','--enable-only64bit'][d.getVar('SITEIN # valgrind checks host_cpu "armv7*)", so we need to over-ride the autotools.bbclass default --host option EXTRA_OECONF_append_arm = " --host=armv7${HOST_VENDOR}-${HOST_OS}" +CFLAGS_append_aarch64 = " -mno-outline-atomics " + EXTRA_OEMAKE = "-w" CACHED_CONFIGUREVARS += "ac_cv_path_PERL='/usr/bin/env perl'" -- cgit 1.2.3-korg