From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/pistache: needs NPTL
Date: Tue, 03 Sep 2024 18:26:31 +0200 [thread overview]
Message-ID: <87zfooog94.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20240723132058.629476-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Tue, 23 Jul 2024 15:20:58 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> pistache needs NPTL as it unconditionally uses pthread_setname_np since
> https://github.com/pistacheio/pistache/commit/b283c32963a7cb0500cf69555d320a6e9e252850
> resulting in the following uclibc build failure since commit
> 82e61bed8208857d5d13c384c89086c4dd4e1e79:
> ../src/common/reactor.cc: In lambda function:
> ../src/common/reactor.cc:512:25: error: 'pthread_setname_np' was not
> declared in this scope; did you mean 'pthread_setcanceltype'?
> 512 | pthread_setname_np(pthread_self(),
> | ^~~~~~~~~~~~~~~~~~
> | pthread_setcanceltype
> Fixes: 82e61bed8208857d5d13c384c89086c4dd4e1e79
> - http://autobuild.buildroot.org/results/b2b22e4f9684aca0246650673fd8c33019712ddf
> - http://autobuild.buildroot.org/results/1597bfe2a57cd3aef54d331447dd81cae020d434
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2024.02.x and 2024.05.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-09-03 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 13:20 [Buildroot] [PATCH 1/1] package/pistache: needs NPTL Fabrice Fontaine
2024-08-02 17:51 ` Thomas Petazzoni via buildroot
2024-09-03 16:26 ` Peter Korsgaard [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=87zfooog94.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.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 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.