Windows system image error with libuv 0.11.22 update

[tkelman]

As mentioned here 1aed903#commitcomment-5844801 this latest libuv update is causing trouble, both locally and on AppVeyor. Was initially getting an ERROR: could not open file c:\projects\julia\base during building the system image.

This commit 368a537 resulted in the error message dropping the "could not open file" part, just an empty ERROR: with no message. Here's as much as I could get out of gdb: https://gist.github.com/tkelman/9871004

[tkelman]

Thanks, this fixed it locally. Not on AppVeyor though, something about make[1]: *** [/c/projects/julia/usr/lib/julia/sys0.o] Error 116. No idea what that is, maybe it'll magically start working again in a few days with updated binaries.

[ihnorton]

The latest binaries are on 4e19b59 so should include this (build failed earlier and was only successful after this).

[tkelman]

Hm, I don't know what's up then. If I fall back to building debug then it's at least able to build the system image, but it's hanging in the core unit tests.

Have a theory, testing now. It may be that MSYS1 is broken by the terminal handling changes, and now only MSYS2 and Cygwin work.

[tkelman]

Nope, unrelated to terminal handling or anything Julia-side. Turns out AppVeyor went and installed MinGW by default, which is a nice gesture to cross-platform projects like us, but they installed a version that isn't compatible with the cross-compiled Windows binaries (as I struggled with for a while - the mingw-builds version we recommend for from-scratch MSYS2 builds is not compatible either). I should've paid closer attention to the early part of the logs, my build script is set up not to download MinGW if gcc is already on the path. Removing the incompatible pre-installed one from the path in AppVeyor before running the script did the trick.