| 25 Nov 2025 |
 connor (he/him) | https://github.com/NixOS/nixpkgs/pull/464957 | 15:52:14 |
| connor (he/him) | https://github.com/NixOS/nixpkgs/pull/465047 | 20:23:29 |
 Gaétan Lepage | https://github.com/NixOS/nixpkgs/pull/450587 | 20:24:55 |
| 26 Nov 2025 |
| connor (he/him) | SomeoneSerge (back on matrix) I updated https://github.com/NixOS/nixpkgs/pull/459416 please merge | 02:57:01 |
| connor (he/him) | 🤦♂️ | 15:37:52 |
| connor (he/him) | https://github.com/onnx/onnx-tensorrt/pull/1043 moved from the pycuda to cuda python package and documented it nowhere I've been able to find | 15:38:34 |
| connor (he/him) | Kevin Mittman (UTC-7): the entry for --verbose seems to be for --no-dry-run, which doesn't have an entry: https://docs.nvidia.com/cuda/cuda-compiler-driver-nvcc/#verbose-v | 18:12:52 |
| connor (he/him) | well, pycuda's tests exposed a few issues with how NVCC works
notably that it dies if GCC isn't on the path -- it doesn't even use the path modifications from nvcc.profile | 18:38:12 |
| connor (he/him) | so this is now a larger PR https://github.com/NixOS/nixpkgs/pull/465047 | 18:38:20 |
| connor (he/him) | I'm going to split out the NVCC changes to a different PR and make pycuda a stacked PR | 18:51:51 |
| connor (he/him) | :F | 18:51:53 |
| connor (he/him) | https://github.com/NixOS/nixpkgs/pull/465329 | 18:57:02 |
| 28 Nov 2025 |
 yorik.sar | Finally got around to doing this: https://github.com/NixOS/nixos-homepage/pull/1903 - connor (burnt/out) (UTC-8) SomeoneSerge (back on matrix)Gaétan Lepage feel free to approve :) | 15:01:30 |
| yorik.sar | I guess I’ll make another one for nixos-cuda.org :) | 15:05:22 |
| yorik.sar | Here it is: https://github.com/nixos-cuda/nixos-cuda.org/pull/2 | 15:12:12 |
| 29 Nov 2025 |
 matthewcroughan | Is there anybody that knows how you add cuda stuff to a rust build? | 01:54:22 |
| matthewcroughan | I have a rust build that is silently doing nothing when cuda isn't present, and not indicating in logs when it is being used or isn't | 01:54:37 |
| matthewcroughan | Leads to https://github.com/alvr-org/ALVR/issues/2792 | 01:55:02 |
 SomeoneSerge (back on matrix) | idk is it even about cuda? Any failing dlopens? @matthewcroughan:defenestrate.it: | 04:30:26 |
| matthewcroughan | I'm not sure, what do you think based on the issue? | 16:12:46 |
| matthewcroughan | Apparently people can get it to work by steam-run'ing the stuff they provide via github releases | 16:13:09 |
| SomeoneSerge (back on matrix) | Id_debuuuuuuuuuuuug | 16:49:33 |
| matthewcroughan | Yeah I can also get it working by steam-run'ing the github release | 17:01:30 |
| matthewcroughan | compiling onnxruntime takes forever though | 17:01:35 |
| matthewcroughan | so I'm doing that whilst compiling what I think could be a fix | 17:01:42 |
| 4 Aug 2022 |
|  Winter (she/her) joined the room. | 03:26:42 |
| Winter (she/her) | (hi, just came here to read + respond to this.) | 03:28:52 |
 tpw_rules | hey. i had previously sympathzied with samuela and like i said before had some of the same frustrations. i just edited my github comment to add "[CUDA] packages are universally complicated, fragile to package, and critical to daily operations. Nix being able to manage them is unbelievably helpful to those of us who work with them regularly, even if support is downgraded to only having an expectation of function on stable branches." | 03:29:14 |
| Winter (she/her) | In reply to @tpw_rules:matrix.org
i'm mildly peeved about a recent merging of something i maintain where i'm pretty sure the merger does not own the expensive hardware required to properly test the package. i don't think it broke anything but i was given precisely 45 minutes to see the notification before somebody merged it ugh, 45 minutes? that's... not great. not to air dirty laundry but did you do what samuela did in the wandb PR and at least say that that wasn't a great thing to do? (not sure how else to word that, you get what i mean) | 03:30:23 |
| tpw_rules | no, i haven't yet, but i probably will | 03:31:03 |
