Patchwork [2/8] configure: Don't say target_nptl="no" if there is no linux-user target

login
register
mail settings
Submitter Peter Maydell
Date July 12, 2013, 8:12 p.m.
Message ID <1373659973-23289-3-git-send-email-peter.maydell@linaro.org>
Download mbox | patch
Permalink /patch/258788/
State New
Headers show

Comments

Peter Maydell - July 12, 2013, 8:12 p.m.
For architectures with no linux-user target, don't claim no NPTL
support. This has no behavioural change, but it means that we
won't accidentally add a new linux-user target without threading
support in future (because attempting to do so would be a compile
failure rather than a silent lack of support).

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Richard Henderson <rth@twiddle.net>
---
 configure |    3 ---
 1 file changed, 3 deletions(-)

Patch

diff --git a/configure b/configure
index ae9519c..c159f34 100755
--- a/configure
+++ b/configure
@@ -4199,7 +4199,6 @@  case "$target_name" in
   cris)
   ;;
   lm32)
-    target_nptl="no"
   ;;
   m68k)
     bflt="yes"
@@ -4228,7 +4227,6 @@  case "$target_name" in
     target_nptl="no"
   ;;
   moxie)
-    target_nptl="no"
   ;;
   or32)
     TARGET_ARCH=openrisc
@@ -4282,7 +4280,6 @@  case "$target_name" in
   ;;
   xtensa|xtensaeb)
     TARGET_ARCH=xtensa
-    target_nptl="no"
   ;;
   *)
     error_exit "Unsupported target CPU"