Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] samba4: requires NPTL
Date: Fri, 17 Feb 2017 21:24:03 +0100	[thread overview]
Message-ID: <20170217202403.GA13945@waldemar-brodkorb.de> (raw)

With OpenRISC there is a uClibc-ng based toolchain for an
architecture with MMU support, but with only Linuxthreads
and no NPTL. Samba4 uses pthread_mutexattr_setrobust which
is not implemented in uClibc-ng Linuxthreads.

Fixes:
  http://autobuild.buildroot.net/results/ec8f078046c92ae23dc973c88ac0fef136ad1535

Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
 package/samba4/Config.in | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/package/samba4/Config.in b/package/samba4/Config.in
index ce97bea..4474185 100644
--- a/package/samba4/Config.in
+++ b/package/samba4/Config.in
@@ -1,7 +1,7 @@
-comment "samba4 needs a toolchain w/ RPC, wchar, dynamic library, threads"
+comment "samba4 needs a toolchain w/ RPC, wchar, dynamic library, NPTL"
 	depends on BR2_TOOLCHAIN_HAS_SYNC_4
 	depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_NATIVE_RPC \
-		|| BR2_STATIC_LIBS || !BR2_TOOLCHAIN_HAS_THREADS
+		|| BR2_STATIC_LIBS || !BR2_TOOLCHAIN_HAS_THREADS_NPTL
 	depends on BR2_USE_MMU
 
 config BR2_PACKAGE_SAMBA4
@@ -9,7 +9,7 @@ config BR2_PACKAGE_SAMBA4
 	depends on BR2_USE_MMU # fork()
 	depends on BR2_USE_WCHAR # python
 	depends on BR2_TOOLCHAIN_HAS_NATIVE_RPC
-	depends on BR2_TOOLCHAIN_HAS_THREADS # python -> libffi
+	depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL # python -> libffi
 	depends on !BR2_STATIC_LIBS # python
 	depends on !BR2_nios2 # binary too large, relocations don't fit
 	depends on BR2_TOOLCHAIN_HAS_SYNC_4
-- 
2.1.4

             reply	other threads:[~2017-02-17 20:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 20:24 Waldemar Brodkorb [this message]
2017-02-18  9:39 ` [Buildroot] [PATCH] samba4: requires NPTL Peter Korsgaard

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=20170217202403.GA13945@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