3 ms·
My knowledge was apparently outdated! So, the bug I was thinking of was https://github.com/rust-lang/rust/issues/28667 https://github.com/rust-lang/rust/issues/
by steveklabnik 11y ago
My knowledge was apparently outdated! So, the bug I was thinking of was https://github.com/rust-lang/rust/issues/28667 https://github.com/rust-lang/rust/issues/28667 , which has apparently since been closed. The Alpine tracker also links to this bug: https://bugs.alpinelinux.org/issues/3949 https://bugs.alpinelinux.org/issues/3949
And in fact, https://doc.rust-lang.org/book/advanced-linking.html#linux https://doc.rust-lang.org/book/advanced-linking.html#linux has some instructions for building your own rustc in this way.
I am not sure why we don't currently distribute them today, though... I will ask around.
EDIT: Alex says:
we don't have an issue for it
specifically, no, but I think all alpine users were
trying to use the llvm on the system
b/c we don't work well with building an llvm against
musl right now
So, yeah, some small things to work out with regards to Alpine.
- cm3 11y agoI've done that once but since building rustc requires a specific nightly I'd need a glibc environment each time I want to build rustc. Replacing the glibc builds with a musl static build (not targeting but built with musl statically and no glibc requirement) would give us a single binary that works on Alpine and Ubuntu. If that's not an option I'd welcome a musl variant that's automatically installed by rustup when on Alpine or VoidLinux musl edition or any other musl linux environment.