<efraim>I'm not sure about removing the search path from guix
***Dynom_ is now known as Guest9264
<efraim>with just the first one I don't have $GUIX_ENVIRONMENT/etc/profile sourced inside of 'guix shell'
<efraim>ok, with the first patch adding GUIX_EXTENSIONS_PATH to the generated profile and then installing my extension instead of just entering a guix shell, after 'bash -l' it shows up with 'guix help'
<Andronikos>I want to compile GNU Artanis locally but I get "In procedure dlopen: file "libnss3.so", message "libnss3.so: cannot open shared object file: No such file or directory"". Using "guix shell autoconf make guile pkg-config nspr nss". What do I do wrong?
<apteryx>patch the dlopen call locally, or set LD_LIBRARY_PATH
<nij_>Anyone tried guix in a VM running over a macbook m2?
<antipode>Downside of supporting more forms of tests is more test failures to resolve ...
<dominicm>Has anyone had issues with guix's libreoffice? I can't install extensions, use spellcheck, etc.
<rekado>dominicm: this sounds plausible. All packages in Guix are installed to /gnu/store, which is not writable. It’s possible that libreoffice attempts to install extensions to its prefix directory in /gnu/store.
<rekado>perhaps it can be patched to prefer a user-writable location (e.g. in ~/.local/share)
<dominicm>possibly yeah, that was my first thought but the error I got did not seem indicative of that. I'll try to look later.
<Andronikos>apteryx: Do you mean "LD_LIBRARY_PATH=$GUIX_ENVIRONMENT/lib/nss"? Don't understand what you mean with "artanis ..". Did try the first and it still does not find the lib.
***mark__ is now known as mjw
<PotentialUser-8>Hello. Are there any Schemers / Guixers in Strasbourg? I moved to that wonderful place recently and I look for more experienced people as mentor. I can offer beer (me) and Sushi / Kimchi (my wife)
<dlowe>I visited once. It's quite a beautiful city.
<apteryx>shcv[m]: hm, the pypy build failed with a different error now: bin/pypy3.debug: error: offset + size of segment 5 (type 1) exceeds total size
<davidl>efraim: reg. the bin output for #$this-package-input pcre (or some other package) - I think it's not possible. If you want the bin output you should have been able to use maybe: (inputs (list some-package `(,pcre "bin") some-other-package ))), but it doesn't work because I think the implementation is limited for the new format. I get issues with the hash when #$this-package-input pcre is used even though the inputs list appears to be accepted.
***hexology- is now known as hexology
<vldn>can i loop over a list and define functions with it?
<vldn>e.g run the define command in a recursive loop?
<antipode>sneek: later tell efraim: #$(gexp-input (this-package-...) "another-output")