<remo3>I've searched the manual for a while now, but I can't find the answer to this question: why is it that when I run "guix package --list-installed", I only see a tiny number of packages (the ones I've installed after the initial system init)? Where are all the system resources?
<sprang>is there a todo/task list for Guix other than the bug database?
***jsgrant` is now known as joshuasgrant
<joshuasgrant>ACTION is attempting to update Racket from 6.1.1 to 6.2, and noticed that there is still no openssl made available to it in the package build, which is needed for "raco pkg" to work.
<joshuasgrant>I'm not exactly what would be the best way to make the system see that openssl is installed with it, via the build. It wouldn't be a build input I know.
<rekado->joshuasgrant: if it needs openssl it should be added as an input.
<joshuasgrant>rekado-: Ah, I'm starting to recall now; Was I mixing up inputs with build-inputs?
<joshuasgrant>ACTION needs to spend a fair amount of time over this weekend rereading some of this documentation; It's been a number of months since I've even really touched Guix. :^P
<joshuasgrant>I just added (gnu packages tls) to scheme.scm, and trying to do a './pre-inst-env guix build racket' it's popping out the message "WARNING: (gnu packages scheme): `openssl' imported from both (guix licenses) and (gnu packages tls)". I then removed the tls package line and it said it was invalid to use licenses' openssl basically.
<joshuasgrant>It's currently building, with that double import. Is that okay ... or?
<joshuasgrant>I might just leave it run to build, and go afk for a bit. This is my really low-end laptop, so it's going to take sometime anyways. I just want to make sure this is the actual reason 'raco pkg' isn't working and do it up proper later today or tomorrow on my main rig.
<joshuasgrant>Yeah, I'm going to go that route and stop chan-spamming by thinking out loud in here. Thanks rekado- for the help; BBL. o/
<joshuasgrant>Sorry, I probably shouldn't even be attempting this atm ... burning the midnight oil and all that.
<taylanub>IIRC there was some talk of renaming all license variables to 'license-foo' at the place they're exported, so one doesn't frequently need to mess with this, dunno if/when it will be done
<joshuasgrant>taylanub: That seems like a pretty good solution actually, if this renaming method is currently used fairly often. But yeah, so long as it currently works I'll be happy either way. :^)
<joshuasgrant>I guess one could also do (guix legal) then 'license-whatever, that helps avoid that ugly double line of (license license-whatever) to (legal license-whatever). But that's just uneducated/knowledable sleep-deprived spitballing at this point.
<joshuasgrant>Well I'm getting an error, but I'm going to tell it to bugger off for the time being and take a nap or something and finish hopefully finish it off rested. Thanks rekado- & taylanub you were a lot of help! :^)
<codemac>Question for packagers here. I've been getting golang packaged in guix - and I'm running into an issue: 'go: error while loading shared libraries: libgcc_s.so.1' during the build stage of the package. Any help on how to set up shared libraries? This is my first package not using gnu-build-system :)
<davexunit>codemac: hmm, I don't know what go's build system looks like. so, it's failing during linking?
<davexunit>paroneayea, paron_remote: congrats on your award!
<codemac>davexunit: it's a totally custom build environment. I've gotten the 'go' binary to get fully built, but when it then goes to run 'go' on later .go files, it fails with not being able to link against libgcc_s.so.1
<davexunit>codemac: you should post the code you save so far to paste.lisp.org
<codemac>It's a very shitty pile of crap while I get it working, so I apologize for the bruteness of it.
<codemac>LD_LIBRARY_PATH being set though means that somehow the right paths aren't being embedded in the go binary? It seems only the glibc one is propagating, but I don't know how ld-linux really works
<codemac>yeah - it looks like the 6c/6l/6g compiler suite uses this ld-linux.so with it's elf implementation. Not sure how to embed multiple directories to load from into the go binary itself :/
<codemac>hm i'm really lost on how to embed library paths correctly with golang :/ because the ld-linux-blah in glibc doesn't know about libgcc_s.so, I'm not sure how to fix it without forcing ld_library_path env variables which won't work
<codemac>I've been looking at the nix package for inspiration, but I can't figure it out