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 <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>

diff --git a/package/rt-tests/Config.in b/package/rt-tests/Config.in
index 0999ebfbce0db68a7e20f17238b0395aaec16263..a04013957923b2ff4c7b58eb3d626380ba4b51d1 100644 (file)
--- a/package/rt-tests/Config.in
+++ b/package/rt-tests/Config.in
@@ -14,6 +14,12 @@ config BR2_PACKAGE_RT_TESTS
          installed if a Python interpreter has been selected in the
          Buildroot configuration.
 
+         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).
+
          http://rt.wiki.kernel.org
 
 comment "rt-tests requires a toolchain with threads support"