-
Notifications
You must be signed in to change notification settings - Fork 882
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
error: toolchain 'stable-x86_64-pc-windows-msvc' is not installable with rustup 1.27.0 on wine #3807
Comments
Isse seems that the line isn't written in the settings.toml |
BTW I investigated the bug and discovered is related to an issue in the wine-staging ntdll-Junction_Points patchset that implement REPARSE POINTS Bug and a patch to make rustup 1.27.0 (and that also fix an issue with the previous 1.26.0) were made here https://bugs.winehq.org/show_bug.cgi?id=56647 Still, better detection of where an error occurs is welcome |
@llde Wow that's impressive! Thanks a lot for the investigation! Anyway, I'm closing this issue as upstreamed now. |
Verification
Problem
trying a fresh install of rustup and downloading the default stable seems to suceeed, but then error with:
error: toolchain 'stable-x86_64-pc-windows-msvc' is not installable
after the verbose message that follow tmp directory deletions:
verbose: toolchain 'stable-x86_64-pc-windows-msvc' installed
VS2019 and the C++ build tools are isntalled on this prefix.
Using latest Wine from git
While this seems to be a specific wine deficiency (similar to the issue removing tmp directories in the 1.26.0. version), I'd like to know what rustup flow is and what cause the error.
If it's the case that this failing step is working correctyl but expect something that a previous step failed to produce, maybe a warning/error on the previous step may be worth to add
Steps
Correct prefix setted in the WINE_PREFIX envvar
Possible Solution(s)
No response
Notes
No response
Rustup version
1.27.0
Installed toolchains
None
OS version
ArchLinux x64, Wine/Wine Staging 9.8
The text was updated successfully, but these errors were encountered: