From: Jamie Gibbons via buildroot <buildroot@buildroot.org>
To: <buildroot@buildroot.org>
Cc: Conor Dooley <Conor.Dooley@microchip.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Valentina Fernandez Alanis
<Valentina.FernandezAlanis@microchip.com>,
Jamie Gibbons <jamie.gibbons@microchip.com>
Subject: [Buildroot] [PATCH 1/1] configs/microchip_mpfs_icicle_defconfig: fix zicsr build error
Date: Tue, 19 Sep 2023 09:10:12 +0100 [thread overview]
Message-ID: <20230919081012.529819-1-jamie.gibbons@microchip.com> (raw)
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>
---
configs/microchip_mpfs_icicle_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configs/microchip_mpfs_icicle_defconfig b/configs/microchip_mpfs_icicle_defconfig
index 54a4d55a5f..c003f70798 100644
--- a/configs/microchip_mpfs_icicle_defconfig
+++ b/configs/microchip_mpfs_icicle_defconfig
@@ -1,7 +1,7 @@
BR2_riscv=y
-BR2_riscv_g=y
BR2_RISCV_ISA_RVC=y
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_1=y
+BR2_GCC_VERSION_11_X=y
BR2_TARGET_GENERIC_HOSTNAME="mpfs_icicle"
BR2_ROOTFS_POST_IMAGE_SCRIPT="board/microchip/mpfs_icicle/post-image.sh"
BR2_LINUX_KERNEL=y
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-09-19 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 8:10 Jamie Gibbons via buildroot [this message]
2023-09-19 8:41 ` [Buildroot] [PATCH 1/1] configs/microchip_mpfs_icicle_defconfig: fix zicsr build error Thomas Petazzoni via buildroot
-- 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=20230919081012.529819-1-jamie.gibbons@microchip.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox