build: stop mentioning Slang in two ./configure messages

Nobody ought to be using Slang, so don't give people the wrong
impression by mentioning it (and even mentioning it *first*).
master
Benno Schulenberg 2020-08-23 09:05:47 +02:00
parent 0f8423eb4c
commit 4873cc26f2
1 changed files with 7 additions and 9 deletions

View File

@ -628,18 +628,16 @@ if test "x$enable_utf8" != xno && \
else else
if test "x$enable_utf8" = xyes; then if test "x$enable_utf8" = xyes; then
AC_MSG_ERROR([ AC_MSG_ERROR([
*** UTF-8 support was requested, but insufficient UTF-8 support was *** UTF-8 support was requested, but insufficient support was
*** detected in your curses and/or C libraries. Please verify that *** detected in your curses and/or C libraries. Please verify
*** your Slang was built with UTF-8 support or your curses was built *** that both your curses library and your C library were built
*** with wide-character support, and that your C library was built
*** with wide-character support.]) *** with wide-character support.])
elif test "x$enable_utf8" != xno; then elif test "x$enable_utf8" != xno; then
AC_MSG_WARN([ AC_MSG_WARN([
*** Insufficient UTF-8 support was detected in your curses and/or C *** Insufficient UTF-8 support was detected in your curses
*** libraries. If you want UTF-8 support, please verify that your *** and/or C libraries. If you want UTF-8 support, please
*** Slang was built with UTF-8 support or your curses was built with *** verify that both your curses library and your C library
*** wide-character support, and that your C library was built with *** were built with wide-character support.])
*** wide-character support.])
fi fi
fi fi