At the end of a long email thread about users having problems building on newly set up Windows systems, we have:


Alright. I think I found it. The tip about installing VS with all the tools helped and might be the root cause of all this.

When I look at the PATH in "VS 32bit Command prompt" and "spec.gmk" file it is set to:

  export PATH:=/cygdrive/c/BullseyeCoverage/bin:/cygdrive/c/Program Files (x86)/Microsoft F#/v4.0:/cygdrive/c/Program Files (x86)/Microsoft Visual Studio 10.0/VSTSDB/Deploy:/cygdrive/c/Program Files (x86)/Microsoft Visual Studio 10.0/Common7/IDE:/cygdrive/c/Program Files (x86)/Microsoft Visual Studio 10.0/VC/BIN:/cygdrive..........

The highlighted part of the PATH is what is causing the PATH to be corrupted (maybe due to '#'? in the path) and no tools (mkdir, echo, mktemp ..) are found. For the work around if I remove this part from my "spec.gmk" file everything work like a charm.