-
Notifications
You must be signed in to change notification settings - Fork 952
Can't install component 'i686-pc-windows-gnu' on linux #1127
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
Looking into it this seems to be an issue with rust-installer. https://github.com/rust-lang/rust-installer/blob/daa2a05ebe7b8d07a309e8891ebc548652362954/src/generator.rs#L111-L129 I'm not sure which side should be fixed however As a workaround something like this would work but i'm not sure if there is a better way? diff --git a/src/rustup-dist/src/component/package.rs b/src/rustup-dist/src/component/package.rs
index e03b8d2..b6296bf 100644
--- a/src/rustup-dist/src/component/package.rs
+++ b/src/rustup-dist/src/component/package.rs
@@ -94,7 +94,7 @@ impl Package for DirectoryPackage {
let part = try!(ComponentPart::decode(l)
.ok_or_else(|| ErrorKind::CorruptComponent(name.to_owned())));
- let path = part.1;
+ let path: PathBuf = part.1.to_string_lossy().replace('\\', "/").into();
let src_path = root.join(&path);
match &*part.0 { |
I reproduced this, but it only happens on nightly. Something must have changed in how the components are built and packaged, which makes this an upstream issue. |
Reported as rust-lang/rust-installer#65 |
If you really need to install this target (x86_64-pc-windows in this case) until this issue resolved, you can find downloaded tarball in |
The manifests should be fixed already by rust-lang/rust#42132. |
Yep, fixed here for me |
From the looks of the error is seems Windows style paths seem to be being used instead of linux style
The text was updated successfully, but these errors were encountered: