[Buildroot] [git commit] package/amazon-ecr-credential-helper: needs NPTL

Julien Olivain via buildroot <[email protected]>
Newsgroups net.busybox.buildroot
Message-ID <[email protected]>
commit: https://gitlab.com/buildroot.org/buildroot/-/commit/7a7b0522b34c4ff39f1386b972ded7360191bc01
branch: https://gitlab.com/buildroot.org/buildroot/-/tree/master

amazon-ecr-credential-helper calls pthread_getattr_np() which is only
available with NPTL; i.e. always available with glibc (where it
originates from, since 2.2.3), always available with musl (which has
had it since 0.9.10 in 2013), and only available when uClibc has NPTL
(since 1.0.0 in 2015).

Fixes: https://autobuild.buildroot.org/results/4e6e13f1161485b412d4601cb8972a1524ddd2d6/

Signed-off-by: Yann E. MORIN <[email protected]>
Signed-off-by: Julien Olivain <[email protected]>
---
 package/amazon-ecr-credential-helper/Config.in | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/package/amazon-ecr-credential-helper/Config.in b/package/amazon-ecr-credential-helper/Config.in
index 93bfb51e4a..2efda5cd49 100644
--- a/package/amazon-ecr-credential-helper/Config.in
+++ b/package/amazon-ecr-credential-helper/Config.in
@@ -1,9 +1,14 @@
 config BR2_PACKAGE_AMAZON_ECR_CREDENTIAL_HELPER
 	bool "amazon-ecr-credential-helper"
 	depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
+	depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL  # pthread_*_np()
 	help
 	  The Amazon ECR Docker Credential Helper is a credential
 	  helper for the Docker daemon that makes it easier to use
 	  Amazon Elastic Container Registry.
 
 	  https://github.com/awslabs/amazon-ecr-credential-helper
+
+comment "amazon-ecr-credential-helper needs a toolchain w/ NPTL"
+	depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
+	depends on !BR2_TOOLCHAIN_HAS_THREADS_NPTL
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.