Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Corbin <mark@dibsco.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] support/config-fragments: add RISC-V 64-bit uclibc autobuild config
Date: Sun, 10 May 2020 16:43:46 +0100	[thread overview]
Message-ID: <20200510154347.5711-2-mark@dibsco.co.uk> (raw)
In-Reply-To: <20200510154347.5711-1-mark@dibsco.co.uk>

Add a RISC-V 64-bit autobuild configuration for the internal
toolchain with uclibc.

Signed-off-by: Mark Corbin <mark@dibsco.co.uk>
---
Changes v1 -> v2:
  - acknowledge that this only adds a uclibc autobuilder configuration
    and not a generic one (Thomas P)
---
 .../config-fragments/autobuild/br-riscv64-full-internal.config  | 2 ++
 1 file changed, 2 insertions(+)
 create mode 100644 support/config-fragments/autobuild/br-riscv64-full-internal.config

diff --git a/support/config-fragments/autobuild/br-riscv64-full-internal.config b/support/config-fragments/autobuild/br-riscv64-full-internal.config
new file mode 100644
index 0000000000..c729eb55e9
--- /dev/null
+++ b/support/config-fragments/autobuild/br-riscv64-full-internal.config
@@ -0,0 +1,2 @@
+BR2_riscv=y
+BR2_TOOLCHAIN_BUILDROOT_CXX=y
-- 
2.20.1

  reply	other threads:[~2020-05-10 15:43 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 ` Mark Corbin [this message]
2020-07-13 21:59   ` [Buildroot] [PATCH v2 2/3] support/config-fragments: add RISC-V 64-bit uclibc autobuild config 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
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=20200510154347.5711-2-mark@dibsco.co.uk \
    --to=mark@dibsco.co.uk \
    --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