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

login
register
mail settings
Submitter Peter Maydell
Date June 25, 2013, 11:33 a.m.
Message ID <1372160027-31837-3-git-send-email-peter.maydell@linaro.org>
Download mbox | patch
Permalink /patch/254127/
State New
Headers show

Comments

Peter Maydell - June 25, 2013, 11:33 a.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>
---
 configure |    3 ---
 1 file changed, 3 deletions(-)

Patch

diff --git a/configure b/configure
index d363f42..440ba64 100755
--- a/configure
+++ b/configure
@@ -4171,7 +4171,6 @@  case "$target_name" in
   cris)
   ;;
   lm32)
-    target_nptl="no"
   ;;
   m68k)
     bflt="yes"
@@ -4200,7 +4199,6 @@  case "$target_name" in
     target_nptl="no"
   ;;
   moxie)
-    target_nptl="no"
   ;;
   or32)
     TARGET_ARCH=openrisc
@@ -4254,7 +4252,6 @@  case "$target_name" in
   ;;
   xtensa|xtensaeb)
     TARGET_ARCH=xtensa
-    target_nptl="no"
   ;;
   *)
     error_exit "Unsupported target CPU"