From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [git commit] package/docker-credential-gcr: needs NPTL
Date: Mon, 20 Jul 2026 21:39:15 +0200 [thread overview]
Message-ID: <20260720194229.2D3AC8907B@busybox.osuosl.org> (raw)
commit: https://gitlab.com/buildroot.org/buildroot/-/commit/12002ceeefa496e62f09e3fa324eb01f04ff7d73
branch: https://gitlab.com/buildroot.org/buildroot/-/tree/master
docker-credential-gcr 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/3ed18da254082b7823b49be4578274792bb7380e/
Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
Signed-off-by: Julien Olivain <ju.o@free.fr>
---
package/docker-credential-gcr/Config.in | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/package/docker-credential-gcr/Config.in b/package/docker-credential-gcr/Config.in
index 1b24ff0e59..6845d5e198 100644
--- a/package/docker-credential-gcr/Config.in
+++ b/package/docker-credential-gcr/Config.in
@@ -1,6 +1,7 @@
config BR2_PACKAGE_DOCKER_CREDENTIAL_GCR
bool "docker-credential-gcr"
depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
+ depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL # pthread_*_np()
help
docker-credential-gcr is Google Container Registry's
standalone, gcloud SDK-independent Docker credential
@@ -9,3 +10,7 @@ config BR2_PACKAGE_DOCKER_CREDENTIAL_GCR
eu.gcr.io, etc.).
https://github.com/GoogleCloudPlatform/docker-credential-gcr/
+
+comment "docker-credential-gcr needs a toolchain w/ NPTL"
+ depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
+ depends on !BR2_TOOLCHAIN_HAS_THREADS_NPTL
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2026-07-20 19:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260720194229.2D3AC8907B@busybox.osuosl.org \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
/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