From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: buildroot@buildroot.org, Pierre-Jean Texier <texier.pj2@gmail.com>
Subject: Re: [Buildroot] [PATCH v2] package/stunnel: fix build on ARM Thumb-1
Date: Sun, 20 Sep 2026 15:45:15 +0200 [thread overview]
Message-ID: <aq_jZkrdAW8uhOCa@windsurf> (raw)
In-Reply-To: <20260917125242.1307618-1-yegorslists@gmail.com>
On Thu, Sep 17, 2026 at 02:52:42PM +0200, Yegor Yefremov via buildroot wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> stunnel's configure unconditionally probes -fstack-clash-protection
> using AX_APPEND_COMPILE_FLAGS. The probe compiles a trivial conftest.c,
> which succeeds, so the flag ends up in CFLAGS. However, on ARM Thumb-1
> gcc implements stack clash protection through -fstack-check=specific,
> which it refuses for any real function body, so every source file fails
> to build:
>
> stunnel.c:1003:1: sorry, unimplemented: '-fstack-check=specific' for Thumb-1
>
> Force the corresponding autoconf cache variable to "no" on Thumb-1, in
> the same way cmocka already works around this gcc limitation, and
> consistently with the existing -fstack-protector-strong override.
>
> Fixes:
> https://autobuild.buildroot.org/results/3d691184ba83ba4d881632f2b2bb4da5aa50f491/
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> Assisted-by: Claude:claude-opus-5
Applied to master, thanks!
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-09-20 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 12:52 [Buildroot] [PATCH v2] package/stunnel: fix build on ARM Thumb-1 Yegor Yefremov via buildroot
2026-09-20 13:45 ` Thomas Petazzoni via buildroot [this message]
2026-09-25 14:46 ` Raphaël Mélotte 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=aq_jZkrdAW8uhOCa@windsurf \
--to=buildroot@buildroot.org \
--cc=texier.pj2@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yegorslists@googlemail.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