| 26 Nov 2025 |
 connor (burnt/out) (UTC-8) | 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 (burnt/out) (UTC-8) | 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 (burnt/out) (UTC-8) | so this is now a larger PR https://github.com/NixOS/nixpkgs/pull/465047 | 18:38:20 |
| connor (burnt/out) (UTC-8) | I'm going to split out the NVCC changes to a different PR and make pycuda a stacked PR | 18:51:51 |
| connor (burnt/out) (UTC-8) | :F | 18:51:53 |
| connor (burnt/out) (UTC-8) | 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 |
| 1 Dec 2025 |
| connor (burnt/out) (UTC-8) | Make sure you’re setting config.cudaCapabilities explicitly to speed up compilation | 12:39:34 |
| connor (burnt/out) (UTC-8) | Packaging onnx/onnx-tensorrt/onnxruntime and getting them working for a range of cuda/cudnn/tensorrt releases is maddening oh my god:
- Fix for GCC 11/NVCC's template processing https://github.com/nixos-cuda/cuda-legacy/commit/79c3026f1a761125b6faa609c5f9e56e723a4568
- https://github.com/nixos-cuda/cuda-legacy/issues/6 since ONNX Runtime needs GCC > 11.1 and I need it to build with 11.4
- I'm fairly certain I managed to get a build failure from ONNX Runtime with CUDA 11.8 because a reference to
cuda_nvcc was held onto, so ONNX Runtime failed the build
| 21:32:54 |
| 2 Dec 2025 |
| connor (burnt/out) (UTC-8) | Okay NVCC from CUDA 11.4 still dies horrifically when using newer versions of glibc with GCC 11 so that’ll stay on GCC 10.
Also it seems onnxruntime 1.22.2 needs CCCL newer than what 11.4 provides, so supporting onnxruntime on 11.4 means finding an older version which works :l | 01:21:58 |
 Gaétan Lepage | connor (burnt/out) (UTC-8) I approved your onnx PR | 08:14:41 |
| Gaétan Lepage | I can tackle the bump to 1.20.0 after it's merged | 08:14:56 |
 teto | is caching disabled for unstable ? I have to build onnxruntime and then I read this https://discourse.nixos.org/t/cuda-cache-for-nix-community/56038/3 | 11:45:21 |
 hexa | building cuda packages on nix-community was discontinued | 12:07:37 |
| hexa | there is now the flox cache, which builds for their versions of nixpkgs | 12:08:00 |
| hexa | * there is now the flox cache, which builds for their versions of nixpkgs, which don't really align with our channels | 12:08:09 |
| hexa | and possibly the build results from nixos-cuda.org | 12:08:32 |
| teto | I had totally missed that. The discourse comment made it sound like it is retaliation against flox actions ? | 12:11:30 |
