Rustup: Downloaded rustup-init traps

[nabijaczleweli]

Problem
When running rustup-init.sh, the script downloads rustup-init, then traps on execution

Steps

1. Download the script from http://sh.rustup.rs/ to rustup-init.sh
2. chmod +x rustup-init.sh
3. ./rustup-init.sh

Possible Solution(s)

Notes

The script says it's a "rustup-init 1.19.0 (a1f78334e 2019-09-07)"

The machine in question is a Toshiba Satellite 1200-S121

[kinnison]

That is quite an old laptop (2002 era CPU) and I fear it's possible that Rust expects newer CPU features than that can provide. I'm not sure where there'd be a list of what features Rust compilers expect these days when we target 'i686' but I do know that the binary works on newer CPUs in 32bit mode, so I don't think it's a corrupt binary.

Were you able to run rust binaries before on that system?

[shepmaster]

that Rust expects newer CPU features than that can provide

@nabijaczleweli are you able to run the current version of Firefox on that machine? That might be a good test for whether it's possible to target that CPU at all.

[nabijaczleweli]

I compiled and built a crate on a VM with the same disk image as the laptop, yielding this:

Running firefox/firefox from the "firefox-69.0.tar.bz2" file I obtained after clicking the "Linux 32-bit" link on the download page:

Does that mean that Rust just doesn't support this platform?

[nabijaczleweli]

Also here's the lscpu output for reference:

[kinnison]

I imagine that at least some of our sub-crates might expect SSE2 to be available. Regular expressions might use those instructions; ditto anything to do with SSL. I'm not convinced we could usefully build rustup for such an old CPU; but if you can find a way, I'd be happy to help you with any rustup-specific issues.

[kinnison]

On the basis that this is a limitation of Rust vs. the older CPU in question in this issue, I'm going to close this. If Rust (and our dependencies) gains support for coping with these CPUs in the future, we'll gain support in Rustup automatically.