valgrind: let the valgrind configure script detect TLS availability
Back in 2005, in commita2c326396a
("update valgrind to the latest and greatest"), an explicit --disable-tls option was added. More recently, in commit31a3f4bd54
("valgrind: enable tls support") changed this to be conditional on BR2_GCC_ENABLE_TLS. However, the configure script of valgrind is perfectly capable of detecting TLS support, even in a cross-compilation case: it tries to compile a program that uses __thread and sees if it works. Since we're about to modify how BR2_GCC_ENABLE_TLS is handled, we'd better remove its usage from packages, and valgrind is the only package using this config option. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
This commit is contained in:
parent
df3df495c4
commit
511a161b87
@ -15,12 +15,6 @@ VALGRIND_INSTALL_STAGING = YES
|
||||
# patch 0004-Fixes-for-musl-libc.patch touching configure.ac
|
||||
VALGRIND_AUTORECONF = YES
|
||||
|
||||
ifeq ($(BR2_GCC_ENABLE_TLS),y)
|
||||
VALGRIND_CONF_OPTS += --enable-tls
|
||||
else
|
||||
VALGRIND_CONF_OPTS += --disable-tls
|
||||
endif
|
||||
|
||||
# When Valgrind detects a 32-bit MIPS architecture, it forcibly adds
|
||||
# -march=mips32 to CFLAGS; when it detects a 64-bit MIPS architecture,
|
||||
# it forcibly adds -march=mips64. This causes Valgrind to be built
|
||||
|
Loading…
Reference in New Issue
Block a user