From: ruggero rossi via ptxdist <ptxdist@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: ruggero rossi <rugrossi@googlemail.com>
Subject: [ptxdist] PTXDIST 2025.09.0: build failure of openssl-3.5.2 when gcc option -fzero-call-used-regs is not supported
Date: Wed, 17 Sep 2025 08:32:39 +0200 [thread overview]
Message-ID: <20250917083239.145112e9@RR-Laptop> (raw)
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
Hello everybody,
On my system, the gcc toolchain does not support the
-fzero-call-used-regs option.
With PTXDIST 2025.09.0 this causes the build of OpenSSL 3.5.2 to fail.
An ad-hoc patch is trivial:
I removed the -fzero-call-used-regs=used-gpr flag from
openssl-3.5.2/Configurations/20-debian.conf (see attached patch).
My question is: would it be possible to integrate a more general solution
into PTXDIST, so that the build works regardless of whether the toolchain
supports this GCC option?
Best regards,
Ruggero Rossi
[-- Attachment #2: 0005-no-fzero-call-used-regs.patch --]
[-- Type: text/x-patch, Size: 469 bytes --]
Index: openssl-3.5.2/Configurations/20-debian.conf
===================================================================
--- openssl-3.5.2.orig/Configurations/20-debian.conf
+++ openssl-3.5.2/Configurations/20-debian.conf
@@ -1,6 +1,6 @@
my %targets = (
"debian" => {
- cflags => add("-Wa,--noexecstack -Wall -fzero-call-used-regs=used-gpr"),
+ cflags => add("-Wa,--noexecstack -Wall"),
},
"debian-alpha" => {
inherit_from => [ "linux-alpha-gcc", "debian" ],
next reply other threads:[~2025-09-17 6:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 6:32 ruggero rossi via ptxdist [this message]
2025-09-17 8:30 ` Christian Melki
2025-09-17 9:00 ` ruggero rossi via ptxdist
2025-09-17 9:18 ` Christian Melki
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=20250917083239.145112e9@RR-Laptop \
--to=ptxdist@pengutronix.de \
--cc=rugrossi@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