From: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH] Config.in.legacy: fix removed bootlin riscv64 toolchains
Date: Tue, 4 Jan 2022 18:11:28 +0100 [thread overview]
Message-ID: <20220104171128.956397-1-arnout@mind.be> (raw)
commit b3c66481e1f1503fcbf193d0c780271e880ad500 replaced RISC-V LP64
bootlin toolchains by RISC-V LP64D. However, Config.in.legacy was added
for BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_RISCV64_GLIBC_STABLE, which never
existed (the stable version was only added after the switch to LP64D).
Conversely, BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_RISCV64_MUSL_BLEEDING_EDGE,
which was removed, was not mentioned in Config.in.legacy.
Correct the symbol name and its comment in Config.in.legacy.
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
---
Config.in.legacy | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Config.in.legacy b/Config.in.legacy
index 5994d94487..e5349e58ac 100644
--- a/Config.in.legacy
+++ b/Config.in.legacy
@@ -153,8 +153,8 @@ config BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_RISCV64_GLIBC_BLEEDING_EDGE
The RISC-V 64-bit LP64 Bootlin toolchains have been removed,
in favor of RISC-V 64-bit LP64D toolchains.
-config BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_RISCV64_GLIBC_STABLE
- bool "Bootlin riscv64 glibc bleeding-edge toolchain removed"
+config BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_RISCV64_MUSL_BLEEDING_EDGE
+ bool "Bootlin riscv64 musl bleeding-edge toolchain removed"
select BR2_LEGACY
help
The RISC-V 64-bit LP64 Bootlin toolchains have been removed,
--
2.31.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-01-04 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 17:11 Arnout Vandecappelle (Essensium/Mind) [this message]
2022-01-04 22:14 ` [Buildroot] [PATCH] Config.in.legacy: fix removed bootlin riscv64 toolchains Yann E. MORIN
2022-01-05 7:54 ` Thomas Petazzoni
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=20220104171128.956397-1-arnout@mind.be \
--to=arnout@mind.be \
--cc=buildroot@buildroot.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