Oops, I withdraw 0003. (I had misunderstood what AC_FUNC_MMAP does.) Please use this one instead.
>From f3f0bc607012a8f30a674000b570ef85433ecc74 Mon Sep 17 00:00:00 2001 From: Bruno Haible <[email protected]> Date: Fri, 31 Jul 2020 13:26:04 +0200 Subject: [PATCH 3/3] doc: Update some more macro descriptions. * doc/autoconf.texi (Particular Functions): Add a remark about AC_FUNC_MMAP. Clarify AC_FUNC_STRCOLL. --- doc/autoconf.texi | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 79ecc9d..2a279ef 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -5393,6 +5393,10 @@ memory. The result of this macro is cached in the @code{ac_cv_func_mmap_fixed_mapped} variable. + +Note: This macro asks for more than what an average program needs from +@code{mmap}. In particular, the use of @code{MAP_FIXED} fails on +HP-UX 11, whereas @code{mmap} otherwise works fine on this platform. @end defmac @defmac AC_FUNC_OBSTACK @@ -5509,7 +5513,8 @@ New programs need not use these macros. If the @code{strcoll} function exists and works correctly, define @code{HAVE_STRCOLL}. This does a bit more than @samp{AC_CHECK_FUNCS(strcoll)}, because some systems have incorrect -definitions of @code{strcoll} that should not be used. +definitions of @code{strcoll} that should not be used. But it does +not check against a known bug of this function on Solaris 10. The result of this macro is cached in the @code{ac_cv_func_strcoll_works} variable. -- 2.7.4
