<nefix>But 1- it keeps asking for the "cc" program and 2- it doesn't seem to be picking up the builtin libraries `zig cc -E -Wp,-v -xc /dev/null` points to `/gnu/store/lscf3a52z0773pr8g15l1z15vrgq1wbl-zig-0.8.0/lib/clang/12.0.0/include`, but it should also have `/gnu/store/lscf3a52z0773pr8g15l1z15vrgq1wbl-zig-0.8.0/lib/zig/libcxx/include/` for example
<nefix>(keep in mind that I think I'm missing out a lot of things)
<GNUtoo>Noisytoot: There are several options: you could try to bugreport or you could try to fix it
<monego>civodul: saw the pytorch patches, i was also working on them, could help review if i saw a series in the list
<monego>there is one missing dependency though, which is onnx (the C++ library), we only have one package which is the python interface with the c++ library bundled
<monego>and it's been a nightmare trying to separate the two
<LevyElara[m]>nefix: do you have any code I can test with? I was able to compile the short snippet above to mips without issues using the bundled musl via `-target mips-linux-musl` https://0x0.st/-W0V.txt
<char>can someone help me understand input vs propgated input?
<char>When installing common lisp packages, the inputs are needed at build time and run time, but they are only available during build time unless manually installed. Should they actually be propgated inputs?
<leoprikler>What kind of bash scripts are you thinking about? You can still bash script normally on Guix System if that's a concern.
<boeg>its not, its that i have been bash scripting on guix system, but i'd like to try and use guile instead and was seeking a starter
<boeg>for example i have a bash script for connecting and disconnecting my bluetooth headphones, for running backups and so on. A resource showing what parts of guile one might use for "commanding the guix system"
<leoprikler>Hmm, `info '(guile)Guile Scripting'` is a start for general purpose stuff.
<vivien>civodul, it’s not very exhaustive (that’s just because the project is a binding for gcrypt, so it’s expected for its manual to only cover the scheme part), and I don’t know what form a "guile" sexp takes to be converted to a "canonical" sexp. The best help for me would be if it had further examples about sexps vs canonical sexps, how to access the RSA and ECC parameters, how to sign and verify signatures, and have the
<vivien>list of function with their arguments for generating random numbers, and encoding and decoding with base64 (I just need the base64url variant without padding). The hashes seem clear to me.
<civodul>vivien: yeah, these parts of the manual are missing quite a few bits
<civodul>well, we should fix it, and then we have a good reason to make another release :-)
<vivien>I have to say, I’ve had trouble with nettle to manage callbacks in a way that does not make guile crash, and I’m really not happy to have to ship more C code (plus, what if one day you rewrite the garbage collector lol) so that would be one more reason.
<vivien>Anyway, first I want to get the name changed because webid-oidc is a stupid name and since the authentication protocol switched to Solid-OIDC it’s not even relevant anymore
<leoprikler>I think we can push those packages over to minetest.scm once they reach a certain size
<leoprikler>I wouldn't create a minetest.scm file for two or three mods, though
<vivien>Do you have an example of how to use (guix docker) build-docker-image to create a docker image with hello in it? I don’t understand what the "paths" and "prefix" arguments are about. Should I put a list of packages in "path"? If so, what is "prefix"?
<civodul>vivien: you can look at how (guix scripts pack) uses it, but note that (guix docker) is semi-private (or semi-public?)
<civodul>cbaines: right! i lost track of it, lemme see
<PurpleSym>rekado_: I looked at that article wrt PYTHONPATH again and implemented a simple finder, which works similar to how NPM packages work (i.e. subdirectory in package dir, which has links to dependencies). The simple PoC works, but it’d have to show it works with Guix too.
<roptat>that sounds like maybe a plugin is blocking this? I see these CORS policy errors when using umatrix in icecat for instance
<roptat>or an issue with the headers of kiwiirc.com
<rovanion>roptat: Figured it out. I exited my .bashrc before setting the path if it was a noninteractive session. Thanks for the clues!
<thorwil>hi! i had to set up a new ubuntu installation and decided to use the apt-get packaged guix. after `guix pull` i started to wonder: are there differences from the script-driven or manual installation in ongoing use?
<thorwil>the first oddity is that this guix doesn’t know audacious and libreoffice
<thorwil>then even after explicit `guix install inkscape` (normally, I use a manifest), `which inkscape` is "".
<dstolfa>thorwil: while guix can be packaged, it's probably not something that should be updated by the distribution and left alone, however from the issues you're describing i think it's clear that it's not been packaged correctly
<maximed>I think the idea is that you do "sudo apt-get install guix" for an initial guix version to start with (and to run the guix daemon) and then do "guix pull" like on Guix System to get up-to-date packages
<thorwil>i was pleased how fast guix-install.sh works, but now i have to note that things still don’t end up in my path!
<thorwil>i though it would take care of all the linking and environment variables?
<dstolfa>NicholasvonKlitz: try using #:cargo-development-inputs, maybe that works (see examples in gnu/packages/crates-io.scm)
<NicholasvonKlitz>dstolfa: Thanks. Actually turns out the initial error I was describing results from the monorepo housing the two crates having set `resolver = 2`. I need to patch the Cargo.toml before build to override the resolver version. Afterwards I'll see if guix gives any errors for circular dependencies