summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristopher Baines <mail@cbaines.net>2024-04-15 09:26:58 +0100
committerGuix Patches Tester <>2024-04-17 14:18:22 +0200
commit945b334d443fa2290424f8081447dff59b407fac (patch)
tree7ac7057a888f161b0822b111b19eade97b1a72b1
parentb47ae1ecc43baaf726701ab2d2f810ecfaa75428 (diff)
downloadguix-patches-issue-70394.tar
guix-patches-issue-70394.tar.gz
gnu: ruby-ruby-memcheck.issue-70394
Use valgrind rather than valgrind/interactive, as this doesn't have gdb as an input, which makes it easier to update gdb. * gnu/packages/ruby.scm (ruby-ruby-memcheck)[inputs]: Use valgrind. Change-Id: Icfcee2c27fc41e68e1a34b38c043ece188cc56af
-rw-r--r--gnu/packages/ruby.scm2
1 files changed, 1 insertions, 1 deletions
diff --git a/gnu/packages/ruby.scm b/gnu/packages/ruby.scm
index 0541bb9562..5e34109a59 100644
--- a/gnu/packages/ruby.scm
+++ b/gnu/packages/ruby.scm
@@ -10114,7 +10114,7 @@ Profiling multiple threads simultaneously is supported.
(("%x\\(git ls-files -z)")
"`git ls-files -z`")))))))
(native-inputs (list ruby-rake-compiler ruby-rspec))
- (inputs (list valgrind/interactive))
+ (inputs (list valgrind))
(propagated-inputs (list ruby-nokogiri))
(synopsis "Valgrind memcheck tool for Ruby")
(description "The @code{ruby_memcheck} gem provides a sane way to use