!OqhvaDMJdKYUicLDiE:nixos.org

Nixpkgs Stdenv

256 Members
80 Servers

Load older messages


SenderMessageTime
6 May 2026
@pyrox:pyrox.devdish [Fox/It/She] one thing is that since you've removed isl from gcc, you should also remove the fetch for it as well from each file 17:27:45
@pyrox:pyrox.devdish [Fox/It/She]also, breaking the changes up into smaller commits targeted at a few changes per package at a time would make it easier to review and keep track of in git history17:28:34
@siraben:matrix.orgsirabenthanks, amending17:33:28
@siraben:matrix.orgsirabendone17:42:38
7 May 2026
@siraben:matrix.orgsirabenhttps://github.com/NixOS/nixpkgs/pull/517368 another review on bootstrap configure flag prune would be appreciated, one approval already15:39:54
@siraben:matrix.orgsirabengetting mrustc bootstrap working15:59:15
@winter:catgirl.cloudWinter i thought we agreed that we don’t want to do mrustc? there was some reason nobody has done it till now… maybe Alyssa Ross remembers 16:01:10
@whispers:catgirl.cloudwhispers [& it/fae] @emily has expressed concerns (that i agree with) about mrustc's concerns to keep up with rustc and LLVM 16:02:29
@k900:0upti.meK900I think the problem that keeps coming up is the insanely long bootstrap chain16:03:11
@whispers:catgirl.cloudwhispers [& it/fae] but we do have a broken = true; mrustc-boostrap package that just builds one rustc version (and iirc there's an open pr to update that to mrustc v0.12.0 / rustc 1.90.0) 16:03:14
@whispers:catgirl.cloudwhispers [& it/fae]and yeah the bootstrap chain prior to the latest release was some 19 rustc versions + 5 llvm versions, which is a pain in the ass to build (especially on staging)16:03:42
@whispers:catgirl.cloudwhispers [& it/fae]* and yeah the bootstrap chain prior to the latest mrustc release was some 19 rustc versions + 5 llvm versions, which is a pain in the ass to build (especially on staging)16:04:02
@whispers:catgirl.cloudwhispers [& it/fae] and as a small (one maintainer) project, it keeping up is a really rough story and that chain length grows real quicky 16:04:34
@whispers:catgirl.cloudwhispers [& it/fae]* and yeah the bootstrap chain prior to the latest mrustc release was some 19 rustc versions + 5 llvm versions (including one we had dropped from nixpkgs entirely at that point), which is a pain in the ass to build (especially on staging)16:04:48
@whispers:catgirl.cloudwhispers [& it/fae]* and yeah the bootstrap chain prior to the latest mrustc release was some 19 rustc versions + 5 llvm versions (including one we had dropped from nixpkgs entirely at that point), which is a pain in the ass to build and maintain dependencies for16:04:58
@whispers:catgirl.cloudwhispers [& it/fae]* and yeah the bootstrap chain prior to the latest mrustc release was some 19 rustc versions + 5 llvm versions (including llvm 17, which we had dropped from nixpkgs entirely at that point), which is a pain in the ass to build and maintain dependencies for16:05:29
@siraben:matrix.orgsirabeni already got rustc 1.91.0 bootstrapped from stage016:10:31
@siraben:matrix.orgsirabengoing through 1.92 to 1.9516:10:39
@k900:0upti.meK900 It's not that it's hard to do 16:11:15
@k900:0upti.meK900The problem is that it basically slows down the critical path on Hydra by like, days16:11:24
@whispers:catgirl.cloudwhispers [& it/fae] yeah, i did it out of tree a few versions ago and build times were rough. the numbers i had were:
  1. reference for build perf on my laptop: nom-build -A rustc-unwrapped --check on nixpkgs master: 1h52m17s

  2. mrustc: 5m2s

  3. rust-1900: 1h54m18s (you can probably cut this one down but i didn't bother at the time)

  4. rust-1911: 17m33s

  5. rust-1920: 18m53s

  6. rust-1931: 18m1s

  7. rustc-1940: 1h48m52s (literally just pkgs.rustc-unwrapped.overrideAttrsed)

16:13:32
@qyliss:fairydust.spaceAlyssa RossI would love to do mrustc16:13:39
@whispers:catgirl.cloudwhispers [& it/fae] yeah, i did it out of tree a few versions ago and build times were rough. the numbers i had were:
  1. reference for build perf on my laptop: nom-build -A rustc-unwrapped --check on nixpkgs master: 1h52m17s

  2. mrustc: 5m2s

  3. rust-1900: 1h54m18s (you can probably cut this one down but i didn't bother at the time)

  4. rust-1911: 17m33s

  5. rust-1920: 18m53s

  6. rust-1931: 18m1s

  7. rustc-1940: 1h48m52s (literally just pkgs.rustc-unwrapped.overrideAttrsed)

and that's uh. really rough
16:13:44
@whispers:catgirl.cloudwhispers [& it/fae] yeah, i did it out of tree a few versions ago and build times were rough. the numbers i had were:
  1. reference for build perf on my laptop: nom-build -A rustc-unwrapped --check on nixpkgs master: 1h52m17s

  2. mrustc: 5m2s

  3. rust-1900: 1h54m18s (you can probably cut this one down but i didn't bother at the time)

  4. rust-1911: 17m33s

  5. rust-1920: 18m53s

  6. rust-1931: 18m1s

  7. rustc-1940: 1h48m52s (literally just pkgs.rustc-unwrapped.overrideAttrsed)

and that's uh. really rough when the chain gets big
16:13:51
@whispers:catgirl.cloudwhispers [& it/fae] yeah, i did it out of tree a few versions ago and build times were rough. the numbers i had were:
  1. reference for build perf on my laptop: nom-build -A rustc-unwrapped --check on nixpkgs master: 1h52m17s

  2. mrustc: 5m2s

  3. rust-1_90_0: 1h54m18s (you can probably cut this one down but i didn't bother at the time)

  4. rust-1_91_1: 17m33s

  5. rust-1_92_0: 18m53s

  6. rust-1_93_1: 18m1s

  7. rustc-1_94_0: 1h48m52s (literally just pkgs.rustc-unwrapped.overrideAttrsed)

and that's uh. really rough when the chain gets big
16:14:28
@whispers:catgirl.cloudwhispers [& it/fae] *

yeah, i did it out of tree a few versions ago and build times were rough. the numbers i had were:

  • reference for build perf on my laptop: nom-build -A rustc-unwrapped --check on nixpkgs master: 1h52m17s
  • mrustc: 5m2s
  • rust-1_90_0: 1h54m18s (you can probably cut this one down but i didn't bother at the time)
  • rust-1_91_1: 17m33s
  • rust-1_92_0: 18m53s
  • rust-1_93_1: 18m1s
  • rustc-1_94_0: 1h48m52s (literally just pkgs.rustc-unwrapped.overrideAttrsed)
    and that's uh. really rough when the chain gets big (especially for local builds on staging that involve rust)
16:15:12
@whispers:catgirl.cloudwhispers [& it/fae] *

yeah, i did it out of tree a few versions ago and build times were rough. the numbers i had were:

  • reference for build perf on my laptop: nom-build -A rustc-unwrapped --check on nixpkgs master: 1h52m17s
  • mrustc: 5m2s
  • rust-1_90_0: 1h54m18s (you can probably cut this one down but i didn't bother at the time)
  • rust-1_91_1: 17m33s
  • rust-1_92_0: 18m53s
  • rust-1_93_1: 18m1s
  • rustc-1_94_0: 1h48m52s (literally just pkgs.rustc-unwrapped.overrideAttrsed)

and that's uh. really rough when the chain gets big (especially for local builds on staging that involve rust)

16:16:25
@pyrox:pyrox.devdish [Fox/It/She]mrustc would be good only if they could do smaller releases that keep up with rust more closely, but i think that requires a higher bus factor which just isn't a thing atm16:19:10
@siraben:matrix.orgsirabenwe could have a non-blocking path for it?16:22:13
@siraben:matrix.orgsirabensimilar to how minimal-bootstrap used to do that before the switchover16:22:28

Show newer messages


Back to Room ListRoom Version: 9