From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/6] toolchain/buildroot: allow uclibc-ng for riscv
Date: Tue, 6 Oct 2020 23:40:12 +0200 [thread overview]
Message-ID: <20201006234012.6b3c2697@windsurf.home> (raw)
In-Reply-To: <20200908113324.1022230-2-damien.lemoal@wdc.com>
Hello,
On Tue, 8 Sep 2020 20:33:19 +0900
Damien Le Moal <damien.lemoal@wdc.com> wrote:
> diff --git a/package/uclibc/Config.in b/package/uclibc/Config.in
> index de2885bc92..35b1cb8e2f 100644
> --- a/package/uclibc/Config.in
> +++ b/package/uclibc/Config.in
> @@ -106,6 +106,8 @@ config BR2_UCLIBC_TARGET_ARCH
> default "xtensa" if BR2_xtensa
> default "i386" if BR2_i386
> default "x86_64" if BR2_x86_64
> + default "riscv64" if BR2_riscv && BR2_ARCH_IS_64
> + default "riscv32" if BR2_riscv && !BR2_ARCH_IS_6
There was a typo here: BR2_ARCH_IS_6 was truncated.
> diff --git a/toolchain/toolchain-buildroot/Config.in b/toolchain/toolchain-buildroot/Config.in
> index 418d5cb387..49f67c7348 100644
> --- a/toolchain/toolchain-buildroot/Config.in
> +++ b/toolchain/toolchain-buildroot/Config.in
> @@ -32,7 +32,9 @@ config BR2_TOOLCHAIN_BUILDROOT_UCLIBC
> BR2_i386 || BR2_m68k || BR2_microblaze || \
> BR2_mips || BR2_mipsel || BR2_mips64 || BR2_mips64el || \
> BR2_or1k || BR2_powerpc || BR2_sh2a || BR2_sh4 || \
> - BR2_sh4eb || BR2_sparc || BR2_xtensa || BR2_x86_64
> + BR2_sh4eb || BR2_sparc || BR2_xtensa || BR2_x86_64 || \
> + BR2_riscv
I fixed the alphabetic ordering.
> +
Dropped the empty new line.
And applied with some small improvements to the commit log as well.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-10-06 21:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 11:33 [Buildroot] [PATCH v2 0/6] Add support for Kendryte K210 RISC-V boards Damien Le Moal
2020-09-08 11:33 ` [Buildroot] [PATCH v2 1/6] toolchain/buildroot: allow uclibc-ng for riscv Damien Le Moal
2020-09-08 21:49 ` Yann E. MORIN
2020-10-06 21:40 ` Thomas Petazzoni [this message]
2020-10-06 22:53 ` Damien Le Moal
2020-10-08 19:33 ` Thomas Petazzoni
2020-10-12 5:00 ` Damien Le Moal
2020-10-12 5:18 ` Waldemar Brodkorb
2020-10-12 5:28 ` Damien Le Moal
2020-09-08 11:33 ` [Buildroot] [PATCH v2 2/6] arch/config: Make RISC-V MMU optional Damien Le Moal
2020-09-09 17:44 ` Alistair Francis
2020-10-06 21:46 ` Thomas Petazzoni
2020-10-06 22:58 ` Damien Le Moal
2020-09-08 11:33 ` [Buildroot] [PATCH v2 3/6] package/elf2flt: add RISC-V support Damien Le Moal
2020-09-09 6:45 ` Peter Korsgaard
2020-09-09 6:48 ` Damien Le Moal
2020-10-06 21:47 ` Thomas Petazzoni
2020-10-06 23:14 ` Damien Le Moal
2020-09-08 11:33 ` [Buildroot] [PATCH v2 4/6] package make: build RISC-V nommu builds as linux Damien Le Moal
2020-09-08 21:56 ` Yann E. MORIN
2020-09-08 11:33 ` [Buildroot] [PATCH v2 5/6] package/uclibc: fix compilation errors Damien Le Moal
2020-09-08 22:06 ` Yann E. MORIN
2020-09-09 5:38 ` Petr Vorel
2020-09-09 6:21 ` Damien Le Moal
2020-10-06 21:49 ` Thomas Petazzoni
2020-10-06 23:14 ` Damien Le Moal
2020-09-08 11:33 ` [Buildroot] [PATCH v2 6/6] board: Add configuration for Kendryte K210 boards Damien Le Moal
2020-09-09 6:49 ` [Buildroot] [PATCH v2 0/6] Add support for Kendryte K210 RISC-V boards 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=20201006234012.6b3c2697@windsurf.home \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox