<katco>so i'm trying to understand how guix does dynamic linking. i read somewhere it tweaks the rpath? i currently have a package that builds a binary, but it can't find libgcc... is there an example package i could look at to figure out how to point it to guix's libgcc correctly?
<efraim>katco: np :) I can never remember if its ,gcc "lib" or ,gcc:lib
<katco>efraim: i found out that gnu-build-system automatically passes in the gcc folder, so i was able to use that
<efraim>libgcc_s is in gcc.scm, which is what needs to be played with for go and gccgo to work
<efraim>I haven't managed to work my way through it yet
<robsyme>Hi all. I'm getting failures in the 'test' step when building ruby. Specifically, 'test_thread.rb' includes a step that spins up 5000 threads. My guix builder processes fail with "can't create Thread: Resource temporarily unavailable (ThreadError)". The output of `cat /proc/sys/kernel/threads-max` is 62692, which should be more than enough. Does anybody know if there is a limit on how many processes the guix-builder
<ngz>Hello. While writing a package, I noticed that unpack phase (from cmake, but I guess this one is inherited from gnu) leaves me in a subdirectory instead of the root directory of the source. Is it intentional?
<ngz>It seems dubious, because I have add a new phase right after 'unpack so as to (chdir "..").