From: Eli Zaretskii <eliz@gnu.org>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org, psmith@gnu.org
Subject: Re: [PATCH] findprog-in: Set errno to indicate why NULL was returned.
Date: Mon, 16 Sep 2019 18:18:11 +0300 [thread overview]
Message-ID: <831rwgxob0.fsf@gnu.org> (raw)
In-Reply-To: <5307069.QXIAngi7cb@omega> (message from Bruno Haible on Sun, 15 Sep 2019 19:58:56 +0200)
> From: Bruno Haible <bruno@clisp.org>
> Cc: Paul Smith <psmith@gnu.org>
> Date: Sun, 15 Sep 2019 19:58:56 +0200
>
> + - Otherwise, it sets errno and returns NULL.
> + Specific errno values include:
> + - ENOENT: means that the program's file was not found.
> + - EACCESS: means that the program's file was found but lacks the
> + execute permissions.
The value of EACCES (not EACCESS!) on MS-Windows frequently means the
file cannot be accessed for a reason that has nothing to do with
execute permissions. It could be, for example, that some intermediate
directory in the full file name doesn't exist or is otherwise
inaccessible.
next prev parent reply other threads:[~2019-09-16 16:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-14 19:35 [PATCH] findprog-in: Set errno to indicate why NULL was returned Paul Smith
2019-09-14 19:38 ` Paul Smith
2019-09-15 17:11 ` new module 'access' Bruno Haible
2019-09-16 15:22 ` Eli Zaretskii
2019-09-16 22:45 ` Bruno Haible
2019-09-17 6:15 ` Eli Zaretskii
2019-09-28 12:06 ` Bruno Haible
2019-09-28 12:17 ` Eli Zaretskii
2019-09-28 13:29 ` Bruno Haible
2019-09-28 13:54 ` Eli Zaretskii
2019-09-15 17:58 ` [PATCH] findprog-in: Set errno to indicate why NULL was returned Bruno Haible
2019-09-16 15:18 ` Eli Zaretskii [this message]
2019-09-28 11:48 ` Bruno Haible
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831rwgxob0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=psmith@gnu.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.
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).