| 2 Sep 2025 |
|  @wolfgangwalther:matrix.org joined the room. | 14:11:50 |
| 3 Sep 2025 |
|  @ghpzin:envs.net joined the room. | 07:30:19 |
|  Winter joined the room. | 15:13:01 |
| Winter | i'm attempting to make a stdenv that uses an old (incompatible with our bootstrap tools) glibc -- i've tried to do things like "fake" cross to work around the issue, but always get stuck in some bootstrapping stage (either 3 or 4 depending on the strategy) because binutils from the previous stage still depends on new glibc. is my best bet for now to maybe create a custom stdenv that somehow bootstraps binutils from newer glibc -> older glibc? i can compile old glibc with new glibc but binutils is where it gets fun :/ | 15:15:39 |
| Winter | * i'm attempting to make a stdenv that uses an old (incompatible with our bootstrap tools) glibc -- i've tried to do things like "fake" cross to work around the issue, but always get stuck in some bootstrapping stage (either 3 or 4 depending on the strategy) because binutils from the previous stage still depends on new glibc, so e.g. expand-response-param can never get compiled. is my best bet for now to maybe create a custom stdenv that somehow bootstraps binutils from newer glibc -> older glibc? i can compile old glibc with new glibc but binutils is where it gets fun :/ | 15:16:53 |
| Winter | obviously the easiest route may be to just make bootstrap tools, but that'll require me downgrading to a nixpkgs rev and then probably get stuck in a bootstrapping-induced loop | 15:22:51 |
| Winter | not sure if i can even do this in one stage but replaceStdenv only lets me use one stage :-/ | 15:37:06 |
| Winter | guess i can make it let me use multiple | 15:37:13 |
| Winter | i suppose the ~nicest?? way to do it will be to modify stage1 (or add a stage between 0 and 1) to rebuild binutils | 15:48:53 |
| Winter | * i suppose the ~nicest?? way to do it will be to modify stage2 | 15:52:02 |
