From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Philipp Stephani
=Philipp Stephani <p.stephani2@gmail.com&= gt; schrieb am Di., 6. Feb. 2018 um 01:26=C2=A0Uhr:Paul Eggert <= eggert@cs.ucla.edu> schrieb am Di., 6. Feb. 2018 um 00:56=C2=A0Uhr:<= br>On 02/05/2018 11:18 AM, Alan Third = wrote:
>
> Yes, it fixes the problem here.
>
> Is this a known issue with macOS?
It's news to me and it's not listed in the Gnulib portability gotch= a list.
What happens if you run the attached program on macOS? It creates a file
"file" and then tries to access it as a directory, which should n= ot work.
It succeeds and prints nothing (i.e. the error is ENOTDIR= in all cases).So this is even more mysterious than I thought.= =C2=A0However, when I change "file&quo= t; to "/usr/bin/true" in the names list, the issue happens again = (i.e. lstat and faccessat succeed for "/usr/bin/true/."). So this= does appear to be a macOS bug, but it's not consistently reproducible.=