[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Never call gl_FUNC_GETCWD_PATH_MAX on Darwin
From: |
Bruno Haible |
Subject: |
Re: [PATCH] Never call gl_FUNC_GETCWD_PATH_MAX on Darwin |
Date: |
Fri, 09 Sep 2022 00:19:02 +0200 |
Kirill A. Korinsky wrote:
> This bug never appears on macOS and it is safe to ignore it,
> specially when the test itself may cause another bug.
>
> See: https://trac.macports.org/ticket/62994
> ---
> m4/getcwd.m4 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/m4/getcwd.m4 b/m4/getcwd.m4
> index 076ca3148..06edd681e 100644
> --- a/m4/getcwd.m4
> +++ b/m4/getcwd.m4
> @@ -114,7 +114,7 @@ AC_DEFUN([gl_FUNC_GETCWD],
>
> gl_abort_bug=no
> case "$host_os" in
> - mingw*)
> + darwin* | mingw*)
> gl_cv_func_getcwd_path_max=yes
> ;;
> *)
I don't think this patch is in line with the findings from the thread in
January 2022, whose last mails were [1] and [2].
IMO, the investigations ought to continue along that thread.
Bruno
[1] https://lists.gnu.org/archive/html/bug-gnulib/2022-01/msg00088.html
[2] https://lists.gnu.org/archive/html/bug-gnulib/2022-01/msg00089.html