| 18 Dec 2023 |
 patryk4815 | * Nick Cao: This fix for gcc13 is only available on staging? https://github.com/NixOS/nixpkgs/pull/275084
thanks for merging :) | 17:31:17 |
| patryk4815 | * Nick Cao: ~~This fix for gcc13 is only available on staging? https://github.com/NixOS/nixpkgs/pull/275084 ~~
thanks for merging :) | 17:46:50 |
| patryk4815 | * Nick Cao: This fix for gcc13 is only available on staging? https://github.com/NixOS/nixpkgs/pull/275084
thanks for merging :) | 17:47:16 |
| 19 Dec 2023 |
 fgaz | In reply to @patryk4815:matrix.org
Nick Cao: This fix for gcc13 is only available on staging? https://github.com/NixOS/nixpkgs/pull/275084
thanks for merging :) It's on master, not staging, and it has yet to reach the channels | 09:24:22 |
 pouspous | once https://github.com/NixOS/nixpkgs/pull/274853 we'll be able to fully cross-compile nixos-star64 and thus remove lib.optionals (stdenv.buildPlatform == stdenv.hostPlatform) | 14:05:08 |
| pouspous | (or at least I would find it nice to remove it by default) | 14:06:10 |
| pouspous | * once https://github.com/NixOS/nixpkgs/pull/274853 is merged into master we'll be able to fully cross-compile nixos-star64 and thus remove lib.optionals (stdenv.buildPlatform == stdenv.hostPlatform) | 14:06:39 |
| fgaz | pouspous: I don't understand the connection between the two and why you want to remove that line | 14:49:41 |
| fgaz | * pouspous: I don't understand the connection between the two and why you want to remove that line | 14:50:22 |
| fgaz | cross-compiled build time dependencies aren't going to help native builds, they have different hashes | 14:51:20 |
| fgaz | by the way, I plan to remove that part completely once I finish setting up my attic cache | 14:53:52 |
| pouspous | oh I didn't know that's a shame. so cross-compiling (say from x86_64 to riscv64) package in system.extraDependencies will still trigger a recompilation of those packages when request on the riscv machine ? | 14:56:42 |
| pouspous | * oh I didn't know that's a shame. so cross-compiling (say from x86_64 to riscv64) packages in system.extraDependencies will still trigger a recompilation of those packages when request on the riscv machine ? | 14:57:52 |
| pouspous | I might not get the purpose of system.extraDependencies | 15:13:26 |
| pouspous | I understand this option as being a list of packages that must remain on the system, even if not necessarily referenced by anything in the store, right ? | 15:15:02 |
| fgaz | In reply to @pouspous:matrix.org
oh I didn't know that's a shame. so cross-compiling (say from x86_64 to riscv64) packages in system.extraDependencies will still trigger a recompilation of those packages when request on the riscv machine ? that's correct, and is the reason why I wrote that conditional | 15:20:48 |
| fgaz | In reply to @pouspous:matrix.org
I understand this option as being a list of packages that must remain on the system, even if not necessarily referenced by anything in the store, right ? yes, and I use it as sort of a lighter version of system.includeBuildDependencies | 15:21:36 |
| pouspous | So why do cross-compiled packages in system.extraDependencies need recompilation when requested on the native machine, but not packages in environment.systemPackages. Them too should have a different hash right ? | 15:50:57 |
| pouspous | * So why do cross-compiled packages in system.extraDependencies need recompilation when requested on the native machine, but not packages in environment.systemPackages ? Them too should have a different hash right ? | 15:51:18 |
| pouspous | * So why do cross-compiled packages in system.extraDependencies need recompilation when requested on the native machine, but not packages in environment.systemPackages ? Them too should have a different hash, right ? | 15:51:29 |
