3 ms·

> Well, hosted is trickier due to compiler plugins, but yes. This has been discussed multiple times in tickets and it's pending. Hopefully soon :). > please s

> Well, hosted is trickier due to compiler plugins, but yes. This has been discussed multiple times in tickets and it's pending. Hopefully soon :). > please submit bugs upstream or comment on any open issues Of course but there's nothing I can add to already existing and open issues that hasn't already been discussed. There's a need for rustc dev focus on this just like msvc support in the past. > Once you get rustc, rustup should be fine. What do you mean? Being able to build rustup doesn't give you access to rustup toolchains/targets that run on Alpine, if that's what you mean. Or?

steveklabnik 10y ago
I meant that in most distros (I know more about Debian than Alpine), the first step is packaging rustc + cargo, then applications built with it. So I imagined it'd go the same way. rustc and cargo are much harder to package, so after that's done, other applications in Rust tend to be easier.
- throwaway161220 10y ago
  For bootstrapping it in and for a distro that's the right thing, but if we want to have access to the rustup toolchains and targets, then those require musl-hosting support upstream in order for rustup binaries to be made available which, like on Windows or FreeBSD, are downloaded and used by rustup. Building rust right now takes enough time that it's hard to recommend a hypothetical from-source mode for rustup that works similar to OCaml's `opam switch compiler-vsn`. If building rustc becomes similarly fast, this can be a good alternative. And in that case having a rustc version in the distro is very useful, as long as it's not older than two releases.
  - steveklabnik 10y ago
    Right. But std with musl is already available from the project; this is mostly about rustc.
    - throwaway161220 10y ago
      That's for targeting musl, typically used for static linking. That should work when running rustup and rustc on FreeBSD as well. What we're missing is rustc-on-musl and with that rustup-on-musl.
    - mitchty 10y ago
      Since I follow alpine linux dev a bit, I thought this: https://github.com/alpinelinux/aports/blob/master/testing/rust/APKBUILD https://github.com/alpinelinux/aports/blob/master/testing/ru... Is the port of rustc to run natively on AL? Bit outdated now but it seemed to work the last time I tried it. You'd have to enable the testing repo to use it however.
      - steveklabnik 10y ago
        Yes, throwaway (in my understanding) seems to want this from the project itself, not the distro.
        throwaway161220 10y ago
        Is there another way to get access to the continuously updated toolchains and targets available via rustup?
        steveklabnik 10y ago
        Well, if you had a "built-with-musl" rustup, then you could just use it. But if not, you can curl the s3 bucket and grab them; rustup is ultimately a convenience, not a requirement. I guess that's why I see it as "mostly about rustc", since once you have that, you can compile rustup, and once you can do that, you can get it easily. Just to be clear: I would like to see better support for all of this, personally. I'm not trying to argue that things are perfect today, just figure out exactly where in the process of getting there all this is, since I use Debian, not Alpine.
        10y ago

steveklabnik 10y ago

I meant that in most distros (I know more about Debian than Alpine), the first step is packaging rustc + cargo, then applications built with it. So I imagined it'd go the same way. rustc and cargo are much harder to package, so after that's done, other applications in Rust tend to be easier.

throwaway161220 10y ago
For bootstrapping it in and for a distro that's the right thing, but if we want to have access to the rustup toolchains and targets, then those require musl-hosting support upstream in order for rustup binaries to be made available which, like on Windows or FreeBSD, are downloaded and used by rustup. Building rust right now takes enough time that it's hard to recommend a hypothetical from-source mode for rustup that works similar to OCaml's `opam switch compiler-vsn`. If building rustc becomes similarly fast, this can be a good alternative. And in that case having a rustc version in the distro is very useful, as long as it's not older than two releases.
- steveklabnik 10y ago
  Right. But std with musl is already available from the project; this is mostly about rustc.
  - throwaway161220 10y ago
    That's for targeting musl, typically used for static linking. That should work when running rustup and rustc on FreeBSD as well. What we're missing is rustc-on-musl and with that rustup-on-musl.
  - mitchty 10y ago
    Since I follow alpine linux dev a bit, I thought this: https://github.com/alpinelinux/aports/blob/master/testing/rust/APKBUILD https://github.com/alpinelinux/aports/blob/master/testing/ru... Is the port of rustc to run natively on AL? Bit outdated now but it seemed to work the last time I tried it. You'd have to enable the testing repo to use it however.
    - steveklabnik 10y ago
      Yes, throwaway (in my understanding) seems to want this from the project itself, not the distro.
      - throwaway161220 10y ago
        Is there another way to get access to the continuously updated toolchains and targets available via rustup?
        steveklabnik 10y ago
        Well, if you had a "built-with-musl" rustup, then you could just use it. But if not, you can curl the s3 bucket and grab them; rustup is ultimately a convenience, not a requirement. I guess that's why I see it as "mostly about rustc", since once you have that, you can compile rustup, and once you can do that, you can get it easily. Just to be clear: I would like to see better support for all of this, personally. I'm not trying to argue that things are perfect today, just figure out exactly where in the process of getting there all this is, since I use Debian, not Alpine.
        10y ago