2 ms·
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
by cm3 10y ago
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 10y agoNote 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 10y agoHallelujah. This has been a pain point for anyone who tried to build rustc on non-tier1 platforms (musl as host, etc.).
- steveklabnik 10y agoEven 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 10y agoWill we maybe also get official musl-host builds accessible via rustup and automatically fetched on such a platform?
- steveklabnik 10y agoWe 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 10y agoI 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.
- steveklabnik 10y agorustc itself loads stuff as a shared library, in my understanding.
- cm3 10y agoSpeaking of non-tier1, is there support for static linking libc when building on/for FreeBSD?
- steveklabnik 10y agoI am not sure, but I don't think so right now. I don't know how FreeBSD and MUSL interact.
- cm3 10y agoI mean given that FreeBSD's libc allows full static linking, the same support as for musl-target.
- steveklabnik 10y agoI assume so, I was just trying to say that I am ignorant about BSDs in general, and don't know what the status of any of it is personally.