From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH v2 next] package/unbound: enable tfo-client for uClibc-ng systems
Date: Tue, 13 Aug 2024 06:48:42 +0200 [thread overview]
Message-ID: <ZrrlqhreN1oOJBdA@waldemar-brodkorb.de> (raw)
uClibc-ng systems have MSG_FASTOPEN since 2018 so no need
to disable support for TCP fastopen client mode.
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
v1->v2:
- split patches this one goes to next, suggested by Thomas P.
---
package/unbound/unbound.mk | 9 +--------
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/package/unbound/unbound.mk b/package/unbound/unbound.mk
index ff0262bef1..04386e8d5b 100644
--- a/package/unbound/unbound.mk
+++ b/package/unbound/unbound.mk
@@ -18,18 +18,11 @@ UNBOUND_CONF_OPTS = \
--with-pidfile=/var/run/unbound.pid \
--with-rootkey-file=/etc/unbound/root.key \
--enable-tfo-server \
+ --enable-tfo-client \
--with-libevent=$(STAGING_DIR)/usr \
--with-libexpat=$(STAGING_DIR)/usr \
--with-ssl=$(STAGING_DIR)/usr
-# uClibc-ng does not have MSG_FASTOPEN
-# so TCP Fast Open client mode disabled for it
-ifeq ($(BR2_TOOLCHAIN_USES_UCLIBC),y)
-UNBOUND_CONF_OPTS += --disable-tfo-client
-else
-UNBOUND_CONF_OPTS += --enable-tfo-client
-endif
-
ifeq ($(BR2_TOOLCHAIN_HAS_THREADS_NPTL),y)
UNBOUND_CONF_OPTS += --with-pthreads
else
--
2.30.2
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-08-13 4:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 4:48 Waldemar Brodkorb [this message]
2024-08-14 21:45 ` [Buildroot] [PATCH v2 next] package/unbound: enable tfo-client for uClibc-ng systems Thomas Petazzoni via buildroot
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=ZrrlqhreN1oOJBdA@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@buildroot.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