Re: [PATCH] findprog: Support searching in a specified path string

Hi Paul, > note that > on Windows, which is the only place this matters, so far, IIRC it is > illegal to use "prog.exe.exe" so if an extension is already provided > the system won't search again Indeed, the native Windows execlp() function behaves like this: - If the caller specifies "prog.exe

make autoconf tests work with -Werror=implicit-function-declaration

There are indications that future GCC versions may be stricter regarding invocations of undeclared functions. [1] Configuring with CC="gcc -Werror=implicit-function-declaration" is a way to exercise similar functionality with released GCCs. So, what I did is 1. create a testdir of all of gnuli

[PATCH] findprog-in: Set errno to indicate why NULL was returned.

Set errno to either ENOENT if the program was not found, or another error if a program was found but was no suitable (i.e., EACCES). * modules/findprog: Depend on errno. * lib/findprog-in.c (find_in_given_path): Save errno if it is not ENOENT and reset errno before returning NULL. * lib/findprog.h

Re: [PATCH] findprog-in: Set errno to indicate why NULL was returned.

On Sat, 2019-09-14 at 15:35 -0400, Paul Smith wrote: > Set errno to either ENOENT if the program was not found, or another > error if a program was found but was no suitable (i.e., EACCES). Without this change it's impossible for a program to show the correct error message when the program is foun