zlacker

[return to "Rust in the NetBSD Kernel, and other odd decisions"]
1. nextac+kw[view] [source] 2026-02-03 08:11:41
>>jaypat+(OP)
> In general, the bootstrap relies on a binary package of the previous version. This is unacceptable for an otherwise source-only, self-contained distribution like the NetBSD sources.

This does not paint the full picture. Rust can be bootstrapped with mrustc, which is written in C++

https://github.com/thepowersgang/mrustc

Now, mrustc supports only Rust 1.74. To build Rust 1.92, you need almost 20 builds. But this can be done from source

Guix has written about bootstrapping Rust from source (they care a lot about this). Here is how it looked like in 2018

https://guix.gnu.org/nb-NO/blog/2018/bootstrapping-rust/

◧◩
2. stocke+dy[view] [source] 2026-02-03 08:27:40
>>nextac+kw
And this is good because? Seriously, modern devs have lost their minds if they think that this state of affairs is okay.
◧◩◪
3. anthk+fR[view] [source] 2026-02-03 10:56:43
>>stocke+dy
Go need a smaller chainloading process from C/C++ too. But the good thing it's there are prebuilt self-contained binary ports from every OS to almost any OS so you can bootstrap it with very little.
◧◩◪◨
4. Borg3+R71[view] [source] 2026-02-03 12:50:23
>>anthk+fR
O really? Please.. can I bootstrap it here?

CYGWIN_NT-5.2 1.3.22(0.78/3/2)

◧◩◪◨⬒
5. LeFant+Nd4[view] [source] 2026-02-04 06:37:21
>>Borg3+R71
https://github.com/felixmaker/thunk
[go to top]