From: Peter Seiderer via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org, Julien Olivain <ju.o@free.fr>
Subject: Re: [Buildroot] [PATCH v3] package/libressl: bump version to 4.4.0
Date: Mon, 2 Nov 2026 14:44:41 +0100 [thread overview]
Message-ID: <20261102144441.33ea2f82@pc-1> (raw)
In-Reply-To: <aufAny9Sf6-bnoa-@windsurf>
Hello Thomas,
On Sun, 1 Nov 2026 23:44:43 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> On Fri, Oct 30, 2026 at 04:19:50PM +0100, Peter Seiderer via buildroot wrote:
>
> > +# Avoid linking problem: "undefined reference to `__stack_chk_fail_local'"
> > +ifeq ($(BR2_TOOLCHAIN_HAS_SSP),y)
> > +LIBRESSL_CONF_OPTS += -DENABLE_HARDENING=ON
> > +else
> > +LIBRESSL_CONF_OPTS += -DENABLE_HARDENING=OFF
> > +endif
>
> This should most likely be an unconditional
> -DENABLE_HARDENING=OFF. Indeed, we have a global BR2_SSP_NONE /
> BR2_SSP_REGULAR / BR2_SSP_STRONG / BR2_SSP_ALL that decides whether we
> want SSP or not.
Same for all other packages?
package/aircrack-ng/aircrack-ng.mk:ifeq ($(BR2_TOOLCHAIN_HAS_SSP),y)
package/botan/botan.mk:ifeq ($(BR2_TOOLCHAIN_HAS_SSP),y)
package/btop/btop.mk:ifneq ($(BR2_TOOLCHAIN_HAS_SSP),y)
package/linux-tools/linux-tool-rtla.mk.in:ifeq ($(BR2_TOOLCHAIN_HAS_SSP),)
package/linux-tools/linux-tool-tmon.mk.in:ifeq ($(BR2_TOOLCHAIN_HAS_SSP),)
package/monit/monit.mk: ax_cv_check_cflags___fstack_protector_all=$(if $(BR2_TOOLCHAIN_HAS_SSP),yes,no) \
package/mosh/mosh.mk:ifeq ($(BR2_TOOLCHAIN_HAS_SSP),)
package/ntp/ntp.mk:ifeq ($(BR2_TOOLCHAIN_HAS_SSP),y)
package/powerpc-utils/powerpc-utils.mk: ax_cv_check_cflags___fstack_protector_all=$(if $(BR2_TOOLCHAIN_HAS_SSP),yes,no)
package/psmisc/psmisc.mk:ifeq ($(BR2_TOOLCHAIN_HAS_SSP),)
package/radvd/radvd.mk:ifeq ($(BR2_TOOLCHAIN_HAS_SSP),y)
package/ruby/ruby.mk:ifeq ($(BR2_TOOLCHAIN_HAS_SSP),)
package/stunnel/stunnel.mk: ax_cv_check_cflags___fstack_protector_strong=$(if $(BR2_TOOLCHAIN_HAS_SSP),yes,no) \
package/vlc/vlc.mk: ax_cv_check_cflags___fstack_protector_strong=$(if $(BR2_TOOLCHAIN_HAS_SSP),yes,no)
Regards,
Peter
>
> Thanks!
>
> Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-11-02 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 15:19 [Buildroot] [PATCH v3] package/libressl: bump version to 4.4.0 Peter Seiderer via buildroot
2026-11-01 22:44 ` Thomas Petazzoni via buildroot
2026-11-02 13:44 ` Peter Seiderer via buildroot [this message]
2026-11-02 17:17 ` 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=20261102144441.33ea2f82@pc-1 \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=ps.report@gmx.net \
--cc=thomas.petazzoni@bootlin.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