NixOS CUDA | 289 Members | |
| CUDA packages maintenance and support in nixpkgs | https://github.com/orgs/NixOS/projects/27/ | https://nixos.org/manual/nixpkgs/unstable/#cuda | 57 Servers |
| Sender | Message | Time |
|---|---|---|
| 23 Oct 2024 | ||
Btw connor (he/him) (UTC-7) we are facing a super weird onnx issue in this PR.Basically, updating torchmetrics makes some random package further down the tree fail on aarch64-linux.In case you have some idea... | 16:29:45 | |
| Yeah part of the reason I’m iterating in a separate repo for this stuff is because I can just say “SCREW THE OTHER PLATFORMS MUAHAHAHHAAH” (and also because I don’t have to re-evaluate nixpkgs on every change). I’ll try to take a look… but no promises :) | 16:31:23 | |
| Okay I looked at it and have no idea 🤷♂️ | 16:32:07 | |
| The whole ONNX ecosystem is difficult to package for Nix because they all use both git submodules AND CMake’s fetchcontent functionality, making it super difficult to package with stuff we already provide. For some packages, they build with flags we don’t, or have patches they apply before building, so it’s painful. | 16:34:04 | |
| That’s partly why my packaging of Onnxruntime involves rewriting some of their CMake files | 16:34:35 | |
| I also love that onnx by default builds with ONNX_ML=0 (disabling old APIs in favor of new ones), but various projects depend on it being set to one value or the other, so you could very easily end up with two copies of onnx, each configured with a different value for ONNX_ML. | 16:36:22 | |
| God what a nightmare | 16:36:36 | |
| We should also update OpenCV at some point to 4.10 if we haven’t already so it can build with CUDA 12.4+ | 16:38:16 | |
| Oh! Unrelated but this was a cute change I made that I quite like: https://github.com/ConnorBaker/cuda-packages/blob/c81a6595f07456c6cc34d8976031c4fa972a741f/cudaPackages-common/backendStdenv.nix#L36 Sets some defaults for the CUDA stdenv and adds a name prefix, similar to what the Python packaging does, for more descriptive store paths | 16:40:07 | |
| Thanks for taking the time to look at it and explain all of this ! | 21:26:24 | |
| 25 Oct 2024 | ||
| * | 11:51:25 | |
| https://gist.github.com/ConnorBaker/6c9c522d46e4244eb33d2aad94c753b0 | 11:51:27 | |
| 26 Oct 2024 | ||
| 🥲 | 20:34:04 | |
Download clipboard.png | 20:34:07 | |
| 27 Oct 2024 | ||
Does anyone of you use clangd as a C LSP, with cudatoolkit coming from a shell? clangd seems not to take notice of CUDA in that case, saying Cannot find CUDA installation; ... | 07:54:44 | |
Also, does cudatoolkit miss a dependency on gcc, or am I mistaken by this error: | 07:56:37 | |
Also, does cudatoolkit miss a dependency on gcc, or am I mistaken by this error:EDIT: No, it indeed seems to try and find GCC: | 07:57:18 | |
In reply to @msanft:matrix.orgYea we don't link gcc directly in nvcc but provide it independently via the overridden stdenv | 09:40:39 | |
In reply to @glepage:matrix.orgA horror security-wise though xD | 11:08:32 | |
| 12:20:53 | ||
connor (he/him) (UTC-7): hiya, any idea why there's nothing like find_package(protobuf) in onnx/onnx before it tests for TARGET protobuf::libprotobuf[-lite]? Is it supposed to inherit these variables from onnxruntime or something? | 15:32:43 | |
| 28 Oct 2024 | ||
| I would have thought that, but ONNX is also built directly and not just as a dependency of onnxruntime, so I don’t think it’s because they intend ONNX to be built solely as a subproject and leave configuration up to the parent I don’t understand how they expect it to be magically detected… but it works for me from what I remember (https://github.com/ConnorBaker/cuda-packages/blob/main/cudaPackages-common/onnx.nix) Although I’m doing the cursed C++/Python install and had to carefully choose dependencies from the normal package set and from Python packages 🤷♂️ | 06:39:55 | |
| 29 Oct 2024 | ||
| 19:58:14 | ||
| 30 Oct 2024 | ||
| 07:49:56 | ||
In reply to @connorbaker:matrix.orgHey wanna publish a review on exposing extendMkDerivationArgs? | 15:24:02 | |
| Could help with upstreaming the tricks | 15:24:30 | |
Btw at NixCon Tom brought up moving cudaSupport &el into the system which I think was raised here at least on a few occasions | 15:26:05 | |
| Maaaybe it's time? :) | 15:26:11 | |
We could even skip exposing nixpkgsFun in the public api then: could be just pkgsCross.cuda | 15:27:51 | |
GPU tests? That's buildPlatform with cuda | 15:28:50 | |