Junio C Hamano wrote: > How does Cygwin-ness of the build environment affect the end result when > you build with MSVC? Not at all. This is an MSVC/NO_MMAP combo problem. (The "problem" also exists with the msvc build on msysGit[1]) > I am not a Windows person, so I am only guessing, > but I suspect that the result does not pull any library nor crt0 from what > people usually consider "Cygwin environment". It feels that the "default > configuration of Cygwin" that insists on NO_MMAP is the guilty party here. > See patch #3. > Shouldn't this be solved by teaching the Makefile about this new "Cygwin > but using MSVC as compiler toolchain" combination? Yes. Err... see patch #3 :-P > [Footnote] > > *1* Notice "if" at the beginning of this sentence---I am not qualified to > make a judgement without help from area experts here. Is it a sane thing > to run Cygwin and still use MSVC as the compiler toolchain? About as sane as running msysGit and still use MSVC as the compiler! :D > Is it > commonly done? I have no idea. > Nor me. I just tried it, and it works (after applying these patches!); for exactly the same reason, and to the same extent, that it works on msysGit. [Footnote] *1* I admit to sometimes being a bit sloppy with naming (and maybe confused also!). Now, IIUC, MinGW is basically gcc + binutils, MSYS is bash + some unix tools and msysGit is MinGW + MSYS + some additional packages needed to build and run git (eg perl). So, the "MinGW build" should really be called the msysGit build ;-) (but the config section specifically picks out the MINGW string from uname_S) Also, the "msvc build on MinGW" should really be the "msvc build on msysGit". Or something like that! ATB, Ramsay Jones -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html