On Tue, 2014-01-14 at 18:02 +0200, Eli Zaretskii wrote: > > =================================================== > > process_begin: CreateProcess(NULL, uname, ...) failed. > > make: > > process_begin: CreateProcess(NULL, uname -a, ...) failed. > > make: > > process_begin: CreateProcess(NULL, cygpath C:\zzz_13.12.1_gener > > make: > > process_begin: CreateProcess(NULL, pwd, ...) failed. > > make: > > process_begin: CreateProcess(NULL, basename "", ...) failed. > > make: > > process_begin: CreateProcess(NULL, pwd, ...) failed. > > make: > > process_begin: CreateProcess(NULL, basename "", ...) failed. > > Do you have uname.exe, cygpath.exe, pwd.exe, and basename.exe > somewhere on your PATH? If not, that's the reason for those failures: > Make looks for these programs, but cannot find them.
Is it possible for the code to understand more about why CreateProcess() failed, and provide a simpler, more informative error message here, especially for common problems such as not being able to locate a program to start? That would be nice... At the very least I don't think it's a good idea to print out internal function names like process_begin() or CreateProcess(), unless this error is really some kind of internal state error that the user should never encounter, regardless of her environment. Also it would be good if these messages looked as much like the other make errors as possible. If this code could use the standard error reporting functions in output.c, that would be ideal (so that if/when we get output sync for Windows, they're managed properly). _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make