From bcc4039df272c880ea54e82b36089af026270410 Mon Sep 17 00:00:00 2001 From: Michael Heimpold Date: Sun, 7 Mar 2021 10:00:43 +0100 Subject: [PATCH] ext/opcache: fix configure output while checking mmap MAP_ANON support It seems that f3efb9e3fb 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 --- ext/opcache/config.m4 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ext/opcache/config.m4 b/ext/opcache/config.m4 index 93d72fb73d19b..993cee855ceb1 100644 --- a/ext/opcache/config.m4 +++ b/ext/opcache/config.m4 @@ -220,7 +220,7 @@ int main() { ]])],[dnl AC_DEFINE(HAVE_SHM_MMAP_ANON, 1, [Define if you have mmap(MAP_ANON) SHM support]) have_shm_mmap_anon=yes],[have_shm_mmap_anon=no],[have_shm_mmap_anon=no]) - AC_MSG_RESULT([$have_shm_mmap_anon=yes]) + AC_MSG_RESULT([$have_shm_mmap_anon]) PHP_CHECK_FUNC_LIB(shm_open, rt, root) AC_MSG_CHECKING(for mmap() using shm_open() shared memory support)