From: Peter Korsgaard <peter@korsgaard.com>
To: Damien Le Moal <damien.lemoal@wdc.com>
Cc: Alistair Francis <alistair@alistair23.me>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v5 03/10] package/Makefile.in: Fix NOMMU RISC-V 64-bits toolchain base name
Date: Wed, 27 Oct 2021 15:38:19 +0200 [thread overview]
Message-ID: <87lf2epoz8.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20211026071728.954356-4-damien.lemoal@wdc.com> (Damien Le Moal's message of "Tue, 26 Oct 2021 16:17:21 +0900")
>>>>> "Damien" == Damien Le Moal <damien.lemoal@wdc.com> writes:
> From: Christoph Hellwig <hch@lst.de>
> Using *-uclinux-* seems like an only partially followed convention.
> And at least RISC-V 64-bits gcc does not know about uclinux tuples.
> So switch back to the normal "linux" one for now.
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> [Damien]
> * Make the change conditional on BR2_RISCV_64 being "y".
> Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-10-27 13:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 7:17 [Buildroot] [PATCH v5 00/10] Add RV64 NOMMU and Canaan K210 SoC support Damien Le Moal
2021-10-26 7:17 ` [Buildroot] [PATCH v5 01/10] package: Makefile.in: fix elf2flt invocation options Damien Le Moal
2021-10-27 13:37 ` Peter Korsgaard
2021-10-26 7:17 ` [Buildroot] [PATCH v5 02/10] package/elf2flt: add RISC-V 64-bits support Damien Le Moal
2021-10-27 13:38 ` Peter Korsgaard
2021-10-28 0:35 ` Damien Le Moal
2021-10-28 6:30 ` Peter Korsgaard
2021-10-26 7:17 ` [Buildroot] [PATCH v5 03/10] package/Makefile.in: Fix NOMMU RISC-V 64-bits toolchain base name Damien Le Moal
2021-10-27 3:26 ` Alistair Francis
2021-10-27 13:38 ` Peter Korsgaard [this message]
2021-10-26 7:17 ` [Buildroot] [PATCH v5 04/10] arch/config: Make RISC-V 64-bits MMU optional Damien Le Moal
2021-10-27 13:38 ` Peter Korsgaard
2021-10-26 7:17 ` [Buildroot] [PATCH v5 05/10] board: Add Sipeed MAIX-bit support Damien Le Moal
2021-10-27 13:51 ` Peter Korsgaard
2021-10-28 1:07 ` Damien Le Moal
[not found] ` <e6eb0eda-20db-dfd6-c3d6-47db131bc247@gmail.com>
2021-10-28 2:24 ` Damien Le Moal
2021-10-28 7:01 ` Peter Korsgaard
2021-12-30 20:27 ` Thomas Petazzoni
2021-12-30 20:29 ` Thomas Petazzoni
2021-12-31 0:39 ` Damien Le Moal
2022-01-03 15:25 ` Thomas Petazzoni
2022-02-15 23:37 ` Damien Le Moal
2022-02-16 7:54 ` Thomas Petazzoni via buildroot
2021-10-26 7:17 ` [Buildroot] [PATCH v5 06/10] board: Add Sipeed MAIX-Go support Damien Le Moal
2021-10-26 7:17 ` [Buildroot] [PATCH v5 07/10] board: Add Sipeed MAIXDUINO support Damien Le Moal
2021-10-26 7:17 ` [Buildroot] [PATCH v5 08/10] board: Add Sipeed MAIX-Dock support Damien Le Moal
2021-10-26 7:17 ` [Buildroot] [PATCH v5 09/10] board: Add Canaan KD233 support Damien Le Moal
2021-10-26 7:17 ` [Buildroot] [PATCH v5 10/10] board: Document Canaan K210 based boards support Damien Le Moal
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=87lf2epoz8.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=alistair@alistair23.me \
--cc=buildroot@buildroot.org \
--cc=damien.lemoal@wdc.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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