| 6 Aug 2025 |
 connor (burnt/out) (UTC-8) | IIRC PyTorch (like OpenCV) has a cxxdev output you need to include if you want to use it in a C++ project; give that a try | 15:13:52 |
| connor (burnt/out) (UTC-8) | Oh you already tried that, never mind
Have you tried with just the cxxdev output? And torch should only go in buildInputs, not nativeBuildInputs | 15:15:11 |
| connor (burnt/out) (UTC-8) | But generally avoid the dev output and make sure to use the cxxdev output for C++ projects | 15:16:18 |
| 7 Aug 2025 |
 grw00 | hey all- is there a similar channel/effort for rocm in nixos? | 09:57:51 |
 le-chat | Now magma fails to build, I did flake update. Switched to nixos-25.05, reran with torch.cxxdev only in buildInputs. Will see. | 10:09:53 |
| connor (burnt/out) (UTC-8) | Make sure you’re specifying cudaCapabilities in config when you import Nixpkgs, otherwise Magma will fail to link because of the sheer amount of device code generated lol | 15:10:33 |
| connor (burnt/out) (UTC-8) | There is/was a ROCm team, not sure about where they are or what they’re up to currently | 15:11:16 |
| 8 Aug 2025 |
|  0x4A6F joined the room. | 06:56:41 |
| connor (burnt/out) (UTC-8) | Kevin Mittman you and SomeoneSerge (Ever OOMed by Element) should chat at some point about the database of binary archives he’s building because I think it might be useful to you as well as us | 14:12:07 |
 indoor_squirrel | In reply to @connorbaker:matrix.org
Kevin Mittman you and SomeoneSerge (Ever OOMed by Element) should chat at some point about the database of binary archives he’s building because I think it might be useful to you as well as us COLLAB!!! | 14:18:16 |
 Kevin Mittman (UTC-8) | Sounds good to me | 16:48:45 |
| Kevin Mittman (UTC-8) | Also if there are any CUDA 13 related packaging questions, let me know | 16:49:27 |
| 10 Aug 2025 |
|  matthewcroughan changed their display name from matthewcroughan to matthewcroughan @ WHY2025 (DECT: 8793). | 11:36:29 |
| 11 Aug 2025 |
| connor (burnt/out) (UTC-8) | For awareness:
- https://github.com/NixOS/nixpkgs/issues/428546
- https://github.com/NixOS/nixpkgs/issues/432646
If anyone has ideas, please chime in. I likely won't have a chance to dig into it for a while :L
| 14:59:10 |
 apyh | ... so, nobody's packaged nvshmem yet, eh? 😭
building torch 2.9.0-nightly bails with > error: auto-patchelf could not satisfy dependency libnvshmem_host.so.3 wanted by /nix/store/73phyh3qhgjnihg20z1jf456xmld6dxr-python3.12-torch-2.9.0.dev20250811/lib/python3.12/site-packages/torch/lib/libtorch_nvshmem.so, i guess i gotta package it 😭 | 20:09:57 |
| apyh | thank go that wasn't so bad at all lol | 21:46:57 |
| 12 Aug 2025 |
 Luke | This would be really great to have imo, how can we get this started? | 03:49:22 |
| 13 Aug 2025 |
| le-chat | I've restricted cudaCapabilities, built torch. NNStreamer build fails at mesonConfigurePhase with messages:
Run-time dependency pytorch found: NO (tried pkgconfig and cmake)
Run-time dependency torch found: NO (tried pkgconfig and cmake)
meson.build:693:6: ERROR: Problem encountered: pytorch-support is enabled but unable to find the target dependency
The gist is updated.
What should I try further?
| 09:29:03 |
| le-chat | Looking into a build directory with --keep-failed I see in build/meson-logs/meson-log.txt.
env[PKG_CONFIG_PATH]: {long path here}
env[PKG_CONFIG]: /nix/store/d667kdfbfn17905f7kmdl33r9gvwzaji-pkg-config-wrapper-0.29.2/bin/pkg-config
-----------
Called: `/nix/store/d667kdfbfn17905f7kmdl33r9gvwzaji-pkg-config-wrapper-0.29.2/bin/pkg-config --modversion torch` -> 1
stderr:
Package torch was not found in the pkg-config search path.
Perhaps you should add the directory containing `torch.pc'
to the PKG_CONFIG_PATH environment variable
This long path does not contain any torch directory.
Also none of torch directories contain torch.pc.
| 12:12:48 |
| matthewcroughan changed their display name from matthewcroughan @ WHY2025 (DECT: 8793) to matthewcroughan. | 17:23:55 |
| Luke | There is now! #ROCm:nixos.org | 17:37:21 |
| 15 Aug 2025 |
| connor (burnt/out) (UTC-8) | Two bugs to be aware of:
- https://github.com/NixOS/nixpkgs/issues/434096
- https://github.com/NixOS/nixpkgs/issues/434101
| 23:31:17 |
| 16 Aug 2025 |
|  Martin Charles joined the room. | 04:58:51 |
| Martin Charles | curious, why is nvcomp missing from nixpkgs cuda? | 05:15:27 |
| connor (burnt/out) (UTC-8) | lack of time, mostly -- there is a redist for it (https://developer.download.nvidia.com/compute/nvcomp/redist/redistrib_5.0.0.6.json) | 05:18:50 |
| Martin Charles | hmm ok, i'm happy to package it are you guys open to patches? | 05:25:04 |
| Martin Charles | is there some way to consume this? | 05:26:22 |
| Martin Charles | it appears this is what the release.nix files are for | 05:26:33 |
| Martin Charles | this nvcomp one seems different in that it has multiple cuda versions for each library version which the other packages don't seem to have? | 05:32:51 |
| connor (burnt/out) (UTC-8) | You can try doing something similar to the steps listed here: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-frameworks/cuda.section.md#updating-cutensor-cuda-updating-cutensor
I've not had a chance to update that script in a while, so not sure how well/if it still works
Generally we use the script from the docs to take the manfiest provided by NVIDIA (dubbed the redist or redistrib manifest) and create a feature manifest which tells us things relevant to the Nix packaging
Then create a fixup function (https://github.com/NixOS/nixpkgs/tree/master/pkgs/development/cuda-modules/_cuda/fixups) for the packages from the manifest
Lastly add it to the package sets by creating and importing an extension, like https://github.com/NixOS/nixpkgs/blob/3b0feaf8c2160a10a974c890e93f5f5387728784/pkgs/top-level/cuda-packages.nix#L201 | 05:48:12 |
