From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] rt-tests: Make it available only when NPLT is selected
Date: Tue, 03 Apr 2012 23:33:48 +0200 [thread overview]
Message-ID: <87fwckv6tf.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20120402162532.156eed02@skate> (Thomas Petazzoni's message of "Mon, 2 Apr 2012 16:25:32 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> Le Mon, 2 Apr 2012 15:15:54 +0100,
Thomas> Markos Chandras <markos.chandras@imgtec.com> a ?crit :
>> rt-tests package requires some definitions (like PTHREAD_PRIO_INHERIT
>> etc) which are only available in Native Posix Linux Thread
>> implementation.
>>
>> Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
Thomas> I agree there is a problem, but unfortunately this solution will break
Thomas> external toolchains and crosstool-ng toolchains that use glibc or
Thomas> eglibc. Those toolchains have NPTL support, but BR2_PTHREADS_NATIVE is
Thomas> not defined when using such toolchains.
Thomas> I guess the real solution would be something like:
Thomas> config BR2_TOOLCHAIN_HAS_NPTL
Thomas> bool
Thomas> and then for internal backend, select this option is
Thomas> BR2_PTHREADS_NATIVE is enabled. For external backend, select this
Thomas> option when glibc/eglibc is used, and add an option when the uClibc
Thomas> library is used. Some similar solution must be found for the
Thomas> crosstool-NG backend.
Alternatively you can make it depend on !pthreads (ugly because it is so
verbose)
depends on !(BR2_TOOLCHAIN_CTNG_THREADS_NONE ||
BR2_TOOLCHAIN_CTNG_THREADS_PTHREADS ||
BR2_TOOLCHAIN_CTNG_THREADS_PTHREADS_OLD ||
BR2_PTHREADS_NONE || BR2_PTHREADS || BR2_PTHREADS_OLD)
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2012-04-03 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 14:15 [Buildroot] [PATCH] rt-tests: Make it available only when NPLT is selected Markos Chandras
2012-04-02 14:25 ` Thomas Petazzoni
2012-04-03 21:33 ` 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=87fwckv6tf.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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