From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Jamie Gibbons via buildroot <buildroot@buildroot.org>
Cc: Valentina Fernandez Alanis
<Valentina.FernandezAlanis@microchip.com>,
Jamie Gibbons <jamie.gibbons@microchip.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
Conor Dooley <Conor.Dooley@microchip.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>
Subject: Re: [Buildroot] [PATCH 1/1] configs/microchip_mpfs_icicle_defconfig: fix zicsr build error
Date: Tue, 19 Sep 2023 10:41:21 +0200 [thread overview]
Message-ID: <20230919104121.4d55e084@windsurf> (raw)
In-Reply-To: <20230919081012.529819-1-jamie.gibbons@microchip.com>
Hello Jamie,
On Tue, 19 Sep 2023 09:10:12 +0100
Jamie Gibbons via buildroot <buildroot@buildroot.org> wrote:
> Build is failing with an unrecognised opcode error due to missing
> `zicsr` extension requirement. This is introduced with GCC version 12.
> All our current defconfigs use GCC version 11. Add GCC version 11
> kconfig to fix this build error and align with our downstream
> Buildroot-External defconfigs.
>
> Signed-off-by: Jamie Gibbons <jamie.gibbons@microchip.com>
Hm, we really want to fix this the proper, aka make this work with GCC
12+. Indeed as soon as GCC 14.x lands, we will drop support for GCC
11.x, so the solution proposed here really isn't suitable :-/
Best regards,
Thomas
--
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:[~2023-09-19 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 8:10 [Buildroot] [PATCH 1/1] configs/microchip_mpfs_icicle_defconfig: fix zicsr build error Jamie Gibbons via buildroot
2023-09-19 8:41 ` Thomas Petazzoni via buildroot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-02 10:53 Jamie Gibbons via buildroot
2023-11-01 10:52 ` Jamie.Gibbons--- via buildroot
2023-11-01 12:56 ` Yann E. MORIN
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=20230919104121.4d55e084@windsurf \
--to=buildroot@buildroot.org \
--cc=Conor.Dooley@microchip.com \
--cc=Valentina.FernandezAlanis@microchip.com \
--cc=jamie.gibbons@microchip.com \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.