mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ladislav Michl <oss-lists@triops.cz>
To: ptxdist@pengutronix.de
Subject: [ptxdist] libseccomp: do not enforce standalone development tools
Date: Wed, 29 Apr 2026 10:05:18 +0200	[thread overview]
Message-ID: <afG7vrP3tXYGiWxQ@lenoch> (raw)

From: Ladislav Michl <ladis@triops.cz>

Partially revert af3a035787a2 ("libseccomp: install some useful
development tools on demand") which is always enforcing standalone
development tools. Leave that on user allowing to choose also
Busybox' variants.

Signed-off-by: Ladislav Michl <ladis@triops.cz>
---
 rules/libseccomp.in | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

Note: alternatively some smart ifdeffery could be done for all
the tools used, but that requires verification on each package
update. Something we know will fail in advance :)
However, in you prefer that way, I can give it a try.

diff --git a/rules/libseccomp.in b/rules/libseccomp.in
index 01c6e8a4f..91a132a85 100644
--- a/rules/libseccomp.in
+++ b/rules/libseccomp.in
@@ -1,12 +1,9 @@
 ## SECTION=system_libraries
 
 menuconfig LIBSECCOMP
-	bool
+	tristate
 	prompt "libseccomp                    "
 	select HOST_GPERF
-	select SED if LIBSECCOMP_UTILS && RUNTIME
-	select STRACE if LIBSECCOMP_UTILS && RUNTIME
-	select WHICH if LIBSECCOMP_UTILS && RUNTIME
 	help
 	  An Enhanced Seccomp (mode 2) Helper Library
 
@@ -23,8 +20,8 @@ config LIBSECCOMP_UTILS
 	prompt "install utils"
 	help
 	  Install some utils, useful for development.
-	  Note: in order to run some of these utils the tools 'uniq', 'sort',
-	  'expr' and 'mktemp' from the 'Busybox' *or* 'Coreutils' package is
-	  required.
+	  Note: in order to run some of these utils the tools 'expr', 'mktemp', 'sed',
+	  'sort', 'strace, ''uniq' and 'which' from the 'Busybox' *or* 'Coreutils'
+	  package is required.
 
 endif
-- 
2.47.3




                 reply	other threads:[~2026-04-29  8:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=afG7vrP3tXYGiWxQ@lenoch \
    --to=oss-lists@triops.cz \
    --cc=ptxdist@pengutronix.de \
    /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