<phant0mas>could it be that the previous error was because of using the wrong libpthread version?
<phant0mas>and I spent so much time searching the source of a non existent problem...I am gonna start knocking my head to the wall :P
<phant0mas>ok I will solve the libihash issue, and move full speed to finish packaging it
<bavier>well, I'm pretty sure I've got this lapack rpath issue figured out, but I've unfortunately got the mods mixed in with several other packages that I was working on in maths.scm, so I have to sort those out before I can push anything
<lliI1>civodul: how does 'guix build' "add" a tarball to the store? it seems it uses 'build-derivations', but I'm not entirely sure.
<civodul>lliI1: right, tarball downloads are normal derivations, so building them actually downloads the tarball and adds it to the store
<lliI1>but how does 'guix build' distinguish between simply adding a tarball to the store versus using the build system?
<lliI1>For instance, I'd like to prefetch wget. I could get a corresponding derivation like so: ,use (guix packages) (gnu packages wget) (guix store) (define s (open-connection)) (package-derivation s wget). What should I do to add the tarball to the store?
<lliI1>As I said, it's not clear how 'guix build' knows when it have to return the location of a tarball instead of building a derivation.
<lliI1>(Perhaps the use of "build" in the forementioned is ambiguous.)
<civodul>lliI1: you'd have to use the 'package-source-derivation' procedure
<civodul>yes, the "source derivation" is the derivation that builds the tarball
<civodul>in practice it's not necessarily a tarball, hence the distinction
<lliI1>civodul: Sorry, I still don't understand how to get a '.tar.gz' file instead of '.drv'. (for-each (lambda (x) (display (derivation-input-path x)) (newline)) (derivation-inputs (package-derivation s wget))) prints a list of '.drv' files. I tried to pass one of the '.drv' locations to 'package-source-derivation' but got the same location back.
<civodul>a .drv is a low-level representation of the build process
<civodul>there's one for everything that is "built", including tarballs
<civodul>at the command line, you can use "guix build -S foo" to get foo's tarball
<lliI1>Yes, but I'd like to know how to do it from the REPL.
<civodul>at the API level, you can use (build-derivations s (list (package-source-derivation s foo)))
<davexunit>civodul: I was trying to package sudo recently and having some troubles, and mark told me about issues with setuid in guix. what are your thoughts on getting tools like sudo working on guix?
<lliI1>civodul: You imply that (build-derivations s (list (package-source-derivation s foo))) corresponds to 'guix build -S foo', but the latter returns the location of a tarball while the former returns a boolean. How can I get the location?
<lliI1>civodul: I've tried 'derivation->output-path' on a bunch of packages, I always get something like "/gnu/store/<hash>-package-name-version". I want to see the same but with something like ".tar.gz".
<civodul>lliI1: try (package-source-derivation s foo)
<lli1I>civodul: There's a neat function that I could use, that is, 'derivation-prerequisites-to-build'. However, its result contains both .drv derivation-inputs and .tar.xz.drv ones. Is it possible to filter out the former?