From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] domoticz: depends on NPTL
Date: Mon, 29 Jan 2018 22:25:16 +0100 [thread overview]
Message-ID: <20180129222516.22768129@windsurf.lan> (raw)
In-Reply-To: <87k1w05sww.fsf@dell.be.48ers.dk>
Hello,
On Mon, 29 Jan 2018 21:09:03 +0100, Peter Korsgaard wrote:
> > boost 1.66 uses pthread_condattr_setclock in
> > boost/asio/detail/impl/posix_event.ipp so add a dependency to
> > BR2_TOOLCHAIN_HAS_THREADS_NPTL
>
> Shouldn't boost then depend on BR2_TOOLCHAIN_HAS_THREADS_NPTL (and
> domoticz enherit it), or is this code only used in special cases?
Well, Boost is mostly a header-only library, in particular the asio
stuff I believe. While we have sub-options for the parts of Boost that
are not purely headers, we don't have any sub-options for the parts of
Boost that are just headers.
So, the options are either to add sub-options to Boost, or to make
Boost as a whole only available on NPTL toolchains. The latter is a bit
annoying as it would mean adding this dependency to all Boost reverse
dependencies, even those not using asio.
So I think Fabrice's patch is the best solution we can have today. I'm
not saying it's perfect, but it's good enough IMO.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2018-01-29 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 11:28 [Buildroot] [PATCH 1/1] domoticz: depends on NPTL Fabrice Fontaine
2018-01-29 20:09 ` Peter Korsgaard
2018-01-29 21:25 ` Thomas Petazzoni [this message]
2018-01-29 21:50 ` Peter Korsgaard
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=20180129222516.22768129@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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