NixOS CUDA - Public Room Timeline - Matrix Static

	NixOS CUDA	293 Members
	CUDA packages maintenance and support in nixpkgs \| https://github.com/orgs/NixOS/projects/27/ \| https://nixos.org/manual/nixpkgs/unstable/#cuda	59 Servers

You have reached the beginning of time (for this room).

Sender	Message	Time
6 Feb 2025
connor (burnt/out) (UTC-8)	I think the first one is related to compiler version and the second one may be static libraries for cuda_cudart not being in one of the default installed outputs Although as a caveat I haven’t looked at Nixpkgs in a bit	15:16:59
ruro	Yeah, it seems that a bunch of libraries are actually missing, not just the cudart_static. I am currently investigating.	15:19:01
connor (burnt/out) (UTC-8)	I know I did this in the out of tree because it’s a pain in the ass to explicitly include the static libraries for cuda_cudart for CMake (for some unknowable reason they’re required when doing compiler identification): https://github.com/ConnorBaker/cuda-packages/blob/dd0266aece12e5177e3ce32d62b6665c33847837/modules/redists/cuda/overrides/common/cuda_cudart.nix#L11 But generally to reduce the build time closure static libraries aren’t pulled in by default	15:19:06
connor (burnt/out) (UTC-8)	Might have to check the CMake for the CUDA samples — it’s possible they’re doing only static builds or preferentially linking against static libraries	15:19:58
	djacu joined the room.	15:49:57
ruro	This might be a stupid question, but when the nixpkgs manual says All new projects should use the CUDA redistributables available in `cudaPackages` in place of `cudaPackages.cudatoolkit` does it mean that individual derivations from `cudaPackages.*` should be manually added to `buildInputs`/`nativeBuildInputs`. For example, would this mean that I should just manually add `cuda_nvcc` to `nativeBuildInputs`. What if the upstream package expects a single `CUDA_PATH` path containing all the cuda dependencies? I think, I saw some people using `buildEnv` to collect all of the required binaries/libraries under a single path, but I am not sure if this is the most elegant way to do this (also, it's not immediately clear, how would a single `CUDA_PATH` interact with cross compilation).	16:54:13
ruro	* This might be a stupid question, but when the nixpkgs manual says All new projects should use the CUDA redistributables available in `cudaPackages` in place of `cudaPackages.cudatoolkit` does it mean that individual derivations from `cudaPackages.*` should be manually added to `buildInputs`/`nativeBuildInputs`. For example, would this mean that I should just manually add `cuda_nvcc` to `nativeBuildInputs`. What if the upstream package expects a single `CUDA_PATH` path containing all the cuda dependencies? I think, I saw some people using `buildEnv` to collect all of the required binaries/libraries under a single path, but I am not sure if this is the most elegant way to do this (also, it's not immediately clear, how would a single `CUDA_PATH` interact with cross compilation).	16:54:19
ruro	* This might be a stupid question, but when the nixpkgs manual says All new projects should use the CUDA redistributables available in `cudaPackages` in place of `cudaPackages.cudatoolkit` does it mean that individual derivations from `cudaPackages.*` should be manually added to `buildInputs`/`nativeBuildInputs`. For example, would this mean that I should just manually add `cuda_nvcc` to `nativeBuildInputs`? What if the upstream package expects a single `CUDA_PATH` path containing all the cuda dependencies? I think, I saw some people using `buildEnv` to collect all of the required binaries/libraries under a single path, but I am not sure if this is the most elegant way to do this (also, it's not immediately clear, how would a single `CUDA_PATH` interact with cross compilation).	16:54:58
SomeoneSerge (back on matrix)	Honestly, I've no idea what license, if any, applies to torch-bin	17:24:28
SomeoneSerge (back on matrix)	Yes, or we could just agree that testing for insecure dependencies is out of scope for hydra	17:26:09
SomeoneSerge (back on matrix)	I expect static and devrt to be in .dev's propagatedBuildInputs	17:27:54
SomeoneSerge (back on matrix)	What if the upstream package expects a single CUDA_PATH path containing all the cuda dependencies? I think, I saw some people using buildEnv to collect all of the required If upstream is co-operative, they need to be contacted and offered a proper solution like FindCUDAToolkit.cmake without any CUDA_PATHs or merged-layout assumptiosn	17:29:22
zopieux	thanks for looking. Sadly, I have now compiled the package myself so it's cached and this doesn't say anything useful. I suppose I can try next time I update. What do you except out of emptying `builders`?	17:29:50

Show newer messages

Back to Room ListRoom Version: 9