From 350b7f8a7441d7df89249b356299a843b9a18794 Mon Sep 17 00:00:00 2001 From: Marius Bakke Date: Wed, 6 Mar 2019 16:00:12 +0100 Subject: gnu: valgrind: Update to 3.14.0. * gnu/packages/patches/valgrind-glibc-compat.patch: Delete file. * gnu/local.mk (dist_patch_DATA): Adjust accordingly. * gnu/packages/valgrind.scm (valgrind): Update to 3.14.0. [supported-systems]: Add mips64el-linux. --- gnu/packages/patches/valgrind-glibc-compat.patch | 18 ------------------ 1 file changed, 18 deletions(-) delete mode 100644 gnu/packages/patches/valgrind-glibc-compat.patch (limited to 'gnu/packages/patches') diff --git a/gnu/packages/patches/valgrind-glibc-compat.patch b/gnu/packages/patches/valgrind-glibc-compat.patch deleted file mode 100644 index 4f8effd207..0000000000 --- a/gnu/packages/patches/valgrind-glibc-compat.patch +++ /dev/null @@ -1,18 +0,0 @@ -Fix build failure with glibc 2.26. - -Patch copied from upstream source repository: -https://sourceware.org/git/?p=valgrind.git;a=commit;h=2b5eab6a8db1b0487a3ad7fc4e7eeda6d3513626 - -diff --git a/memcheck/tests/linux/stack_changes.c b/memcheck/tests/linux/stack_changes.c -index a978fc2..7f97b90 100644 ---- a/memcheck/tests/linux/stack_changes.c -+++ b/memcheck/tests/linux/stack_changes.c -@@ -10,7 +10,7 @@ - // This test is checking the libc context calls (setcontext, etc.) and - // checks that Valgrind notices their stack changes properly. - --typedef struct ucontext mycontext; -+typedef ucontext_t mycontext; - - mycontext ctx1, ctx2, oldc; - int count; -- cgit v1.2.3