| 2 Sep 2022 |
 linj | Do you mean for file in $(find $out/{lib,bin} -type f); do? | 14:28:47 |
| 4 Sep 2022 |
 SomeoneSerge (back on matrix) | I'm not familiar with this bash syntax 🤣 But, FYI, I had a variation of this code meant to enumerate the outputs list: https://github.com/SomeoneSerge/nixpkgs/blob/c0fc4b2abc6322db67b4ad4aac1ddb8ddcccfc43/pkgs/development/compilers/cudatoolkit/auto-add-opengl-runpath-hook.sh
Shellcheck still won't like for ... in $(...) though
| 05:45:57 |
| SomeoneSerge (back on matrix) | (it keeps amazing me, frankly speaking, that we still write the imperative parts in bash) | 05:48:07 |
| SomeoneSerge (back on matrix) | Here's the original:
pkgs/os-specific/darwin/moltenvk/default.nix
156: for output in "''${!outputs[@]}"; do
| 05:51:31 |
 FRidh | In reply to @me:linj.tech
Do you mean for file in $(find $out/{lib,bin} -type f); do? these are all $outputs that may contain patchable objects | 09:45:59 |
| FRidh | probably better to check outputs | 09:46:58 |
| 13 Sep 2022 |
|  danielrf joined the room. | 21:37:24 |
| SomeoneSerge (back on matrix) | Offtop, but I imagine this kind of an issue could also arise with a cuda application, and I wonder if you here might be the right people to ask: there's a program that is built with the gcc10StdenvCompat. It links dynamically against gcc10's libstdc++. At runtime the program needs to use opengl libraries (from the same nixpkgs revision), some of which link against gcc11's libstdc++. This results in a failure
I simply don't know what is the right way to deploy something like this (or if there is one) and it's kind of making me sad.
https://github.com/NixOS/nixpkgs/issues/190984
| 21:49:29 |
| SomeoneSerge (back on matrix) | ...I'm not sure this could be built and run on any typical FHS distribution either (unless one actually uses a repo from X years ago where gcc10 is the default, and where both mesa and fluxus are in sync) | 21:52:10 |
| 14 Sep 2022 |
 hexa | preparing another python-updates run | 02:36:04 |
| 15 Sep 2022 |
|  m_algery joined the room. | 12:33:41 |
| m_algery left the room. | 12:33:43 |
| hexa | https://github.com/NixOS/nixpkgs/pull/191333 | 16:22:20 |
| SomeoneSerge (back on matrix) | In reply to @hexa:lossy.network
https://github.com/NixOS/nixpkgs/pull/191333 https://hercules-ci.com/github/SomeoneSerge/nixpkgs-unfree/jobs/1925 | 16:36:11 |
| hexa | fwiw: possibly a bit too early, given that we have a failing numpy build | 16:45:30 |
| hexa | numba pins setuptools<60 | 21:19:53 |
| hexa | i can't even. | 21:20:00 |
| hexa | we have been >60 for a while now | 21:20:08 |
| 16 Sep 2022 |
|  Suwon Park joined the room. | 17:28:32 |
| Suwon Park left the room. | 17:30:03 |
| Suwon Park joined the room. | 17:30:26 |
| Suwon Park | Hello everyone! | 17:33:48 |
| Suwon Park | Is there anyone who has tried building pytorch with cuda enabled? | 17:34:56 |
| Suwon Park | When I tried to build pytorch, this error occurs.
| 17:36:51 |
| Suwon Park | Redacted or Malformed Event | 17:36:59 |
| Suwon Park | * When I tried to build pytorch, this error occurs in the cmake phase.
-- Could NOT find CUDA (missing: CUDA_CUDART_LIBRARY) (found version "11.6")
| 17:37:25 |
| Suwon Park | So I looked up the source of pytorch in nixpkgs and there was no cudaPackages.cuda_cudart in buildInputs. | 17:38:18 |
| Suwon Park | cudaPackages.cuda_cudart seems to fix the error, but is there any reason why it is not there? | 17:39:17 |
| SomeoneSerge (back on matrix) | python3Packages.pytorch currently still uses the older cudaPackages.cudatoolkit expression, which ships a lot of stuff, including cuda_cudart | 17:39:58 |
| SomeoneSerge (back on matrix) | cuda_* expressions are preferred | 17:40:20 |
