rustup: rustup-init.sh does not correctly detect host string for Pinebook Pro
Problem
On Pinebook Pro Debian stretch (9.9), rustup-init.sh tries to download rustup-init for aarch64, but that doesn’t work; the CPU is ARMv8. Even once I downloaded an armv7 rustup-init, it guessed the wrong target triple.
Possible Solution(s)
Instead of just checking uname, check the actual ld library; on my machine this is only ld-linux-armhf.so.3 and therefore it is detectable that any aarch64 binaries won’t run.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 16 (10 by maintainers)
Commits related to this issue
- rustup-init.sh: Support detecting 32bit userland on aarch64 This should fix #2111 Signed-off-by: Daniel Silverstone <dsilvers@digital-scurf.org> — committed to kinnison/rustup by kinnison 5 years ago
- rustup-init.sh: Support detecting 32bit userland on aarch64 We duplicate the 'eabihf' suffix code here to ensure that if we select armv7 as a result, we append the ABI suffix if necessary. This shou... — committed to kinnison/rustup by kinnison 5 years ago
- rustup-init.sh: Support detecting 32bit userland on aarch64 We duplicate the 'eabihf' suffix code here to ensure that if we select armv7 as a result, we append the ABI suffix if necessary. This shou... — committed to AJ-Ianozi/getada-download by kinnison 5 years ago
Okay, that’s fascinating. I suppose it might be similar to someone running an
amd64kernel and a 32 bit userland, but without running it under a 32 bit personality. Hmm.Perhaps we could add a check via
getconf LONG_BITwhich should return32for you (if you can confirm?)