From: Philipp Stephani <p.stephani2@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 30350@debbugs.gnu.org, Alan Third <alan@idiocy.org>,
Sam Steingold <sds@podval.org>
Subject: bug#30350: 27.0.50; Newest master can't run processes on macOS
Date: Tue, 06 Feb 2018 00:43:35 +0000 [thread overview]
Message-ID: <CAArVCkThmsB0Z-qdq39QeV=0jS8oPwuBWb5ghWKOevZ-H6QscQ@mail.gmail.com> (raw)
In-Reply-To: <59f3f90b-f19d-71be-6cf9-de8a020db174@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
Paul Eggert <eggert@cs.ucla.edu> schrieb am Di., 6. Feb. 2018 um 01:36 Uhr:
> On 02/05/2018 04:26 PM, Philipp Stephani wrote:
> > It succeeds and prints nothing (i.e. the error is ENOTDIR in all cases).
> > So this is even more mysterious than I thought.
>
> Very strange. I installed the workaround into Emacs master, so at least
> the symptoms should be fixed now. But I don't know why the fix worked,
> and this doesn't inspire warm feelings.
>
> The Gnulib manual says that macOS faccessat (..., "FILE/", ...)
> incorrectly succeeds when FILE is a regular file, and Gnulib has code to
> work around that bug that should be in effect for Emacs. However, the
> Gnulib manual doesn't say that faccessat (..., "FILE/.", ...)
> incorrectly succeeds in this situation, nor that faccessat (...,
> "FILE/./", ...) does the right thing; and the test program I gave you
> didn't illustrate any bugs in this area so I'm not sure what's going on.
>
Maybe that bug was once present, and has been fixed since then?
I've noticed that REPLACE_FACCESSAT is 1, so configure thinks that
faccessat is broken. Apparently faccessat.m4 checks for the behavior of
lstat, not faccessat.
[-- Attachment #2: Type: text/html, Size: 1558 bytes --]
next prev parent reply other threads:[~2018-02-06 0:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 20:15 bug#30350: 27.0.50; Newest master can't run processes on macOS Philipp
2018-02-04 20:20 ` Philipp Stephani
2018-02-04 21:06 ` Alan Third
2018-02-04 21:12 ` Alan Third
2018-02-04 21:28 ` Philipp Stephani
2018-02-04 22:49 ` Alan Third
2018-02-04 23:16 ` Philipp Stephani
2018-02-10 10:47 ` Eli Zaretskii
2018-02-04 20:24 ` Eli Zaretskii
2018-02-05 19:13 ` Paul Eggert
2018-02-05 19:18 ` Alan Third
2018-02-05 23:56 ` Paul Eggert
2018-02-06 0:26 ` Philipp Stephani
2018-02-06 0:36 ` Paul Eggert
2018-02-06 0:43 ` Philipp Stephani [this message]
2018-02-06 23:38 ` Paul Eggert
2018-02-06 8:28 ` Alan Third
2018-02-06 22:07 ` Philipp Stephani
2018-02-06 22:10 ` Philipp Stephani
2018-02-11 15:56 ` Philipp Stephani
2018-02-06 22:44 ` Alan Third
2018-02-06 22:53 ` Noam Postavsky
2018-02-11 16:01 ` Philipp Stephani
2018-02-11 21:15 ` Alan Third
2020-08-16 16:53 ` Lars Ingebrigtsen
2020-10-02 4:54 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAArVCkThmsB0Z-qdq39QeV=0jS8oPwuBWb5ghWKOevZ-H6QscQ@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=30350@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=eggert@cs.ucla.edu \
--cc=sds@podval.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).