Re: win32 compilation of make 4. 0 source code‏

[Mark Brown]

I showed some of the output when this new windows/dos make is run
from the command prompt, in the original message.
Why not just post a step by step description of how to compile
make  in Windows 7 64, post some output of its operation,
and clear everything up ?
Also, can you describe what the series of failed process_begin's indicates ?
Are they emanating from inside the make code or from executables invoked by 
make ?

===================================================
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.
make:
'.' is not recognized as an internal or external command,
operable program or batch file.
...
=====================================================

-----Original Message----- 
From: Eli Zaretskii
Sent: Monday, January 13, 2014 8:51 PM
To: Mark Brown
Cc: address@hidden ; address@hidden
Subject: Re: Re: win32 compilation of make 4.0 source code‏

> From: "Mark Brown" <address@hidden>
> Cc: <address@hidden>
> Date: Mon, 13 Jan 2014 14:06:16 -0800
>
> As mentioned I used Visual C++ 2005,
> loading the project file and building it:
> make_msvc_net2003.vcproj .
>
> This results in a make_msvc.net2003.exe   of length   892 KB
> being created in the debug directory.

Does this binary work if you invoke it from the cmd.exe prompt?  But
please make sure your Makefile invokes programs that are on Path, and
try to avoid invoking Cygwin programs as much as possible.  Also, I
would suggest to remove Cygwin's sh.exe from Path, as Make on Windows
always prefers to use a Unix shell if available.

If Make doesn't work even under these circumstances, then something is
broken.  Otherwise, you could be experiencing some incompatibility
between Cygwin and native Windows programs.