You should now be able to use rustup or multirust to install the nightly version of rustc and

cargo on these hosts:

arm-unknown-linux-gnueabi : 32-bit ARMv6/ARMv7 without FPU

: 32-bit ARMv6/ARMv7 without FPU arm-unknown-linux-gnueabihf : 32-bit ARMv6/ARMv7 with FPU

: 32-bit ARMv6/ARMv7 with FPU armv7-unknown-linux-gnueabihf : 32-bit ARMv7 with FPU

: 32-bit ARMv7 with FPU aarch64-unknown-linux-gnu : 64-bit ARMv8

: 64-bit ARMv8 x86_64-unknown-freebsd

x86_64-unknown-netbsd

Some comments:

I have only tested the arm-gnueabihf and armv7-gnueabihf triples. Do let us know if you have any

problem using these binary releases or with rustup/multirust on these platforms by opening an issue

in the respective repository.

rustup installs the arm-unknown-linux-gnueabihf toolchain instead of the armv7 one on ARMv7

devices because of a limitation in the auto-detection mechanism. You can install the armv7 toolchain

using the command rustup default nightly-armv7-unknown-linux-gnueabihf . And you definitely want

the armv7 toolchain because is faster ( cargo build ing hyper takes half the time) than the arm

toolchain. multirust doesn’t have this problem.

Bonus: OpenWRT

You can also use multirust/rustup to install cross compiled std crates for these targets:

mips-unknown-linux-musl

mipsel-unknown-linux-musl

These std crates plus the OpenWRT SDK can be used to cross compile Rust apps for OpenWRT

(trunk edition) devices. For an example of how to do this check the Travis CI configuration of

the rust-cross repository.

Final note

All these targets are tier 2/3 platforms so either (a) we don’t run the full test suite on

these targets (like ARM Linux) or (b) we run the test suite but don’t block PRs on the success of

running the test suite on these targets (like FreeBSD). This means that you may find bugs than we

are not aware of; if you do please report them on the rust-lang/rust issue tracker!

Oh, and if you want to thank someone. Thank @alexcrichton, he has done all the hard work here.

