| 4 Dec 2025 |
 Alexandros Liarokapis | any idea what is the difference between torch-bin and torchWithCuda ? | 12:28:06 |
 Robbie Buxton | In reply to @aliarokapis:matrix.org
any idea what is the difference between torch-bin and torchWithCuda ? Iirc torch-bin is torch not built from source and torchWithCuda is torch built from source with cuda enabled forced regardless of global configuration? | 13:34:25 |
 Gaétan Lepage | Yes, this is it. | 13:46:25 |
| Alexandros Liarokapis | and it is apparently in the nixos cache by defualt? | 14:05:18 |
| Alexandros Liarokapis | * and it is apparently in the nixos cache by default? | 14:16:57 |
| Gaétan Lepage | I'm not sure torchWithCuda will be.
For `cudaSupport-enabled packages, consider using the Flox binary cache, or the NixOS-CUDA one. | 14:28:52 |
 connor (burnt/out) (UTC-8) | I’ll try to answer this later today. Depending on how comfortable you are with Nix, pull in the overlay for CUDA-legacy (https://github.com/nixos-cuda/cuda-legacy) to add a bunch of manifests and then customize the package set to your liking by using override on the CUDA package set and providing the manifest version you want. The docs are lacking an example for this.
As you discovered, NVCC may support capabilities but that doesn’t mean the big libraries most people use (cuDNN, libcublas, TensorRT, etc.) do. We have the unenviable job of either adopting the latest release for each version or fixing them in time and never updating. The decision is made more difficult by the fact NVIDIA seems to fix bugs by doing major/minor releases much more often than patch releases.
The trace-verbose thing is handy but undocumented and only exists because implementations of the Problems RFC keep getting bikeshedded to death.
We should probably have a section in the CUDA docs which list supported capabilities for each package set. Could be automatically generated given I added the available capabilities for each release to backendStdenv.
| 16:28:20 |
| connor (burnt/out) (UTC-8) | god i hate computers | 16:29:35 |
| connor (burnt/out) (UTC-8) | Reminder to self: post about changes I’ve been working on / need (fix adding attributes to backendStdenv, nvcc multiple outputs again, ccache) | 16:33:13 |
 SomeoneSerge (back on matrix) |
problems rfc
Tha release was cut off, IMO we should push a half-assed partial impl as per my closed PR in, bc 99% of the features we don't care about
| 19:52:52 |
| SomeoneSerge (back on matrix) |
stdenv attributes
...also nuke the other 90% attributes that don't actually belong and aren't even used
| 19:53:40 |
 corroding556 | Thank you so much! cuda-legacy was exactly what I needed.
Managed to get the configuration successfully built and deployed, going to try out an application which uses CUDA soon to verify everything is in working order.
Unenviable does seem like an appropriate word, digging into all this really made me appreciate how much work goes into making any of this possible.
Pointing folks like myself on older/unsupported hardware towards cuda-legacy (an example in the wiki/manual would be great) seems like a reasonable way to do things. | 23:52:06 |
