From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] boost: thread depends on NPTL
Date: Mon, 25 Jun 2018 23:20:10 +0200 [thread overview]
Message-ID: <20180625232010.019e5b8d@windsurf.home> (raw)
In-Reply-To: <20180625211317.12643-1-fontaine.fabrice@gmail.com>
Hello,
On Mon, 25 Jun 2018 23:13:17 +0200, Fabrice Fontaine wrote:
> - Since boost 1.67, CLOCK_MONOTONIC is used by default, there is no more
> check on pthread_condaddr_setclock availability:
> https://github.com/boostorg/thread/commit/1e84b978b2bb0aae830cc14533dea3b7ddda5cde
> - So add NPTL dependency on boost-thread but also on boost-contract,
> boost-locale, boost-type_erasure and boost-wave which use
> boost-thread (and select it even if boost will do it on its own)
> - Add also NPTL dependency to pulseview
> - Update comment on NPTL in azmq
>
> Fixes:
> - http://autobuild.buildroot.net/results/7db2baeb70b30f7785cbb823e9eaeb8e99ef0d24
> - http://autobuild.buildroot.net/results/6a4c5f8d45b51d32114093fa68195c2df2db5449
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
pthread_condattr_setclock() is now implemented in linuxthreads in
uClibc-ng starting version 1.0.30. I think I should instead rebuild the
pre-built toolchains rather than adding this NPTL dependency.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-06-25 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 21:13 [Buildroot] [PATCH 1/1] boost: thread depends on NPTL Fabrice Fontaine
2018-06-25 21:20 ` Thomas Petazzoni [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=20180625232010.019e5b8d@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--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