<civodul>of course that café wifi looked stable until i connected to IRC...
<mb[m]1>The TL;DR is that GCC 6 and later "monkey patches" `stdlib.h` from glibc and uses an "#include_next" macro to load the real thing, but the search logic fails to locate the "next" stdlib.h if C_INCLUDE_PATH is set.
<Steap>civodul: I puished a few updates last night
<ngz>Ah well. scribus > me. I have an almost working update, which builds, but fails miserably when calling the program with "ImportError: No module named _sysconfigdata_nd". Oddly, it complains about /usr/lib/python2.7/site.py. I don't even know where to investigate.
<civodul>if not, there might be a hard-coded /usr/lib that needs to be fixed
<Steap>ngz: maybe this module is missing from our Python install :/
<mb[m]1>Steap: FYI, watch out for source URI changes when using the Python updater, I had to change chardet to use 'pypi-uri' because the previous URL was 404. You probably didn't notice because the updater had already downloaded the tarball to your store.
<Steap>I can "import _sysconfigdata_nd" using Debian's python2, but not Guix's
<civodul>and then strace the whole thing to see whether it's accessing /usr/lib stuff
<ngz>IIUC, the command above is going to call scribus. Where can I sneak in the strace command then?
<ngz>Ah well, I cannot pre-inst-env guix environment... gnu/services/shepherd.scm:90:2: In procedure allocate-struct: Wrong type argument in position 2: 5
<ngz>I have the strace output in a regular pre-inst-env build (no guix environment command), if you're interested. I see it tries to open various Python locations, including in .guix-profile/ and /usr/lib ...
<rekado>if all goes really well today it will be back by the end of the day.
<rekado>ACTION tries to split up the patches from bug#26776
***fr33domlover1 is now known as fr33domlover
<aravind>hi, I am attempting my first local revision to guix - I need an updated version of python2-websocket-client and the all of my attempts to build it have failed. I did some digging around and it appears that the new requirements in that python module pull some stuff from the network in the test phase of the library.
<aravind>more digging around tells me that the guix build process essentially kills all network access during the build/test part - which explains why my attempts to build it are failing.
<ngz>Hello. Do you know how I can get a clean Guix repository again? From HEAD, when I run ./boostrap, I get "error: possibly undefined macro: GUILE_MODULE_AVAILABLE" and if I try ./configure, it stops with "line 7052: syntax error near unexpected token `2.2' `GUILE_PKG(2.2 2.0)'".
<ngz>Of course, I can delete everything and clone repository again, but I'd rather not lose my local branches.
<Guest67041>I just tried on Ubuntu and I get the same error, so apparently this is not GuixSD specific.
<nee`>Apteryx_: Guest67041: I don't know anything about qemu, but I have an old hurd.sh file that looks like this: qemu-system-i386 -m 512 -net nic,model=rtl8139 -net user -drive cache=writeback,index=0,media=disk,file="$DISK"
<mb[m]1>`guix pull` currently fails with "no code for module (guix build compile)"
<rama_dan>i saw a presentation about Guix where someone said there are plans for a "guix deploy" command, that seems like it would be quite delightful :P .. but how would deploying to "bare metal" work, for example?
<rama_dan>and does anyone know about a VPS provider that would support GuixSD? or are you all using some kind of custom images to run it?
<efraim>Some people take a base install of another distro and run guix system reconfigure on it