From: Mathieu Othacehe <othacehe@gnu.org>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: 58045-done@debbugs.gnu.org
Subject: bug#58045: [PATCH] gnu: Add libpatch.
Date: Mon, 26 Sep 2022 15:33:46 +0200 [thread overview]
Message-ID: <87zgemqmyt.fsf@gnu.org> (raw)
In-Reply-To: <3400e6a50d528e085834f77e7159607f22d9b8b9.1664037413.git.olivier.dion@polymtl.ca> (Olivier Dion's message of "Sat, 24 Sep 2022 12:38:15 -0400")
> * gnu/packages/instrumentation.scm (libpatch): New variable.
Applied with the following diff:
--8<---------------cut here---------------start------------->8---
diff --git a/gnu/packages/instrumentation.scm b/gnu/packages/instrumentation.scm
index b611f2b141..3d6b6fab38 100644
--- a/gnu/packages/instrumentation.scm
+++ b/gnu/packages/instrumentation.scm
@@ -233,28 +233,25 @@ (define-public libpatch
(or
(%current-target-system)
(%current-system))))))))
+ ;;; Add lttng-ust to the inputs if you want tracepoints within libpatch
+ ;;; for debugging.
(inputs
(list capstone
elfutils
- ;; Uncomment the following if you want tracepoints within libpatch
- ;; for debugging.
- ;;
- ;; lttng-ust
libunwind
liburcu))
(native-inputs
(list coreutils
;; test-ftrace.scm
(list coreutils "debug")
+ (list guile-3.0 "debug")
+ (list gnu-make "debug")
+
;; For eu-nm in test-ftrace.scm.
(list elfutils "bin")
- ;; Put Guile in your profile if you want to use the bindings.
+
guile-3.0
- ;; test-ftrace.scm
- (list guile-3.0 "debug")
gnu-make
- ;; test-ftrace.scm
- (list gnu-make "debug")
pkg-config
;; zlib is required by libdw. This can be removed if zlib is put
;; as a propagated-input of elfutils.
--8<---------------cut here---------------end--------------->8---
Thanks,
Mathieu
prev parent reply other threads:[~2022-09-26 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 16:38 [bug#58045] [PATCH] gnu: Add libpatch Olivier Dion via Guix-patches via
2022-09-26 13:33 ` Mathieu Othacehe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgemqmyt.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=58045-done@debbugs.gnu.org \
--cc=olivier.dion@polymtl.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.