| 3 Sep 2025 |
 Winter | tried doing the cursed thing of:
build old glibc in stage2 build new xgcc in a subsequent stage, using the old xgcc's stdenv, but pointing to the old glibc as build sysroot use that xgcc like nothing has changed
but that also blows up, i guess expectedly | 19:47:15 |
| Winter | i guess there is really no nice way forward here lol | 19:47:30 |
| Winter | (i really don't wanna use an old nixpkgs!) | 19:47:37 |
| Winter | curiously, it also seems like my xgcc in between stages 2/3 and the binutils in stage4 can build at the same time?! | 19:52:01 |
| Winter | i have no clue how on earth that's possible | 19:52:46 |
 dish [Fox/It/She] | ugh why is our bootstrap not following the live-bootstrap build chain | 19:54:43 |
| Winter | 🤔 | 19:55:08 |
| Winter | 
Download image.png | 19:55:09 |
| dish [Fox/It/She] | talking about minimal-bootstrap which is fully from source and should be(but clearly isn't) following the build chain that live-bootstrap establishes | 19:56:12 |
| dish [Fox/It/She] | sorry if that was confusing | 19:56:26 |
| dish [Fox/It/She] | * sorry if that was confusing and/or not what you were talking about | 19:56:32 |
| Winter | it's not | 19:56:48 |
| Winter | i am talking about our normal bootstrapping process | 19:57:05 |
