From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] rt-tests: disable NPTL is missing
Date: Mon, 13 Jan 2014 16:10:12 +0800 [thread overview]
Message-ID: <20140113161012.06535faf@skate> (raw)
In-Reply-To: <0255f67e72bc626106163b3cfb821a68d99970fd.1389596187.git.baruch@tkos.co.il>
Dear Baruch Siach,
On Mon, 13 Jan 2014 08:56:27 +0200, Baruch Siach wrote:
> + # priority-inheritance mutex needs NPTL
> + depends on !BR2_PTHREADS && !BR2_PTHREADS_OLD
No, these symbols are specific to the internal toolchain backend, and
do not make sense for external toolchains. Therefore, they shouldn't be
used for package dependencies.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-13 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 6:56 [Buildroot] [PATCH v2] rt-tests: disable NPTL is missing Baruch Siach
2014-01-13 8:10 ` Thomas Petazzoni [this message]
2014-01-13 8:25 ` Baruch Siach
2014-01-13 8:27 ` Peter Korsgaard
2014-01-16 8:25 ` 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=20140113161012.06535faf@skate \
--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