configure: better diagnostics if hyper is built wrong

If hyper is indeed present in the specified directory but couldn't be
used to find the correct symbol, then offer a different error message to
better help the user understand the issue.

Suggested-by: Jacob Hoffman-Andrews
Fixes #8001
Closes #8005
This commit is contained in:
Daniel Stenberg 2021-11-13 11:44:34 +01:00
parent b7e1443a1d
commit 9492d3382b
No known key found for this signature in database
GPG Key ID: 5CC908FDB71E12C2

View File

@ -703,7 +703,8 @@ if test X"$want_hyper" != Xno; then
LIBS="$LIB_HYPER $LIBS"
if test "x$cross_compiling" != "xyes"; then
DIR_HYPER=`echo $LD_HYPER | $SED -e 's/^-L//'`
dnl remove -L, separate with colon if more than one
DIR_HYPER=`echo $LD_HYPER | $SED -e 's/^-L//' -e 's/ -L/:/g'`
fi
AC_CHECK_LIB(hyper, hyper_io_new,
@ -721,6 +722,11 @@ if test X"$want_hyper" != Xno; then
AC_MSG_NOTICE([Added $DIR_HYPER to CURL_LIBRARY_PATH]),
)
],
for d in `echo $DIR_HYPER | sed -e 's/:/ /'`; do
if test -f "$d/libhyper.a"; then
AC_MSG_ERROR([hyper was found in $d but was probably built with wrong flags. See docs/HYPER.md.])
fi
done
AC_MSG_ERROR([--with-hyper but hyper was not found. See docs/HYPER.md.])
)
fi