| 18 Dec 2025 |
 bake.monorail | * more on practical things, I assume you're somehow involved in maintaing compilers, what would you think about making compilers more externally overridable. I'm thinking about making versions an argument of pkgs/development/compilers/gcc/all.nix. I guess it wouldn't be too bad, what do you think? | 13:57:16 |
 emily | wouldn't really do much good | 14:01:13 |
| emily | the GCC derivations have pretty extensive version conditionals | 14:01:20 |
| emily | the LLVM ones are closer to being something you can reasonably override versions out-of-tree but still not really there | 14:01:35 |
| emily | I suggest just maintaining a fork of gcc/ | 14:01:45 |
| emily | it will be less painful than a nest of hacky overrideAttrs | 14:02:00 |
| emily | (I also suggest putting this effort into making a newer GCC work instead) | 14:02:15 |
| bake.monorail | OK, thanks for the feedback | 14:02:29 |
 @rosssmyth:matrix.org | Something I was considering yesterday:
Currently we have gcc-arm-embedded, which is a pre-built GCC distribution. It has a manifest with all the configure flags. How hard is it to add a new version of GCC? I took a little look and there's a lot of machinery all over the place in the GCC directory. Maybe easier to use the NG package set?
| 15:22:17 |
