-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows builds use an old version of GCC #8598
Comments
I was able to build Rust with GCC 4.7 on Linux Mint 15 x86-64 for the record without having to do anything particular. |
It would be good if we know latest working gcc version. |
yet another w32api issue (4.0.0-1) from irc: #if (_WIN32_WINNT >= _WIN32_WINNT_WIN2K)
...
#if (NTDDK_VERSION >= NTDDI_WIN2KSP2)
#define FILE_FLAG_FIRST_PIPE_INSTANCE 524288
#endif
...
#endif but My old w32api-3.17-2 contains: #if (_WIN32_WINNT >= 0x0500)
#define FILE_FLAG_FIRST_PIPE_INSTANCE 524288
#endif I guess |
@aarondandy documented detailed instruction for gcc 4.8 on wiki. Hooray! |
@klutzy I ran make only. |
We might currently work with gcc 4.8. But we nonetheless must update our bots to test against the appropriate version of gcc on Windows. Accepted for P-high. |
I just attempted to build rust on fresh install of MinGW with GCC 4.8.1.
|
That's expected. On Windows one should build the "check-fast" target, i.e. "make check-fast". |
Rust windows bots have transitioned to mingw-w64, so this is now fixed. |
Rust wiki states that on Windows an old version of GCC must be used because of incompatibility with then-current LLVM. This causes problems for Windows users who run on a fresh mingw installation: #5878, #5712.
There had been several LLVM upgrades since then and apparently the incompatibility issue got fixed somewhere along the way: I was able to build Rust with GCC 4.7.2 on 64-bit Windows machine without apparent problems. Well, I had to copy old libgcc_s_dw2-1.dll and libstdc++-6.dll into stage0\bin to make stage1 compilation work, but other than that everything had worked fine.
The text was updated successfully, but these errors were encountered: