Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] musl: enable or1k architecture
Date: Thu, 30 Nov 2017 07:00:28 +0100	[thread overview]
Message-ID: <20171130060027.GA25417@waldemar-brodkorb.de> (raw)

With Linux kernel >= 4.13.x musl or1k can be used
with Qemu.

Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
 toolchain/toolchain-buildroot/Config.in | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/toolchain/toolchain-buildroot/Config.in b/toolchain/toolchain-buildroot/Config.in
index c624350cac..9668f8d41a 100644
--- a/toolchain/toolchain-buildroot/Config.in
+++ b/toolchain/toolchain-buildroot/Config.in
@@ -79,10 +79,10 @@ comment "glibc on MIPS w/ NAN2008 needs a toolchain w/ headers >= 4.5"
 
 config BR2_TOOLCHAIN_BUILDROOT_MUSL
 	bool "musl"
-	depends on BR2_aarch64	  || BR2_arm     || BR2_armeb     || BR2_i386 || \
-		   BR2_microblaze || BR2_mips    || BR2_mipsel    || BR2_mips64 || \
-		   BR2_mips64el   || BR2_powerpc || BR2_powerpc64 || BR2_powerpc64le || \
-		   BR2_sh         || BR2_x86_64
+	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
 	depends on !BR2_powerpc_SPE # not supported, build breaks
 	# sh2 nommu is supported by musl, but we don't have support
 	# for it in Buildroot.
-- 
2.11.0

             reply	other threads:[~2017-11-30  6:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30  6:00 Waldemar Brodkorb [this message]
2017-11-30  7:57 ` [Buildroot] [PATCH 3/3] musl: enable or1k architecture Thomas Petazzoni
2017-11-30 10:15   ` Waldemar Brodkorb

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=20171130060027.GA25417@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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