diff options
Diffstat (limited to 'gnu/packages')
| -rw-r--r-- | gnu/packages/patches/valgrind-glibc-compat.patch | 18 | ||||
| -rw-r--r-- | gnu/packages/valgrind.scm | 13 |
2 files changed, 4 insertions, 27 deletions
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; diff --git a/gnu/packages/valgrind.scm b/gnu/packages/valgrind.scm index 0a6206b3b1..9952fa1647 100644 --- a/gnu/packages/valgrind.scm +++ b/gnu/packages/valgrind.scm @@ -32,7 +32,7 @@ (define-public valgrind (package (name "valgrind") - (version "3.13.0") + (version "3.14.0") (source (origin (method url-fetch) (uri (list (string-append "http://www.valgrind.org/downloads" @@ -41,9 +41,8 @@ "/valgrind-" version ".tar.bz2"))) (sha256 (base32 - "0fqc3684grrbxwsic1rc5ryxzxmigzjx9p5vf3lxa37h0gpq0rnp")) - (patches (search-patches "valgrind-enable-arm.patch" - "valgrind-glibc-compat.patch")))) + "19ds42jwd89zrsjb94g7gizkkzipn8xik3xykrpcqxylxyzi2z03")) + (patches (search-patches "valgrind-enable-arm.patch")))) (build-system gnu-build-system) (outputs '("doc" ;16 MB "out")) @@ -79,8 +78,4 @@ tools. There are Valgrind tools that can automatically detect many memory management and threading bugs, and profile your programs in detail. You can also use Valgrind to build new tools.") - (license gpl2+) - - ;; Building VEX on mips64el-linux fails with "opcode not supported on this - ;; processor: mips3". - (supported-systems (delete "mips64el-linux" %supported-systems)))) + (license gpl2+))) |