1.8 prerelease testing


It’s that time again. 1.8 comes out Thursday.

This release is the first where i686-pc-windows-msvc is a tier 1 platform, and also the first to support installation of multiple targets. There are 31 binary targets distributed with this release, including classics like arm-linux-androideabi and armv7-unknown-linux-gnueabihf.

So there are a great number of configurations to install Rust in these days, and frankly we get very little testing of the end-to-end installation experience. Please give your favorite combination a quick smoke test and report back.

The binaries are here.

Test rustup.sh like:

curl -sSf https://static.rust-lang.org/rustup.sh | RUSTUP_DIST_SERVER=https://static.rust-lang.org/dist/staging sh

Test multirust.sh like:

RUSTUP_DIST_SERVER=https://static.rust-lang.org/dist/staging multirust update stable

Test rustup.rs like:

RUSTUP_DIST_ROOT=https://static.rust-lang.org/dist/staging/dist rustup update stable

As this is the first stable release to support component-based installation, you can further do things like install the Android target:

RUSTUP_DIST_ROOT=https://static.rust-lang.org/dist/staging/dist rustup target add arm-linux-androideabi

Furthermore, you can also install by exact version number:

RUSTUP_DIST_ROOT=https://static.rust-lang.org/dist/staging/dist rustup update 1.8.0


@alexcrichton just discovered that the multirust/rustup UI lists some targets that aren’t actually available, like netbsd. If you try to install them you will get an error.


As simple smoke test of i686/x86_64 targets on Linux, OSX, and Windows all works just fine (yay!)

Only snag I ran into was I couldn’t simultaneously install the arm-unknown-linux-gnueabi and arm-unknown-linux-gnueabihf targets via rustup. This I believe is due to rust-lang/rust#31101 which should be fixed for the next beta release.