| 31 Oct 2025 |
 Gaétan Lepage | Actually, I was able to build python3Packages.torch and firefox with an empty propagatedBuildInputs in cuda_nvcc. Why do we need it exactly? | 23:25:46 |
 connor (he/him) | If it’s in propagatedBuildInputs it should still slide out of the dependencies far enough down
It likely worked because the current stdenv is supported by the version of NVCC in the default CUDA package set
stdenv.cc needs to be in NVCC’s propagatedBuildInputs because NVCC needs it available it when it is in nativeBuildInputs | 23:28:42 |
| connor (he/him) | I believe Firefox-unwrapped and Firefox should use disallowedReferences. I’m trying to think why it’s okay to try to block that transitively? | 23:30:54 |
| Gaétan Lepage | Thanks! Opened https://github.com/NixOS/nixpkgs/pull/457391. Let's see what the firefox maintainers think. | 23:42:18 |
| 1 Nov 2025 |
 SomeoneSerge (back on matrix) | Catching up just now, but I do not see any conclusion on why and how firefox retains a path to gcc after the build? | 01:50:57 |
| SomeoneSerge (back on matrix) | That should not be happening | 01:51:02 |
| SomeoneSerge (back on matrix) | Ah. We didn't used to have that, cc in propagated inputs Since when do we? We did used to propagate a hook though, I forget under what conditions if any | 01:53:05 |
