From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14651] OpenSSH 8.9p1 compiler error under ARM
Date: Wed, 09 Mar 2022 21:44:20 +0000 [thread overview]
Message-ID: <bug-14651-163-cX3QG58rvm@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14651-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14651
--- Comment #1 from Peter Seiderer <ps.report@gmx.net> ---
(In reply to mf from comment #0)
- from build/openssh-8.9p1/ChangeLog:
2692 commit 39f2111b1d5f00206446257377dcce58cc72369f
2693 Author: Darren Tucker <dtucker@dtucker.net>
2694 Date: Wed Sep 29 10:53:55 2021 +1000
2695
2696 Add new compiler hardening flags.
2697
2698 Add -fzero-call-used-regs and -ftrivial-auto-var-init to the list of
2699 compiler hardening flags that configure checks for. These are
support ed
2700 by clang and gcc, and make ROP gadgets less useful and mitigate
2701 stack-based infoleaks respectively. ok djm@
- from openssh-8.9p1/configure.ac:
195 OSSH_CHECK_CFLAG_COMPILE([-fzero-call-used-regs=all])
- from build/openssh-8.9p1/config.log:
716 configure:6832: checking if
.../host/bin/arm-buildroot-linux-gnueabihf-gcc supports compile flag
-fzero-call-used-regs=all
717 configure:6865: .../hos t/bin/arm-buildroot-linux-gnueabihf-gcc -c
-D_LARGEFILE_SOURCE -D_LARGEFIL E64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -g0
-D_FORTIFY_SOURCE=1 -pipe -Wno- error=format-truncation -Wall -Wextra
-Wpointer-arith -Wuninitialized -Wsi gn-compare -Wformat-security
-Wsizeof-pointer-memaccess -Wno-pointer-sign -Wno-unused-parameter
-Wno-unused-result -Wimplicit-fallthrough -Wmisleadi ng-indentation
-fno-strict-aliasing -ftrapv -Werror -fzero-call-used-regs= all
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 conft
est.c >&5
718 arm-buildroot-linux-gnueabihf-gcc.br_real: error: unrecognized
command-lin e option '-fzero-call-used-regs=all'
[...]
766 configure:6878: result: no
So 'zero-call-used-regs' not supported (gcc-10.3, raspberrypi0w_defconfig) is
detected correctly here...
Same test with gcc-11.2, from build/openssh-8.9p1/config.log:
configure:6832: checking if .../host/bin/arm-buildroot-linux-gnueabihf-gcc
supports compile flag -fzero-call-used-regs=all
configure:6865: .../host/bin/arm-buildroot-linux-gnueabihf-gcc -c
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -g0
-D_FORTIFY_SOURCE=1 -pipe -Wno-error=format-truncation -Wall -Wextra
-Wpointer-arith -Wuninitialized -Wsign-compare -Wformat-security
-Wsizeof-pointer-memaccess -Wno-pointer-sign -Wno-unused-parameter
-Wno-unused-result -Wimplicit-fallthrough -Wmisleading-indentation
-fno-strict-aliasing -ftrapv -Werror -fzero-call-used-regs=all
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 conftest.c >&5
configure:6865: $? = 0
configure:6873: result: yes
Which compiler do you use? For which target do you compile?
Can you provide a failing .config/defconfig file?
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-03-09 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 9:58 [Buildroot] [Bug 14651] New: OpenSSH 8.9p1 compiler error under ARM bugzilla
2022-03-09 21:44 ` bugzilla [this message]
2022-03-10 9:19 ` [Buildroot] [Bug 14651] " bugzilla
2022-03-10 9:22 ` bugzilla
2022-03-10 20:23 ` bugzilla
2022-03-19 21:50 ` bugzilla
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=bug-14651-163-cX3QG58rvm@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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