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?

Reply via email to