!OqhvaDMJdKYUicLDiE:nixos.org

Nixpkgs Stdenv

224 Members
72 Servers

Load older messages


SenderMessageTime
28 Jan 2026
@pyrox:pyrox.devdish [Fox/It/She]but that is coming from my perspective so... grain of salt22:49:04
@whispers:catgirl.cloudwhispers [& it/fae]same, but :/22:49:36
@atemu12:matrix.orgAtemuOne issue that is not clear to me is sustanability22:54:20
@atemu12:matrix.orgAtemuIs the bootstrap compiler still getting updates?22:54:45
@atemu12:matrix.orgAtemuOr does the chain grow indefinitely?22:55:10
@atemu12:matrix.orgAtemuBecause that would not scale well w.r.t. rebuilds22:55:37
@atemu12:matrix.orgAtemuThis is the reason why we don't have rust source bootstrap either22:57:14
@pyrox:pyrox.devdish [Fox/It/She]
In reply to @atemu12:matrix.org
Is the bootstrap compiler still getting updates?
which one? go's bootstrap compiler is gccgo, so whatever that supports is supported by the bootstrap. Currently, with go the bootstrap chain would get 1 version longer per year, as go only increments their version reqs every other minor release, and each release is 6 months apart. Afaik there aren't any plans for them to change that or shrink the chain at a later time, besides gccgo actually getting developed to support later golang features to shrink our bootstrap chain
23:07:56
@pyrox:pyrox.devdish [Fox/It/She]so to answer your question, the bootstrap chain does grow infinitely. The good thing wrt rust is that go is much faster to build, so we don't have to worry about compile times as much, and the chain grows much slower. But it will grow unmanagable at some point, and there's the thorny details of new architectures etc23:09:06
@pyrox:pyrox.devdish [Fox/It/She]the chain in my PR is gccgo -> 1.17 -> 1.20 -> 1.22 -> 1.24/2523:10:32
@pyrox:pyrox.devdish [Fox/It/She]once 1.26 is released, 1.24 becomes part of its bootstrap chain23:10:46
@pyrox:pyrox.devdish [Fox/It/She]* once 1.26 is released, 1.24 becomes part of its bootstrap chain because of how go's bootstrap process works23:13:20
@pyrox:pyrox.devdish [Fox/It/She] https://go.dev/doc/install/source#go14 23:13:44
@pyrox:pyrox.devdish [Fox/It/She] * upstream docs are at https://go.dev/doc/install/source#go14 23:13:53
@atemu12:matrix.orgAtemuThese details should be documented in the PR; this is critical information for deciding on this change!23:15:08
@atemu12:matrix.orgAtemuAlso how long exactly are we talking? If it'd only scale to, like, an hour for the whole bootstrap in the next 10 years (given current velocity), that'd be a very different proposition to it scaling to multiple hours23:17:37
@pyrox:pyrox.devdish [Fox/It/She]checking compile time rn23:18:22
@pyrox:pyrox.devdish [Fox/It/She]uhh23:30:10
@pyrox:pyrox.devdish [Fox/It/She]hmm23:30:11
@pyrox:pyrox.devdish [Fox/It/She]im worried that the minimal-bootstrap PR just broke staging23:30:21
@pyrox:pyrox.devdish [Fox/It/She]28-18-30-34.png
Download 28-18-30-34.png
23:30:51
@whispers:catgirl.cloudwhispers [& it/fae]fwiw, stdenv itself did manage to build fine on x86_64-linux https://hydra.nixos.org/build/32073666223:31:43
@pyrox:pyrox.devdish [Fox/It/She]any ideas why my build is broken23:33:41
@pyrox:pyrox.devdish [Fox/It/She]I just rebased my branch to latest staging, will push to the above PR23:33:57
@whispers:catgirl.cloudwhispers [& it/fae] did a git fetch upstream refs/pull/435345/merge:go-bootstrap && jj new go-bootstrap && nom-build -A go in nixpkgs and gccgo is in the process of configuring just fine for me? 23:39:49
@pyrox:pyrox.devdish [Fox/It/She]okay this does seem to be exclusive to my homelab for... reasons :think23:37:17
@pyrox:pyrox.devdish [Fox/It/She] * okay this does seem to be exclusive to my homelab for... reasons 🤔 23:37:23
@pyrox:pyrox.devdish [Fox/It/She]hmmmmmmm23:41:36
@pyrox:pyrox.devdish [Fox/It/She]very strange, checking my homelab23:41:42
29 Jan 2026
@rosssmyth:matrix.orgrosssmythWrote my thoughts about block on freebsd support in the Go PR00:41:52

Show newer messages


Back to Room ListRoom Version: 9