-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Experimental cygwin host support #137819
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
Comments
The tracking issue for |
In addition to cargo, there seems to be at least one other Cargo.toml that needs a version bump: rust/src/tools/rust-analyzer/Cargo.toml Line 119 in 462cc09
|
rust/src/tools/rust-analyzer/Cargo.lock Lines 1126 to 1127 in bf64d66
|
Cool, I was wondering why I wasn't seeing this issue again with the new nightly I got earlier. |
Trying on actual Cygwin instead of MSYS2, I ran into an issue with it trying to use an MSYS2-style path
Some(format!("/proc/cygdrive/{}/{}", drive, &s[drive.len_utf8() + 2..])) which should work on both Cygwin and MSYS2. I don't know what any other Windows ports of sh would expect (WSL would be |
Now
|
it looks like cargo was updated so 2025-06-01 nightly shouldn't need to be patched for that anymore, but as of yesterday's nightly I get a new error trying to bootstrap from x86_64-pc-windows-gnu: |
rust now requires no patching to build on Cygwin. Curl 8.14.1 is fixed for the crashing on thread exit issue, just need Cygwin to package it (shouldn't take too long). |
Uh oh!
There was an error while loading. Please reload this page.
While we do not yet formally support the cygwin target by distributing binaries, that is not because we do not wish for people to be able to build a rustc that uses cygwin as its host if they so please. I am opening this issue so that interested parties can track the progress on enabling a rustc to be built for cygwin. There's a few needed patches:
cc @Berrysoft
The text was updated successfully, but these errors were encountered: