buildroot/package/valgrind, branch 2016.02

valgrind: fix musl compile

2016-02-13T17:26:45+00:00

Add musl libc detection (based on suggestions by Romain Naour and Arnout Vandecappelle) and add some tweaks for musl support (based on OpenWRT patch [1]). Fixes ([2]): checking the glibc version... unsupported version configure: error: Valgrind requires glibc version 2.2 or later Patch suggested upstream (see [3]). [1] https://dev.openwrt.org/browser/trunk/package/devel/valgrind/patches/200-musl_fix.patch?rev=46302 [2] http://autobuild.buildroot.org/results/7b0/7b048ba58918f0a08498c61327fcf35a85a84837 [3] https://bugs.kde.org/show_bug.cgi?id=359202 Signed-off-by: Peter Seiderer Reviewed-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

valgrind: update 0003-mips-replace-addi-with-addiu.patch

2015-12-17T21:01:12+00:00

This patch has been updated in the upstream bug report, so let's update it in Buildroot as well. It will fix the build issue for mips64r6: m_dispatch/dispatch-mips64-linux.S:199: Error: opcode not supported on this processor: mips64r6 (mips64r6) `daddi $13,$13,8' Fixes: http://autobuild.buildroot.net/results/6ca/6ca3a31d1542fbbb44238e296565b40d6afcd5fa/ Signed-off-by: Vicente Olivert Riera Signed-off-by: Thomas Petazzoni

valgrind: add a patch to fix MIPS R6 by replacing ADDI with ADDIU

2015-11-30T16:08:10+00:00

The ADDI instruction has been removed for MIPS R6, so valgrind fails to build for this revision level because it uses that assembly instruction. Using ADDIU instead fixes the problem. The patch has been sent upstream: https://bugs.kde.org/show_bug.cgi?id=356112 Fixes: http://autobuild.buildroot.net/results/488/488937704b3b6bae8daed7b24da8c740b56f4d84/ Signed-off-by: Vicente Olivert Riera Signed-off-by: Peter Korsgaard

valgrind: enable tls support

2015-11-02T14:24:57+00:00

Tested with example program from [1] with qemu_x86_64. [1] http://valgrind.10908.n7.nabble.com/Thread-local-storage-TLS-support-td40815.html Signed-off-by: Peter Seiderer Signed-off-by: Thomas Petazzoni

valgrind: bump version to 3.11.0

2015-10-31T14:42:36+00:00

- rebase patch 0001-workaround-SIGSEGV-on-PPC.patch - remove upstream applied patches 0002-Fix-configure-for-Linux-kernel-4.0-rc1.patch 0004-configure.ac-Generalize-glibc-version-check.patch - rebase 0003-add-missing-ptrace-getsiginfo-on-powerpc.patch (convert to git patch format, rename to 0002-Define-PTRACE_GETSIGINFO-on-PowerPC-when-not-availab.patch) - remove legacy VALGRIND_AUTORECONF=YES (no more patch touching confgure.ac) - add '--disable-ubsan' for new undefined behaviour sanitiser option Signed-off-by: Peter Seiderer Signed-off-by: Thomas Petazzoni

valgrind: build for the right MIPS ISA revision level

2015-10-03T13:26:21+00:00

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 always for the first ISA revision level (R1), even when the user has configured Buildroot for the second ISA revision level (R2). Since R2 is backwards compatible with R1, you can run a Valgrind built for R1 in an R2 core. This is why nobody noticed about this problem, or at least nobody complained. But, since (I hope) we will support R6 in Buildroot in the near future, this problem will become very important because R6 is not backwards compatible with R1 or R2, so building Valgrind for R1 when your target is R6 will result in a non-working Valgrind. Override the CFLAGS variable (which Valgrind appends to its CFLAGS) and pass the right -march option, so they take precedence over Valgrind's wrongfully detected value. Signed-off-by: Vicente Olivert Riera Reviewed-by: Arnout Vandecappelle (Essensium/Mind) Reviewed-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

package/valgrind: disable for static-only builds

2015-09-13T20:50:00+00:00

Fixes: http://autobuild.buildroot.net/results/3b6/3b6f253f30afaee428ea0fc559be210dcec61dae http://autobuild.buildroot.net/results/60e/60e5a49360e2ee9482b4d548789f874a6502c429 http://autobuild.buildroot.net/results/5cc/5ccc2e48fa4deb90ab214c82e8921ec494555457 http://autobuild.buildroot.net/results/452/4524184b407bb6f9b55f8f85c8e0b475ff105420 Valgrind ordinarily works by preloading a shared object to replace malloc, free and friends. Some combinations of toolchain/libc allow this to build with -static, but others complain. Since it makes little sense to try to build this on a static-only system, this patch disables it on static platforms entirely. [Peter: move comment to top of file to fix menuconfig indentation] Signed-off-by: Brendan Heading Signed-off-by: Peter Korsgaard

valgrind: install to staging

2015-07-02T21:42:28+00:00

This is necessary for some packages depending on valgrind, such as libdrm which will fail with an error like this one: checking for VALGRIND... no checking whether to enable Valgrind support... configure: error: Valgrind support required but not present package/pkg-generic.mk:146: recipe for target '/br/output/build/libdrm-2.4.62/.stamp_configured' failed Signed-off-by: Vicente Olivert Riera Acked-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

valgrind: backport support for glibc 2.20+

2015-06-10T09:47:46+00:00

Fixes: http://autobuild.buildroot.net/results/352/352d087bf5daed8ce2c7e2d61db2e75db9b069b9/ http://autobuild.buildroot.net/results/a2c/a2c46d35b1c1da45f4d136f5a2be926695695bd9/ Signed-off-by: Peter Korsgaard

valgrind: Backport patch to fix build on 4.0 host kernels

2015-05-07T20:34:58+00:00

Valgrind fails to build when the host kernel is >=4.0. This patch backports the commit from upstream that fixes the kernel version verification. This verification is pointless for buildroot anyway, but it fixes the building process. [Peter: rename patch to 0002-* and add SoB, slightly reword commit msg] Signed-off-by: Christian Artin Signed-off-by: Peter Korsgaard