-
Notifications
You must be signed in to change notification settings - Fork 920
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
Rust 1.26.0 fails to install on ARM #1410
Comments
I'm also getting this issue. I've got a dockerfile installing via rustup, and the 1.26.0 release has broken it with this error :) |
Same on Aarch64 here!
Will try to look into it 😄 |
same here, no Rust 1.26 for me :( $ rustup update
info: syncing channel updates for 'stable-armv7-unknown-linux-gnueabihf'
info: latest update on 2018-05-10, rust version 1.26.0 (a77568041 2018-05-07)
error: component 'rust-docs' for 'armv7-unknown-linux-gnueabihf' is unavailable for download
info: checking for self-updates
stable-armv7-unknown-linux-gnueabihf update failed - rustc 1.25.0 (84203cac6 2018-03-25) |
Forget updating, if you don't already have a working toolchain you can't even install Rust:
This is on a Raspberry Pi 2 Model B. |
I'm having the same issue on a Raspberry Pi 3 |
I'm having the same issue on a Raspberry Pi Zero W |
Ditto here... on Raspberry Pi 3B+ |
As a check, this also fails on ARMv6
|
Looks like the nightly build resolves the issues: It's also fixed in |
See rust-lang/rust#49462 – it will apparently be fixed in 1.27, but it's not clear whether there will be a fix for 1.26. |
This just looks like an error from a missing file somewhere, why would this
not be fixed until the next release.
…On Sun, May 13, 2018, 12:40 PM Josh Holland ***@***.***> wrote:
See rust-lang/rust#49462 <rust-lang/rust#49462>
– it will apparently be fixed in 1.27, but it's not clear whether there
will be a fix for 1.26.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1410 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFDC8rcGJAfeO0vz6rc0Y8c7qcIfmj_Xks5tyIxFgaJpZM4T6z7H>
.
|
😞
|
Version 1.25 can be installed with the command: |
That's nice until you try something (like displaying the --version) and you get this: error: no default toolchain configured And then of course, no real way to look this error up as in the past after a successful install Rust just worked. So, how do you configure a default toolchain? |
|
On a new board that doesn't already have rustup, it appears you can install 1.25.0, from scratch, using this:
|
@CodeCutterUK that worked: 1.25.0-armv7-unknown-linux-gnueabihf installed - rustc 1.25.0 (84203cac6 2018-03-25) pi@goldpi:~ $ rustc --version |
Could this be backported to stable. It's really bad UX for new users if the language installer fails. EDIT I'm happy to do this if someone oks it/points me in the right direction. |
First installation is still broken on pi2. fpagliughi's workaround helped to get rustup installed |
Same issue, had to install beta. Please fix it. Edit: I wanted to post a bounty, but since Bountysource disabled Bitcoin, I have to offer it here directly. I offer $15 worth of Bitcoin to anyone who manages to fix this until next week. |
The 1.26.1 release isn't quite out yet, but you can test whether it works for you with |
ok I'll have a go with this :) Update:
So for me(tm) 1.26.1 fixes the issue. |
By the way, the problem @Mark-Simulacrum mentioned above is rust-lang/rust#51097, aka |
That one fixed the problem for me too. |
@Mark-Simulacrum It worked for me, but what exactly did I install? I mean, 1.26.1 is not officially out, yet I've been able to install it, so did I install some RC version, or is the release process in some phase in which the compiler exists but is not announced for some reason? @pietroalbini Thank you for the PR! Once rustup will use it, I'll test it and then I'll ask you to send me your Bitcoin address. |
This is a preview of what is likely to be the actual artifacts for the release on Tuesday. It's intended for this sort of confirmation testing to ensure that the release works as expected (though of course we've already run tests on CI as well). |
Worked for me on an UDOO Neo (i.MX6 SoloX)...
|
Still having issues here on a raspberry pi w upgrading to 1.26.1
|
"Some users will need to run rustup install stable instead of rustup update to make rustup avoid the missing docs component, but this should be a one-time problem." |
Install also did not work for me. I had to first uninstall and then install again and it worked. Thanks @rosenk !
|
In order to clean everything up, I had to delete (rm -rf) ~/.cache and ~/.rustup, then just do a regular install. I have 1.26.1 installed on a Raspberry Pi 3 Model B+ |
Yeah, until a new rustup release is done it's not possible to update to 1.26.1, only to install it from scratch. |
Was this fixed in the meantime? The arm stages (if rust is >=1.26.0) from static.rust-lang.org do not include the components folder rust-doc, hence the install fails if probing 1.25.0 is fine in this regard. |
Once this bug hit I could not update from an existing Rust on a Raspberry Pi. I had to delete ~/.cargo and ~/.rustup and then do a completely new 1.26.1 installation. Once 1.26.1 was installed, I was able to do a Rust update to 1.27.0. (I know I said ~/.cache in an earlier comment, but I was delirious.) |
At the moment, a workaround is to remove and reinstall the toolchain. |
This should be fixed already in 1.12 |
This seems related to #1383, but this time on stable.
The text was updated successfully, but these errors were encountered: