|
From: | Paul Eggert |
Subject: | Re: [PATCH] fchmodat, lchmod: port to buggy Linux filesystems |
Date: | Sun, 23 Feb 2020 15:56:25 -0800 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 |
On 2/23/20 2:58 AM, Bruno Haible wrote:
the file doc/glibc-functions/lchmod.texi still says ... This function always fails with @code{errno} set to @code{ENOSYS}, even when the file is not a symbolic link: GNU/Linux with glibc 2.31. Overriding the system's lchmod function requires the case REPLACE_LCHMOD=1.
Hmm, why? 'configure' says that GNU/Linux functions that always fail with errno==ENOSYS do not exist, i.e., 'configure' sets HAVE_LCHMOD=0 on GNU/Linux. This convention is used often by Autoconf and Gnulib. And if HAVE_LCHMOD=0 why would we want REPLACE_LCHMOD=1?
[Prev in Thread] | Current Thread | [Next in Thread] |