From: Peter Maydell <[email protected]> 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 <[email protected]> Reviewed-by: Richard Henderson <[email protected]> Signed-off-by: Riku Voipio <[email protected]> --- configure | 3 --- 1 file changed, 3 deletions(-) diff --git a/configure b/configure index 983f4d5..3792607 100755 --- a/configure +++ b/configure @@ -4206,7 +4206,6 @@ case "$target_name" in cris) ;; lm32) - target_nptl="no" ;; m68k) bflt="yes" @@ -4235,7 +4234,6 @@ case "$target_name" in target_nptl="no" ;; moxie) - target_nptl="no" ;; or32) TARGET_ARCH=openrisc @@ -4289,7 +4287,6 @@ case "$target_name" in ;; xtensa|xtensaeb) TARGET_ARCH=xtensa - target_nptl="no" ;; *) error_exit "Unsupported target CPU" -- 1.8.1.2
