Skip to content

Commit eaf9421

Browse files
mheinikic
authored andcommitted
ext/opcache: fix configure output while checking mmap MAP_ANON support
It seems that f3efb9e introduced a "typo" which may result in the following confusing message: checking for mmap() using MAP_ANON shared memory support... no=yes Let's fix this. Signed-off-by: Michael Heimpold <mhei@heimpold.de> Closes GH-6758.
1 parent 3b377b5 commit eaf9421

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

ext/opcache/config.m4

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -220,7 +220,7 @@ int main() {
220220
]])],[dnl
221221
AC_DEFINE(HAVE_SHM_MMAP_ANON, 1, [Define if you have mmap(MAP_ANON) SHM support])
222222
have_shm_mmap_anon=yes],[have_shm_mmap_anon=no],[have_shm_mmap_anon=no])
223-
AC_MSG_RESULT([$have_shm_mmap_anon=yes])
223+
AC_MSG_RESULT([$have_shm_mmap_anon])
224224

225225
PHP_CHECK_FUNC_LIB(shm_open, rt, root)
226226
AC_MSG_CHECKING(for mmap() using shm_open() shared memory support)

0 commit comments

Comments
 (0)