Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/3] support/config-fragments: use external riscv64 musl toolchain
Date: Mon, 27 Jul 2020 21:08:08 +0200	[thread overview]
Message-ID: <20200727210808.42f5716b@windsurf.home> (raw)
In-Reply-To: <20200510154347.5711-3-mark@dibsco.co.uk>

On Sun, 10 May 2020 16:43:47 +0100
Mark Corbin <mark@dibsco.co.uk> wrote:

> Move to an external RISC-V 64 bit musl toolchain to ease the load
> on the autobuilders.
> 
> Signed-off-by: Mark Corbin <mark@dibsco.co.uk>
> ---
>  .../autobuild/br-riscv64-internal-musl.config            | 3 ---
>  .../config-fragments/autobuild/br-riscv64-musl.config    | 9 +++++++++
>  2 files changed, 9 insertions(+), 3 deletions(-)
>  delete mode 100644 support/config-fragments/autobuild/br-riscv64-internal-musl.config
>  create mode 100644 support/config-fragments/autobuild/br-riscv64-musl.config

Here as well, you had forgotten to update
support/config-fragments/autobuild/toolchain-configs.csv, so I did that
when applying. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2020-07-27 19:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-10 15:43 [Buildroot] [PATCH v2 1/3] toolchain/toolchain-buildroot: enable uclibc for riscv64 Mark Corbin
2020-05-10 15:43 ` [Buildroot] [PATCH v2 2/3] support/config-fragments: add RISC-V 64-bit uclibc autobuild config Mark Corbin
2020-07-13 21:59   ` Romain Naour
2020-07-27 19:07   ` Thomas Petazzoni
2020-05-10 15:43 ` [Buildroot] [PATCH v2 3/3] support/config-fragments: use external riscv64 musl toolchain Mark Corbin
2020-07-13 22:06   ` Romain Naour
2020-07-27 19:08   ` Thomas Petazzoni [this message]
2020-07-13 21:50 ` [Buildroot] [PATCH v2 1/3] toolchain/toolchain-buildroot: enable uclibc for riscv64 Romain Naour
2020-07-13 21:52   ` Romain Naour
2020-07-27 16:04 ` 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=20200727210808.42f5716b@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