| 12 Nov 2024 |
 Randy Eckenrode | https://github.com/NixOS/nixpkgs/blob/45d55abd3964711133c2c3bdfdae82e178e9ce55/pkgs/stdenv/darwin/default.nix#L1262-L1278 | 22:47:28 |
| Randy Eckenrode | If clang is correctly setting itself up as a multi-target compiler, should that be overlaid unconditionally? | 22:47:45 |
| Randy Eckenrode | Or at least the LLVM portion. I don’t know about the Darwin binutils stuff. | 22:48:01 |
| Randy Eckenrode | That allows clang.cc to equal the cross one in buildPackages even on Darwin.
| 22:48:31 |
| 13 Nov 2024 |
 p14 | In reply to @reckenrode:matrix.org
If clang is correctly setting itself up as a multi-target compiler, should that be overlaid unconditionally? Not clear to me. The unwrapped clang can be; but llvmPackages contains wrapped clangs which embed information about the targetPlatform, right? | 17:42:07 |
| Randy Eckenrode | In reply to @p14:matrix.org
Not clear to me. The unwrapped clang can be; but llvmPackages contains wrapped clangs which embed information about the targetPlatform, right? Assuming the targetPlatform stuff gets dropped, so the same Clang can be used for all cross builds. | 18:11:41 |
| p14 | In reply to @reckenrode:matrix.org
Assuming the targetPlatform stuff gets dropped, so the same Clang can be used for all cross builds. Same llvmPackages.clang.cc but not same llvmPackages.clang. | 18:12:48 |
| Randy Eckenrode | https://github.com/NixOS/nixpkgs/blob/45d55abd3964711133c2c3bdfdae82e178e9ce55/pkgs/stdenv/darwin/default.nix#L306_L326 | 18:13:11 |
| Randy Eckenrode | * | 18:13:42 |
| Randy Eckenrode | @p14:matrix.org: Just double-checked what’s overlaid. See above. Only those packages are overlaid. No wrappers are included in those packages. | 18:14:35 |
| p14 | Ah cool. That was opaque to me, thanks for explaining! | 18:15:21 |
| p14 | I wish we had a simpler llvmPackages extend expression. | 18:15:37 |
| Randy Eckenrode | The Darwin stdenv uses functions to group overrides for the stdenv bootstrap (and provide consistency between stages). That stuff is new with the rework. The wrapper won’t be overlaid because it’s not in those functions. | 18:16:27 |
| Randy Eckenrode | Darwin bintools can target either Darwin platform, so it probably ought to be overlaid as well (but not the wrapper, of course). | 18:17:02 |
| Randy Eckenrode | Of course, once the LLVM/Clang fixes are merged. | 18:17:20 |
 Tristan Ross | I'll try taking a look at those PR's tonight and tomorrow | 19:18:46 |
| p14 | I'd appreciate any input on ideas for where I might put an assert / how to implement an assert that clang.cc == pkgsStatic.stdenv.cc.cc == pkgsLLVM.stdenv.cc.cc for https://github.com/NixOS/nixpkgs/pull/355532. I figure I can't just put one in the expression for every eval since we don't want to be evaluating stuff unnecessarily, so presumably it should go into a release test of some sort; but is there anything I can use for precommit? | 19:56:39 |
 emily | I think it could go into stdenv. that doesn't sound like an expensive check to eval all the time | 20:03:44 |
| emily | though it should probably be .outPath | 20:03:50 |
| emily | since comparing derivations is mildly evil I think | 20:03:56 |
| p14 | +1 on outPath; but I'm thinking that evaling some cross derivation surely involves a substantial amount of additional eval you otherwise don't need. | 20:13:20 |
| emily | oh, sorry, I only skimmed the message and missed the cross package sets | 20:13:52 |
| emily | yeah that wouldn't be good | 20:13:54 |
| emily | maybe it's a pkgs/test type thing? | 20:14:02 |
| emily | for hooks, I mean – you could just nix eval | 20:14:26 |
| emily | assuming you just mean for your local purposes | 20:14:31 |
| p14 | I mean I'd like to defend the effect of that PR: to ensure we don't actually regress it. | 20:18:47 |
| p14 | Ideally in pre-commit. | 20:19:06 |
| emily | we don't do pre-commit | 20:19:41 |
| emily | but you could put it in CI | 20:19:44 |
