From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] toolchain: enable musl for riscv
Date: Tue, 30 Jul 2019 17:46:05 +0200 [thread overview]
Message-ID: <20190730174605.4481ad0d@windsurf> (raw)
In-Reply-To: <20190730102331.25609-2-joerg.krause@embedded.rocks>
Hello,
On Tue, 30 Jul 2019 12:23:31 +0200
J?rg Krause <joerg.krause@embedded.rocks> wrote:
> Since version 1.1.23 musl supports the RISC-V architecture.
>
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
> toolchain/toolchain-buildroot/Config.in | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/toolchain/toolchain-buildroot/Config.in b/toolchain/toolchain-buildroot/Config.in
> index d9f16e2a3a..b4168bd40c 100644
> --- a/toolchain/toolchain-buildroot/Config.in
> +++ b/toolchain/toolchain-buildroot/Config.in
> @@ -84,7 +84,7 @@ config BR2_TOOLCHAIN_BUILDROOT_MUSL
> depends on BR2_aarch64 || BR2_arm || BR2_armeb || BR2_i386 || \
> BR2_microblaze || BR2_mips || BR2_mipsel || BR2_mips64 || \
> BR2_mips64el || BR2_or1k || BR2_powerpc || BR2_powerpc64 || \
> - BR2_powerpc64le || BR2_sh || BR2_x86_64
> + BR2_powerpc64le || BR2_riscv || BR2_sh || BR2_x86_64
My understanding is that musl 1.1.23 only supports RISC-V 64 bits, not
RISC-V 32 bits, so that should probably be "BR2_RISCV_64" instead of
just "BR2_riscv".
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-07-30 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 10:23 [Buildroot] [PATCH 1/2] package/musl: bump to version 1.1.23 Jörg Krause
2019-07-30 10:23 ` [Buildroot] [PATCH 2/2] toolchain: enable musl for riscv Jörg Krause
2019-07-30 14:28 ` Mark Corbin
2019-07-30 15:46 ` Thomas Petazzoni [this message]
2019-07-30 16:25 ` Peter Korsgaard
2019-07-30 15:54 ` Peter Korsgaard
2019-07-30 14:27 ` [Buildroot] [PATCH 1/2] package/musl: bump to version 1.1.23 Mark Corbin
2019-07-30 15:53 ` Peter Korsgaard
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=20190730174605.4481ad0d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.