configure: improve error for ucontext coroutine backend

Instead of using feature_not_found(), which is not a good match because
there is no "remedy" to fix the lack of makecontext(), just print a
custom error.

This happens to remove the last use of feature_not_found(), so remove
the definition and the documentation.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
This commit is contained in:
Paolo Bonzini 2022-08-19 18:40:46 +02:00
parent 45ed68a1a3
commit 7cb5844808
2 changed files with 1 additions and 15 deletions

11
configure vendored
View File

@ -1468,15 +1468,6 @@ if test "$tcg" = "enabled"; then
git_submodules="$git_submodules tests/fp/berkeley-softfloat-3" git_submodules="$git_submodules tests/fp/berkeley-softfloat-3"
fi fi
feature_not_found() {
feature=$1
remedy=$2
error_exit "User requested feature $feature" \
"configure was not able to find it." \
"$remedy"
}
# --- # ---
# big/little endian test # big/little endian test
cat > $TMPC << EOF cat > $TMPC << EOF
@ -1639,7 +1630,7 @@ else
;; ;;
ucontext) ucontext)
if test "$ucontext_works" != "yes"; then if test "$ucontext_works" != "yes"; then
feature_not_found "ucontext" error_exit "'ucontext' backend requested but makecontext not available"
fi fi
;; ;;
sigaltstack) sigaltstack)

View File

@ -99,11 +99,6 @@ developers in checking for system features:
Write a minimal C program main() function to the temporary file Write a minimal C program main() function to the temporary file
indicated by $TMPC indicated by $TMPC
``feature_not_found $NAME $REMEDY``
Print a message to stderr that the feature $NAME was not available
on the system, suggesting the user try $REMEDY to address the
problem.
``error_exit $MESSAGE $MORE...`` ``error_exit $MESSAGE $MORE...``
Print $MESSAGE to stderr, followed by $MORE... and then exit from the Print $MESSAGE to stderr, followed by $MORE... and then exit from the
configure script with non-zero status configure script with non-zero status