From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@buildroot.org
Cc: Pierre-Jean Texier <texier.pj2@gmail.com>
Subject: [Buildroot] [PATCH] package/stunnel: fix STUNNEL_CONF_ENV
Date: Sun, 5 Jul 2026 18:45:33 +0200 [thread overview]
Message-ID: <akqKLbhp-5ANsPNj@waldemar-brodkorb.de> (raw)
In commit 45d056e7bf69aca4a036aba83e2573301996e9e0 stunnel got an
update to 5.78, but missed a change in configure.ac/configure.
Update STUNNEL_CONF_ENV accordingely.
Fixes:
- https://autobuild.buildroot.net/results/69b/69b87d600ef9fa1d4eb8f65a7282c53808faf362/
- https://autobuild.buildroot.net/results/b87/b87040d5264befa18da213d460f28a214410386b/
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
package/stunnel/stunnel.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/stunnel/stunnel.mk b/package/stunnel/stunnel.mk
index 8bd680af32..59321f910a 100644
--- a/package/stunnel/stunnel.mk
+++ b/package/stunnel/stunnel.mk
@@ -10,7 +10,7 @@ STUNNEL_DEPENDENCIES = host-pkgconf openssl
STUNNEL_CONF_OPTS = --with-ssl=$(STAGING_DIR)/usr --with-threads=fork \
--disable-libwrap
STUNNEL_CONF_ENV = \
- ax_cv_check_cflags___fstack_protector=$(if $(BR2_TOOLCHAIN_HAS_SSP),yes,no) \
+ ax_cv_check_cflags___fstack_protector_strong=$(if $(BR2_TOOLCHAIN_HAS_SSP),yes,no) \
LIBS=`$(PKG_CONFIG_HOST_BINARY) --libs openssl`
STUNNEL_LICENSE = GPL-2.0+
STUNNEL_LICENSE_FILES = COPYING.md COPYRIGHT.md
--
2.47.3
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-07-05 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 16:45 Waldemar Brodkorb [this message]
2026-08-08 17:51 ` [Buildroot] [PATCH] package/stunnel: fix STUNNEL_CONF_ENV 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=akqKLbhp-5ANsPNj@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@buildroot.org \
--cc=texier.pj2@gmail.com \
/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