fdad2e564e
As Thomas puts it:
The comment can only be visible when a toolchain that is *not*
uclibc and *not* glibc is used. I.e, the comment is now only visible
when musl is used. Which is not what we want.
Indeed, I completely borked the conditions. When a glibc or uClibc
toolchain is selected, the comment is entirely hidden, and we don;t get
the extra requirements (wchar, !static).
Fix that with the solution proposed by Thomas.
Reported-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
36 lines
1.2 KiB
Plaintext
36 lines
1.2 KiB
Plaintext
config BR2_PACKAGE_RACEHOUND
|
|
bool "racehound"
|
|
select BR2_PACKAGE_ELFUTILS
|
|
depends on BR2_LINUX_KERNEL
|
|
depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_14
|
|
depends on BR2_INSTALL_LIBSTDCPP
|
|
depends on BR2_USE_WCHAR # elfutils
|
|
depends on !BR2_STATIC_LIBS # elfutils
|
|
depends on BR2_TOOLCHAIN_USES_UCLIBC || BR2_TOOLCHAIN_USES_GLIBC # elfutils
|
|
# only x86/x86_64 supported
|
|
depends on BR2_i386 || BR2_x86_64
|
|
help
|
|
RaceHound can be used to detect data races in the Linux
|
|
kernel on x86.
|
|
|
|
RaceHound needs the following kernel configurations enabled:
|
|
- CONFIG_X86_32 or CONFIG_X86_64
|
|
- CONFIG_MODULES
|
|
- CONFIG_MODULE_UNLOAD
|
|
- CONFIG_SYSFS
|
|
- CONFIG_DEBUG_FS
|
|
- CONFIG_KALLSYMS
|
|
- CONFIG_KALLSYMS_ALL
|
|
- CONFIG_KPROBES
|
|
|
|
https://github.com/winnukem/racehound
|
|
|
|
comment "racehound needs an Linux kernel >= 3.14 to be built"
|
|
depends on !BR2_LINUX_KERNEL || !BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_14
|
|
depends on BR2_i386 || BR2_x86_64
|
|
|
|
comment "racehound needs a uClibc or (e)glibc toolchain w/ C++, wchar, dynamic library"
|
|
depends on BR2_i386 || BR2_x86_64
|
|
depends on !BR2_INSTALL_LIBSTDCPP || !BR2_USE_WCHAR || BR2_STATIC_LIBS \
|
|
|| !(BR2_TOOLCHAIN_USES_UCLIBC || BR2_TOOLCHAIN_USES_GLIBC)
|