RFC: Update Windows build toolchain and instructions #11705
Conversation
tkelman
added
building
tkelman
force-pushed
the
tk/winbuild
branch
4 times, most recently
from
811fbe8 to
c257a16
Compare
|
[edit by @tkelman] moved to https://gist.github.com/tkelman/b6a4852600d0715f6d63 |
|
Thanks! That was MSYS2, using the script and instructions here? That commit looks like master, rather than this branch. Looks like cross-compiling won't actually work under docker, will try with vagrant instead today. |
|
Oh I think I haven't fully understood your intentions. This was the binary from juliang.org! |
|
At least that confirms #11682 (comment) that the nightlies are working. I moved the comment into a gist to save space. This PR is about updating the recommended toolchain and build instructions. |
|
This line should replace point number 2. I just reinstalled msys2 and opening |
|
Should that replace |
|
That'll teach me to read the raws and not the formatted version! |
|
I just ran the I will retry it and build it tomorrow, can't stay up and resume the failed downloads unfortunately. |
|
The downloads fall back to a mirror so the 404's are probably not fatal, if the fallback fails then the script should terminate with an error. How do the updated msys2 setup steps look? I'll probably try in a clean VM just to make sure it works okay, so far I've been running the cross-compiles. |
|
They look fine now. I can't see anything wrong with a quick read-through. |
and no longer always cd to dist-extras and explicitly check for its own dependencies
Partially fix using the opensuse toolchain from cygwin Only create junction to includes if it does not exist yet
testers needed! Rewrite cross-compiling instructions to use docker and opensuse 13.1 and fix markdown lists Vagrant instead of Docker adjust msys2 setup steps Test with msys2's python2 Remove path recommendation, not really needed any more [av skip]
|
Pretty sure this works now (though vagrant + wine can be flaky for the cross-compiles), let me know if any feedback, will merge soon if I don't get any. We also need to fix the toolchain on release-0.3 before we tag 0.3.10. |
|
Err, I thought this was working. Now msys2 Python (which I was hoping would make the installation simpler) is interacting badly with virtualenv pypa/virtualenv#650 - could have sworn I built the docs successfully at least once. |
tkelman
changed the title
Is the issue that opensuse did a major version bump of libstdc++? |
|
Not even! They did that a month or two ago and it didn't cause that many problems. A couple weeks ago they fixed a typo in a gcc configure flag and that apparently caused ABI breakage. https://build.opensuse.org/package/rdiff/windows:mingw:win64/mingw64-gcc?linkrev=base&rev=73 Oh, the neverending "joys" of C++. |
|
I see, thanks. Fun times: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16612 Linking (your) relevant cygwin mailing list post for future reference: http://comments.gmane.org/gmane.os.cygwin/153535 |
|
Also ref JuliaCI/julia-buildbot#20 (comment) where we're figuring out what to do about the buildbots. |
Hehe... precisely why I'm working so hard to make sure I can use julia for my consulting job... Hell would be going to C++ full time! |
|
C++ standard library ABIs are absolutely horrible. I just lost a week of my life to the fact that std::shared_ptr ABIs differ depending on whether the compiler thinks it has certain atomics, causing subtly memory corruption if not GRRRR. |
separate installers are annoying, but MSYS2 python does not play well with virtualenv [av skip]
|
Last call for comments, I'll merge if no one has any. |
tkelman
changed the title
|
Seems to build fine on my windows machine + cygwin! |
|
I know cygwin works, what's more in need of testing here is the opensuse toolchain + msys2. Cygwin-built Julia won't work with WinRPM packages at the moment. This unfortunately keeps changing. |
|
Is the behaviour that it hangs at "INFO: Extracting packageX" ? |
|
The behavior would more likely be something like |
|
... Is the WinRPM problem supposed to also happen with the prebuild binaries from julialang? using WinRPM
WinRPM.install("gcc")
..
..
..
INFO: Extracting: runtime
#nothing happens anymoreThis goes for all tested versions, which were something between 5-day old master and 0-day old master (juliang binary) and this branch here. |
|
Yes the nightly binaries are built from cygwin so are also broken with WinRPM packages right now. Just checking, you did the usual |
|
yes! also make binary-dist, installed it and copied |
|
And by freshly built you mean from cygwin? I don't know what's wrong with the extraction. I hope an msys2+opensuse toolchain build would run more smoothly, I'll try to test that along with WinRPM on my own machine. |
|
Yes, that's what I meant. |
|
Sorry to @SimonDanisch that what I was wanting help with testing here was unclear. I just did some tests using an MSYS2 + opensuse toolchain build with WinRPM packages and things worked more or less the way I expected them to, so I'll merge this. |
RFC: Update Windows build toolchain and instructions
|
backport moved to #11793 |
[release-0.3] Backport #11705, windows build instructions
Cygwin's mingw-w64 package was rebuilt for --enable-dynamic-string, so now using julia built with cygwin's mingw works again with gcc dlls from opensuse, but we do need opensuse gcc dlls to work with winrpm packages (cherry picked from commit 00242a4)
This uses the opensuse toolchain, to maximize compatibility with WinRPM packages. Ref previous related issues and discussion in #10490 #11285 and #11682.
I haven't gotten this toolchain to fully work in Cygwin yet, since it's a native windows compiler executable and not cygwin-hosted so it doesn't understand Cygwin paths, symlinks, etc. If we're lucky, a future cygwin mingw-w64 package update might restore ABI compatibility with opensuse. We'll need to figure out something to do about the buildbots, which are currently cygwin-based. Maybe we could transition or augment them with MSYS2 and/or opensuse cross-compile.
I'd greatly appreciate people testing this, especially from a clean environment (pristine VM or fresh separate install of msys2, no pre-existing junk on the path, etc) to verify that it works as I'm describing for other people too.
I'll be adding another commit shortly that replaces the cross-compiling section of README.windows.md with a much simpler set of Docker+opensuse instructions.