4 ms·
Off-topic, but since you're here, let me ask: where can I track the progress on rustup support for musl-based distros where musl is the host (void linux, alpine
by cm3 10y ago
Off-topic, but since you're here, let me ask: where can I track the progress on rustup support for musl-based distros where musl is the host (void linux, alpine linux) and FreeBSD? I got everything but Rust working nicely on void linux, and it's the only thing holding me back right now. Since Docker defaults to alpine linux, the reach of such support will be wider than one might initially think.
- steveklabnik 10y agoFor void: https://github.com/voidlinux/void-packages/issues/4570 https://github.com/voidlinux/void-packages/issues/4570 And alpine: http://pkgs.alpinelinux.org/packages?name=rust*&branch=&repo=&arch=&maintainer= http://pkgs.alpinelinux.org/packages?name=rust*&branch=&repo... https://github.com/rust-lang/rust/issues/31322#issuecomment-247818983 https://github.com/rust-lang/rust/issues/31322#issuecomment-... is the latest news on the subject. It's not impossible, but we're not sure _how_ we want to make it easy. The real issue is the bootstrapping, my understanding is that cross-compiling a musl compiler from a gnu compiler does work today, which is how those packages were made.
- cm3 10y agoThanks for the pointers. Yeah, after you've bootstrapped once, you have a version to bootstrap another, especially since the new requirements to not depend on a nightly snapshot. rustup should be able to provide images that way which work on both alpine and void. The default would be a dynamically linked against musl rustup image which may still expose musl-static as a target just like it does on glibc hosts. I wouldn't complicate matters as a first step with questions of whether a musl image should be statically linked.
- FreeFull 10y agoI tried rustup.rs on PacBSD, and everything just worked, so presumably it'll just work on FreeBSD too.