23 May 2024 |
| lazycaaat joined the room. | 10:58:15 |
24 May 2024 |
| Charlotte ๐ฆ (it/its) changed their profile picture. | 06:54:08 |
| Rusty joined the room. | 10:59:15 |
29 May 2024 |
| raitobezarius changed their display name from raitobezarius to raitobezarius (DECT: 7248). | 17:07:26 |
30 May 2024 |
| cyanlight joined the room. | 10:26:35 |
2 Jun 2024 |
| aloisw set a profile picture. | 18:01:46 |
| aloisw changed their profile picture. | 18:23:55 |
4 Jun 2024 |
| raitobezarius changed their display name from raitobezarius (DECT: 7248) to raitobezarius. | 11:14:58 |
5 Jun 2024 |
| J7 left the room. | 13:46:35 |
11 Jun 2024 |
| IPK left the room. | 19:49:58 |
19 Jun 2024 |
maupind | Any academics using NixOS as a method for reproducibility of analysis? I'm interested to see what your processes are and curious if there are any funding opportunities that can be used to develop Nix in this area | 21:31:03 |
jbedo | In reply to @maupind:matrix.org Any academics using NixOS as a method for reproducibility of analysis? I'm interested to see what your processes are and curious if there are any funding opportunities that can be used to develop Nix in this area i use nix extensively for reproducibility, not so much nixos | 21:54:31 |
jbedo | i mean i run it, but not on institute/university compute | 21:55:08 |
21 Jun 2024 |
| Wilhelm joined the room. | 09:15:55 |
22 Jun 2024 |
| Charlotte ๐ฆ (it/its) left the room. | 19:23:12 |
28 Jun 2024 |
benoitdr | Anyone interested to work with me on a derivation for llama-cpp-python ? I had a working solution a few months ago but it's not working anymore with the latest package version. | 12:09:12 |
benoitdr | Currently facing this problem :
"fatal error: nv/target: No such file or directory" | 12:53:42 |
29 Jun 2024 |
| maka_77x joined the room. | 00:48:44 |
30 Jun 2024 |
Bruno Rodrigues | has one of you packaged positron ? | 13:07:15 |
Bruno Rodrigues | * has one of you packaged positron ? https://github.com/posit-dev/positron/tree/main?tab=readme-ov-file#positron-- | 13:07:40 |
benoitdr | I'm making some progress, now I can build llama-cpp-python with cuda, but unfortunately at runtime, the python app doesn't see the GPU ๐ญ these lines from llama.cpp derivation caught my attention :
# It's necessary to consistently use backendStdenv when building with CUDA support,
# otherwise we get libstdc++ errors downstream.
# cuda imposes an upper bound on the gcc version, e.g. the latest gcc compatible with cudaPackages_11 is gcc11
effectiveStdenv = if cudaSupport then cudaPackages.backendStdenv else stdenv;
....
effectiveStdenv.mkDerivation (finalAttrs: {
....
in my case I'm not making a derivation but I'm building a python package using pkgs.python311.pkgs.buildPythonPackage could it be the reason why gpu/cuda is not used at runtime ?
| 20:15:11 |
SomeoneSerge (UTC+3) |
not making a derivation b
buildPythonPackage is a wrapper around mkDerivation | 20:33:02 |
SomeoneSerge (UTC+3) |
python app doesn't see the GPU
Usually that means you need to add a DT_RUNPATH or LD_LIBRARY_PATH somewhere, pointing at ${addDriverRunpath.driverLink}/lib | 20:33:36 |
1 Jul 2024 |
| Philippe Olivier joined the room. | 13:27:47 |
benoitdr | In reply to @ss:someonex.net
python app doesn't see the GPU
Usually that means you need to add a DT_RUNPATH or LD_LIBRARY_PATH somewhere, pointing at ${addDriverRunpath.driverLink}/lib Could you please help me on the syntax ? The closest I can get is below and has no effect (in my shellHook) : ยดยดยด export LD_LIBRARY_PATH=${pkgs.lib.makeLibraryPath [ pkgs.addDriverRunpath.driverLink ]} export DT_RUNPATH=${pkgs.lib.makeLibraryPath [ pkgs.addDriverRunpath.driverLink ]} ยดยดยด | 13:30:16 |
benoitdr | In reply to @ss:someonex.net
python app doesn't see the GPU
Usually that means you need to add a DT_RUNPATH or LD_LIBRARY_PATH somewhere, pointing at ${addDriverRunpath.driverLink}/lib * Could you please help me on the syntax ? The closest I can get is below and has no effect (in my shellHook) :
export LD\_LIBRARY\_PATH=${pkgs.lib.makeLibraryPath \[
pkgs.addDriverRunpath.driverLink
\]}
export DT\_RUNPATH=${pkgs.lib.makeLibraryPath \[
pkgs.addDriverRunpath.driverLink
\]}
| 13:30:45 |
benoitdr | * Could you please help me on the syntax ? The closest I can get is below and has no effect (in my shellHook) :
export LD_LIBRARY_PATH=${pkgs.lib.makeLibraryPath [
pkgs.addDriverRunpath.driverLink
]}
export DT_RUNPATH=${pkgs.lib.makeLibraryPath [
pkgs.addDriverRunpath.driverLink
]}
| 13:31:36 |
SomeoneSerge (UTC+3) | DT_RUNPATH is not an environment variable, but the first export seems like it should work | 13:36:18 |
benoitdr | well it doesn't .. | 13:37:16 |
SomeoneSerge (UTC+3) | Well now it's a matter of finding out how exactly it doesn't work:) | 13:41:17 |