|author||Thomas Petazzoni <email@example.com>||2013-03-24 08:19:22 +0000|
|committer||Peter Korsgaard <firstname.lastname@example.org>||2013-03-24 19:39:09 +0100|
rt-tests: mention that NPTL thread implementation is needed
This patch superseds http://patchwork.ozlabs.org/patch/150161/, but does it in a different way. Since we don't have a way of selecting the thread implementation for external toolchains, and it sounds a bit too heavy to add new config options just for the sake of rt-tests, we instead simply add some help text to the rt-tests package explaining that NPTL thread implementation is needed. Signed-off-by: Thomas Petazzoni <email@example.com> Signed-off-by: Peter Korsgaard <firstname.lastname@example.org>
Diffstat (limited to 'package/rt-tests')
1 files changed, 6 insertions, 0 deletions
diff --git a/package/rt-tests/Config.in b/package/rt-tests/Config.in
index 0999ebfbce..a040139579 100644
@@ -14,6 +14,12 @@ config BR2_PACKAGE_RT_TESTS
installed if a Python interpreter has been selected in the
+ Note that this package requires a toolchain built with the
+ NPTL implementation of the pthread API (this is always the
+ case with glibc/eglibc toolchains, but may not necessarily
+ be the case with uClibc toolchains, since the thread
+ implementation is configurable).
comment "rt-tests requires a toolchain with threads support"