From: Peter Maydell <peter.maydell@linaro.org>
To: Vineet Gupta <vineetg@rivosinc.com>
Cc: Alistair Francis <alistair.francis@wdc.com>,
gnu-toolchain@rivosinc.com, Palmer Dabbelt <palmer@dabbelt.com>,
qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Subject: Re: [PATCH] build: fix build failure with gcc 11.2 by disabling -fcf-protection
Date: Fri, 18 Feb 2022 13:13:59 +0000 [thread overview]
Message-ID: <CAFEAcA8-h2TH0kG64mec6Yu6MTTSKOVTpVAToqA167MYWa4ZxQ@mail.gmail.com> (raw)
In-Reply-To: <20220208211937.79580-1-vineetg@rivosinc.com>
On Tue, 8 Feb 2022 at 21:29, Vineet Gupta <vineetg@rivosinc.com> wrote:
>
> When doing RV qemu builds with host gcc 11.2, ran into following build failure
>
> | cc -MMD -MP -MT linuxboot_dma.o -MF ./linuxboot_dma.d -O2 -g -march=i486 -Wall \
> | -Wstrict-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes \
> | -Wold-style-declaration -Wold-style-definition -Wtype-limits -Wformat-security \
> | -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wnested-externs \
> | -Wendif-labels -Wexpansion-to-defined -Wimplicit-fallthrough=2 -Wno-missing-include-dirs \
> | -Wno-shift-negative-value -Wno-psabi -fno-pie -ffreestanding -IQEMU/include \
> | -fno-stack-protector -m16 -Wa,-32 \
> | -c QEMU/pc-bios/optionrom/linuxboot_dma.c -o linuxboot_dma.o
> |cc1: error: ‘-fcf-protection’ is not compatible with this target
>
> Signed-off-by: Vineet Gupta <vineetg@rivosinc.com>
> ---
> This might be a crude fix to the problem
I think this patch
https://patchew.org/QEMU/20220103090112.312202-1-bjorn@kernel.org/
fixes the same problem...
thanks
-- PMM
next prev parent reply other threads:[~2022-02-18 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 21:19 [PATCH] build: fix build failure with gcc 11.2 by disabling -fcf-protection Vineet Gupta
2022-02-18 13:13 ` Peter Maydell [this message]
2022-02-18 15:47 ` Paolo Bonzini
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=CAFEAcA8-h2TH0kG64mec6Yu6MTTSKOVTpVAToqA167MYWa4ZxQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=gnu-toolchain@rivosinc.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=vineetg@rivosinc.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;
as well as URLs for NNTP newsgroup(s).