mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Lars Alex Pedersen <lapeddk@gmail.com>
To: ptxdist@pengutronix.de
Cc: Lars Alex Pedersen <lapeddk@gmail.com>
Subject: [ptxdist] [PATCH] chrony: Add option for NTS support
Date: Wed,  9 Jul 2025 10:35:13 +0200	[thread overview]
Message-ID: <20250709083513.399356-1-lapeddk@gmail.com> (raw)

chrony was compiled implicitly with NTS support enabled, but it also
required gnutls. This commit makes the option explicit and selects
gnutls and CHRONY_USE_NETTLE

Signed-off-by: Lars Alex Pedersen <lapeddk@gmail.com>
---
 rules/chrony.in   | 8 ++++++++
 rules/chrony.make | 1 +
 2 files changed, 9 insertions(+)

diff --git a/rules/chrony.in b/rules/chrony.in
index 49226f58e..9805b7a2c 100644
--- a/rules/chrony.in
+++ b/rules/chrony.in
@@ -6,6 +6,7 @@ menuconfig CHRONY
 	prompt "chrony                        "
 	select LIBC_M
 	select LIBCAP
+	select GNUTLS		if CHRONY_ENABLE_NTS
 	select LIBSECCOMP	if CHRONY_SECCOMP
 	select NETTLE		if CHRONY_USE_NETTLE
 	select PPS_TOOLS	if CHRONY_PPS_REFCLK
@@ -24,6 +25,13 @@ menuconfig CHRONY
 
 if CHRONY
 
+config CHRONY_ENABLE_NTS
+	bool
+	prompt "Enable NTS support"
+	select CHRONY_USE_NETTLE
+	help
+	  Enable NTS support
+
 config CHRONY_USE_NETTLE
 	bool
 	prompt "Use nettle crypto library"
diff --git a/rules/chrony.make b/rules/chrony.make
index ee58ae164..b0e28c4d2 100644
--- a/rules/chrony.make
+++ b/rules/chrony.make
@@ -44,6 +44,7 @@ CHRONY_CONF_OPT		:= \
 	--sysconfdir=/etc \
 	--disable-readline \
 	--without-editline \
+	$(call ptx/ifdef, PTXCONF_CHRONY_ENABLE_NTS,,--disable-nts) \
 	$(call ptx/ifdef, PTXCONF_CHRONY_USE_NETTLE,,--disable-sechash) \
 	$(call ptx/ifdef, PTXCONF_CHRONY_USE_NETTLE,,--without-nettle) \
 	--without-nss \

base-commit: 51f6fea554acb994e4f082af28077e82aab221cc
-- 
2.50.0




                 reply	other threads:[~2025-07-09  8:35 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=20250709083513.399356-1-lapeddk@gmail.com \
    --to=lapeddk@gmail.com \
    --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