public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/libtrace/
Date: Thu, 05 Jun 2025 21:20:59 +0000 (UTC)	[thread overview]
Message-ID: <1749158145.497bde980a8c81767fd0dad77db3b6918a3aa8d4.sam@gentoo> (raw)

commit:     497bde980a8c81767fd0dad77db3b6918a3aa8d4
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jun  5 21:15:45 2025 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jun  5 21:15:45 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=497bde98

net-libs/libtrace: don't strip BPF

Just like in DTrace.

Closes: https://bugs.gentoo.org/856493
Closes: https://bugs.gentoo.org/956760
Signed-off-by: Sam James <sam <AT> gentoo.org>

 net-libs/libtrace/libtrace-4.0.28.ebuild | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/net-libs/libtrace/libtrace-4.0.28.ebuild b/net-libs/libtrace/libtrace-4.0.28.ebuild
index e50efac5eb3a..fa8398c11a0e 100644
--- a/net-libs/libtrace/libtrace-4.0.28.ebuild
+++ b/net-libs/libtrace/libtrace-4.0.28.ebuild
@@ -33,6 +33,10 @@ BDEPEND="
 	app-alternatives/yacc
 "
 
+QA_EXECSTACK="
+	usr/share/libtrace/format_linux_xdp_kern.bpf
+"
+
 src_prepare() {
 	default
 
@@ -60,6 +64,9 @@ src_configure() {
 src_install() {
 	default
 
+	# BPF
+	dostrip -x /usr/share/libtrace/format_linux_xdp_kern.bpf
+
 	if use doc ; then
 		docinto html
 		dodoc -r docs/doxygen/html


             reply	other threads:[~2025-06-05 21:21 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 21:20 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-05 21:20 [gentoo-commits] repo/gentoo:master commit in: net-libs/libtrace/ Sam James
2024-06-23  0:27 Sam James
2023-08-31  6:04 Sam James
2023-06-01  6:43 Sam James
2022-12-17  8:52 Sam James
2022-11-09  5:41 Sam James
2022-07-05  3:15 Sam James
2022-07-05  3:15 Sam James
2021-09-16  1:18 Sam James
2021-02-27  4:12 Sam James
2021-02-27  4:12 Sam James
2021-02-27  4:12 Sam James
2021-02-27  4:12 Sam James
2021-02-27  4:12 Sam James
2021-02-27  4:12 Sam James
2021-02-27  4:12 Sam James
2020-08-07  7:40 Jeroen Roovers
2020-05-26  6:32 Jeroen Roovers
2020-03-27  6:46 Jeroen Roovers
2020-02-15 11:05 Jeroen Roovers
2020-02-15  9:30 Jeroen Roovers
2020-02-13 13:30 Jeroen Roovers
2020-02-13 13:04 Jeroen Roovers
2020-01-29 15:04 Jeroen Roovers
2019-11-09  8:58 Jeroen Roovers
2019-11-07 23:06 Jeroen Roovers
2019-11-07  8:28 Jeroen Roovers
2019-08-18 12:07 Jeroen Roovers
2019-08-18 12:06 Jeroen Roovers
2019-07-01  5:34 Jeroen Roovers
2019-05-15  8:41 Jeroen Roovers
2019-05-15  8:41 Jeroen Roovers
2019-05-15  8:24 Jeroen Roovers
2019-03-11  4:48 Aaron Bauman
2019-01-19 11:38 Jeroen Roovers
2019-01-19 11:38 Jeroen Roovers
2019-01-19 11:38 Jeroen Roovers
2018-11-21 23:42 Jeroen Roovers
2018-11-21 23:42 Jeroen Roovers
2018-07-06 11:18 Jeroen Roovers
2018-07-06 11:18 Jeroen Roovers
2018-03-05 15:06 Jeroen Roovers
2018-03-05 15:03 Jeroen Roovers
2017-11-18 10:43 Jeroen Roovers
2017-01-04 15:26 Jeroen Roovers
2017-01-04 15:26 Jeroen Roovers
2016-08-31 13:01 Jeroen Roovers

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=1749158145.497bde980a8c81767fd0dad77db3b6918a3aa8d4.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox