configure.ac: improve description of NO_REGEX test
The commit 2f8952250a
("regex: add regexec_buf() that can work on a
non NUL-terminated string", 2016-09-21) changed description of
NO_REGEX build config variable to be more neutral, and actually say
that it is about support for REG_STARTEND. Change description in
configure.ac to match.
Change also the test message and variable name to match. The test
just checks that REG_STARTEND is #defined.
Issue-found-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
Signed-off-by: Jakub Narębski <jnareb@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
parent
b7d36ffca0
commit
842a516cb0
13
configure.ac
13
configure.ac
@ -835,9 +835,10 @@ AC_CHECK_TYPE([struct addrinfo],[
|
||||
])
|
||||
GIT_CONF_SUBST([NO_IPV6])
|
||||
#
|
||||
# Define NO_REGEX if you have no or inferior regex support in your C library.
|
||||
AC_CACHE_CHECK([whether the platform regex can handle null bytes],
|
||||
[ac_cv_c_excellent_regex], [
|
||||
# Define NO_REGEX if your C library lacks regex support with REG_STARTEND
|
||||
# feature.
|
||||
AC_CACHE_CHECK([whether the platform regex supports REG_STARTEND],
|
||||
[ac_cv_c_regex_with_reg_startend], [
|
||||
AC_EGREP_CPP(yippeeyeswehaveit,
|
||||
AC_LANG_PROGRAM([AC_INCLUDES_DEFAULT
|
||||
#include <regex.h>
|
||||
@ -846,10 +847,10 @@ AC_EGREP_CPP(yippeeyeswehaveit,
|
||||
yippeeyeswehaveit
|
||||
#endif
|
||||
]),
|
||||
[ac_cv_c_excellent_regex=yes],
|
||||
[ac_cv_c_excellent_regex=no])
|
||||
[ac_cv_c_regex_with_reg_startend=yes],
|
||||
[ac_cv_c_regex_with_reg_startend=no])
|
||||
])
|
||||
if test $ac_cv_c_excellent_regex = yes; then
|
||||
if test $ac_cv_c_regex_with_reg_startend = yes; then
|
||||
NO_REGEX=
|
||||
else
|
||||
NO_REGEX=YesPlease
|
||||
|
Loading…
Reference in New Issue
Block a user