Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: yann.morin@orange.com
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/docker-credential-gcr: needs NPTL
Date: Fri, 31 Jul 2026 14:21:51 +0200	[thread overview]
Message-ID: <20260731122151.155473-1-thomas.perale@mind.be> (raw)
In-Reply-To: <81e1623bc37fdedb5cd3e4b9268fa03b45af65a6.1784526170.git.yann.morin@orange.com>

In reply of:
> 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>

Applied to 2026.05.x. Thanks

> ---
>  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
> -- 
> 2.34.1
> 
> ____________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-07-31 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20  5:42 [Buildroot] [PATCH] package/docker-credential-gcr: needs NPTL yann.morin
2026-07-20 19:43 ` Julien Olivain via buildroot
2026-07-31 12:21 ` Thomas Perale via buildroot [this message]

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=20260731122151.155473-1-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=thomas.perale@mind.be \
    --cc=yann.morin@orange.com \
    /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