| 24 Nov 2022 |
 tpw_rules | no, nixGL is only necessary to link up with the hardware graphics drivers | 05:07:26 |
 pie_ | Hm. I didnt hink through how I'm going to deal with UnityPlayer.so requiring glibc 2.14 or 2.15 | 05:27:18 |
| pie_ | * Hm. I didnt think through how I'm going to deal with UnityPlayer.so requiring glibc 2.14 or 2.15 | 05:27:26 |
| pie_ | though technically I think thats old enough to run? | 05:27:37 |
| pie_ | I might have done a lot more work than needed for this binary at least | 05:28:14 |
| pie_ | it might not be trivial to build against an old glibc though | 05:50:48 |
| pie_ | https://discourse.nixos.org/t/compiling-with-old-glibc/12054/4 | 05:51:02 |
| 18 Dec 2022 |
 Madoura | So apparently mainline clang can compile and link HIP executables just fine without hipcc.
It still makes sense to follow the official ROCm software stack for nixpkgs, but dang. This would have been a lot easier to just use regular clang. | 15:48:46 |
| pie_ | heh | 15:49:57 |
| pie_ | I still want to work on it but I haven't gotten my little project working yet. Also exams. | 15:50:23 |
| Madoura | Ah I get it.
I've had a lot of free time lately so I've been spending it (without sleeping...) working on porting ROCm to nixpkgs lol.
Theoretically since we have rocmClangStdenv now switching away from hipcc if/when it's needed should be easy for all the ROCm packages. | 15:51:35 |
| 20 Dec 2022 |
|  Pascal joined the room. | 00:24:20 |
| 24 Dec 2022 |
| Madoura | We have torch now. https://github.com/Madouura/nixpkgs/commit/df71e711026a37178f9a258f236db0e1a66e2f0b | 14:36:29 |
| 29 Dec 2022 |
|  @luizirber:matrix.org joined the room. | 19:48:22 |
| 21 Feb 2023 |
|  John ✒️ joined the room. | 10:48:27 |
| 28 Feb 2023 |
|  Ido Samuelson joined the room. | 05:43:18 |
| 14 Mar 2023 |
|  pbsds joined the room. | 13:15:12 |
| 24 Mar 2023 |
|  htran joined the room. | 02:20:37 |
| 25 Mar 2023 |
|  @valconius:matrix.org joined the room. | 23:44:55 |
|  rbutani joined the room. | 23:55:19 |
| 27 Mar 2023 |
|  Ryan Swart joined the room. | 09:41:42 |
| 29 Mar 2023 |
|  SomeoneSerge (nix.camp) joined the room. | 19:39:45 |
| SomeoneSerge (nix.camp) | Hi! Just wanted to mention that torchWithRocm is going to require allowUnfree = true when https://github.com/NixOS/nixpkgs/pull/222273 gets merged. I think this needs to be addressed upstream in openai/triton (they unconditionally download and vendor a copy of ptxas from cuda), but I haven't the capacity to handle this now | 19:54:53 |
| 31 Mar 2023 |
| Ryan Swart | Kind of a meta question - I am trying to run static nix on an HPC cluster and am running into some roadblocks (with a custom path and disabling the sandbox as much as possible I am still running into permission denied errors - can't chroot or run bubblewrap); given that I have the ability to run arbitrary binaries - is there a way to disable all "special" path modification etc in such a way that common HPC access limitations can allow nix to still build derivations? | 02:28:46 |
| Ryan Swart | I have looked into both static-nix and nix-portable, but neither seem to be a drop-in solution for my case | 02:29:36 |
| 2 Apr 2023 |
| John ✒️ | ryantalo: have you tried something like this? https://www.jboy.space/blog/nix-on-hpc.html | 11:56:18 |
| 1 Apr 2023 |
| SomeoneSerge (nix.camp) | Anyone tried running running Nix from Singularity and binding /nix/store? The cluster at my uni won't enable user namespaces, so no unchroot and no bubblewrap for me | 23:44:29 |
| SomeoneSerge (nix.camp) | singularity run --bind /abc:/efg something.sif works, but I want to use singularity-tools.buildImage and that puts e.g. the shell into /nix/store, which then is hidden by the --bind =' | 23:45:35 |
| SomeoneSerge (nix.camp) | And singularity run --overlay is, again, disabled on the cluster xD | 23:45:55 |
| SomeoneSerge (nix.camp) | In reply to @ryantalo:matrix.org
Kind of a meta question - I am trying to run static nix on an HPC cluster and am running into some roadblocks (with a custom path and disabling the sandbox as much as possible I am still running into permission denied errors - can't chroot or run bubblewrap); given that I have the ability to run arbitrary binaries - is there a way to disable all "special" path modification etc in such a way that common HPC access limitations can allow nix to still build derivations?
disable all "special" path modification etc
Hi, which path modifications are you referring to?
| 23:46:27 |
