[cm3]

Thanks, because the way which snapshots of LLVM and rustc are required to build a certain rustc release does not make it an easy to use solution for common Rust users. It'd be great if an existing LLVM 3.8 can be leveraged.

[steveklabnik]

Note that with 1.10, the way we do rustc snapshots is changing: it will build with 1.9. And then 1.11 will build with 1.10, etc. so that will help a bit.

[cm3]

Hallelujah. This has been a pain point for anyone who tried to build rustc on non-tier1 platforms (musl as host, etc.).

[steveklabnik]

Even on those platforms, it's helpful for distros, who only want one package, not a separate bootstrapping package. I'm real glad we're doing it.

[cm3]

Will we maybe also get official musl-host builds accessible via rustup and automatically fetched on such a platform?

[steveklabnik]

We are always interested in adding more platforms. I don't remember if there are any open issues with a MUSL host; I vaguely remember something about compiler plugins?

[cm3]

I suppose the issues you're referring to are with statically linked against musl executables. I wouldn't expect any such issue with musl just as the host, where you can run rustc on alpine and voidlinux, just not necessarily statically.

[cm3]

Speaking of non-tier1, is there support for static linking libc when building on/for FreeBSD?

[steveklabnik]

I am not sure, but I don't think so right now. I don't know how FreeBSD and MUSL interact.

[cm3]

I mean given that FreeBSD's libc allows full static linking, the same support as for musl-target.