From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-debug/dtrace/
Date: Thu, 22 Aug 2024 12:22:08 +0000 (UTC) [thread overview]
Message-ID: <1724329301.b2f1216adb56a434ab8e590cb530ce79c2e4da1a.sam@gentoo> (raw)
commit: b2f1216adb56a434ab8e590cb530ce79c2e4da1a
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Aug 22 12:20:46 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Aug 22 12:21:41 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b2f1216a
dev-debug/dtrace: improve config checks further (mostly pedantry, also for tests)
This adds some technically-required-but-already-covered-by-dependencies
CONFIG_* requirements in general, and then some real config requirements
we were missing for the testsuite.
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-debug/dtrace/dtrace-2.0.1.1-r1.ebuild | 12 +++++++++++-
dev-debug/dtrace/dtrace-9999.ebuild | 12 +++++++++++-
2 files changed, 22 insertions(+), 2 deletions(-)
diff --git a/dev-debug/dtrace/dtrace-2.0.1.1-r1.ebuild b/dev-debug/dtrace/dtrace-2.0.1.1-r1.ebuild
index f084535e5911..04646e70ea08 100644
--- a/dev-debug/dtrace/dtrace-2.0.1.1-r1.ebuild
+++ b/dev-debug/dtrace/dtrace-2.0.1.1-r1.ebuild
@@ -85,12 +85,22 @@ pkg_pretend() {
CONFIG_CHECK+=" ~CUSE"
# Tracing
- CONFIG_CHECK+=" ~FTRACE_SYSCALLS ~UPROBE_EVENTS ~DYNAMIC_FTRACE ~FUNCTION_TRACER"
+ CONFIG_CHECK+=" ~TRACING"
+ CONFIG_CHECK+=" ~UPROBES ~UPROBE_EVENTS"
+ CONFIG_CHECK+=" ~FTRACE ~FTRACE_SYSCALLS ~DYNAMIC_FTRACE ~FUNCTION_TRACER"
CONFIG_CHECK+=" ~FPROBE"
+ # DTrace can fallback to kprobes for fbt but people often want them off
+ # for security and newer kernels work fine with BPF for that, so
+ # let's omit it.
# https://gcc.gnu.org/PR84052
CONFIG_CHECK+=" !GCC_PLUGIN_RANDSTRUCT"
+ if use install-tests ; then
+ # See test/modules
+ CONFIG_CHECK+=" ~EXT4_FS ~ISO9660_FS ~NFS_FS ~RDS ~TUN"
+ fi
+
check_extra_config
}
diff --git a/dev-debug/dtrace/dtrace-9999.ebuild b/dev-debug/dtrace/dtrace-9999.ebuild
index f084535e5911..04646e70ea08 100644
--- a/dev-debug/dtrace/dtrace-9999.ebuild
+++ b/dev-debug/dtrace/dtrace-9999.ebuild
@@ -85,12 +85,22 @@ pkg_pretend() {
CONFIG_CHECK+=" ~CUSE"
# Tracing
- CONFIG_CHECK+=" ~FTRACE_SYSCALLS ~UPROBE_EVENTS ~DYNAMIC_FTRACE ~FUNCTION_TRACER"
+ CONFIG_CHECK+=" ~TRACING"
+ CONFIG_CHECK+=" ~UPROBES ~UPROBE_EVENTS"
+ CONFIG_CHECK+=" ~FTRACE ~FTRACE_SYSCALLS ~DYNAMIC_FTRACE ~FUNCTION_TRACER"
CONFIG_CHECK+=" ~FPROBE"
+ # DTrace can fallback to kprobes for fbt but people often want them off
+ # for security and newer kernels work fine with BPF for that, so
+ # let's omit it.
# https://gcc.gnu.org/PR84052
CONFIG_CHECK+=" !GCC_PLUGIN_RANDSTRUCT"
+ if use install-tests ; then
+ # See test/modules
+ CONFIG_CHECK+=" ~EXT4_FS ~ISO9660_FS ~NFS_FS ~RDS ~TUN"
+ fi
+
check_extra_config
}
next reply other threads:[~2024-08-22 12:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 12:22 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-25 8:14 [gentoo-commits] repo/gentoo:master commit in: dev-debug/dtrace/ Sam James
2025-03-08 8:41 Arthur Zamarin
2025-03-08 1:41 Sam James
2025-02-05 1:12 Sam James
2024-10-30 22:50 Sam James
2024-10-30 22:50 Sam James
2024-10-30 22:50 Sam James
2024-10-30 22:50 Sam James
2024-10-24 8:22 Arthur Zamarin
2024-10-24 2:37 Sam James
2024-09-12 1:06 Sam James
2024-09-12 0:43 Sam James
2024-09-12 0:42 Sam James
2024-09-12 0:42 Sam James
2024-09-12 0:38 Sam James
2024-09-12 0:38 Sam James
2024-09-12 0:30 Sam James
2024-09-12 0:10 Sam James
2024-09-11 23:59 Sam James
2024-09-11 3:35 Sam James
2024-09-10 13:58 Sam James
2024-08-30 18:13 Sam James
2024-08-25 18:49 Sam James
2024-08-22 12:54 Sam James
2024-08-22 12:36 Sam James
2024-08-22 12:36 Sam James
2024-08-20 1:49 Sam James
2024-08-20 1:49 Sam James
2024-08-20 1:49 Sam James
2024-08-19 23:27 Sam James
2024-08-19 20:16 Sam James
2024-08-18 22:59 Sam James
2024-08-18 21:47 Sam James
2024-08-18 21:42 Sam James
2024-08-18 21:36 Sam James
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=1724329301.b2f1216adb56a434ab8e590cb530ce79c2e4da1a.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