All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mircea GLIGA <mgliga@bitdefender.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/uclibc: enable linuxthreads for all supported architectures
Date: Fri, 21 May 2021 16:41:22 +0300	[thread overview]
Message-ID: <20210521134122.122426-1-mgliga@bitdefender.com> (raw)
In-Reply-To: <20210521095924.52527-1-mgliga@bitdefender.com>

Synchronize the list of architectures that have LinuxThreads support
with the ones from uClibc-ng.

Signed-off-by: Mircea GLIGA <mgliga@bitdefender.com>
---
Changes v1 -> v2:
  - enable linuxthreads for all supported architectures,
    not just MIPS (suggested by Yann E. MORIN)
---
 package/uclibc/Config.in | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/package/uclibc/Config.in b/package/uclibc/Config.in
index e59fef3c69..2091166b62 100644
--- a/package/uclibc/Config.in
+++ b/package/uclibc/Config.in
@@ -53,7 +53,8 @@ config BR2_PTHREADS_NATIVE
 
 config BR2_PTHREADS
 	bool "linuxthreads"
-	depends on BR2_m68k || BR2_microblaze || BR2_or1k || BR2_arm || BR2_armeb || BR2_xtensa
+	depends on !BR2_aarch64 && !BR2_aarch64_be
+	depends on !BR2_RISCV_64
 	select BR2_TOOLCHAIN_HAS_THREADS
 
 config BR2_PTHREADS_NONE
-- 
2.31.1

  parent reply	other threads:[~2021-05-21 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21  9:59 [Buildroot] [PATCH 1/1] package/uclibc: enable linuxthreads for MIPS Mircea GLIGA
2021-05-21 10:30 ` Yann E. MORIN
2021-05-21 11:36   ` Mircea GLIGA
2021-05-21 13:41 ` Mircea GLIGA [this message]
2021-05-21 16:53   ` [Buildroot] [PATCH v2] package/uclibc: enable linuxthreads for all supported architectures Yann E. MORIN

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=20210521134122.122426-1-mgliga@bitdefender.com \
    --to=mgliga@bitdefender.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.