<mark_weaver>here's what I do: after I've installed guix on top of another distro, then I set up my environment variables so that I'm only using things from guix itself, and then I recompile guix from clean using that environment.
<davexunit>the new binary tarball will save you a step :)
<taylanub>'which guix' points to ~/.guix-profile/bin/guix which has the shebang of a guile 2.0.11 in /gnu/store. 'which guile' also points to ~/.guix-profile, where it further points to the same guile 2.0.11 in the store. if I launch that guile and enter ",use (gnutls)" it can't find it.
<phant0mas>civodul: when crossbuilding bison-2.7 with target=i686-pc-gnu, m4 can't be found in PATH
<phant0mas>I added it as a native input, but shouldn't the already added propagated-input be enough?
<mark_weaver>taylanub: do you have gnutls in your profile? does GUILE_LOAD_PATH include $HOME/.guix-profile/share/guile/site/2.0 ?
<civodul>it's getting slightly less bad according to loadavg
<mark_weaver>I think it must be at least 30 minutes since hydra-evaluator printed the message "created cached eval 104182", and yet I still don't see it on the web interface. maybe the message should be "creating ..."
<taylanub>my guile load path has ~/.guix-profile/share/guile/site/2.0, but there seems to be no gnutls there. I thought its presence would be ensured by the guix package somehow, since its needed for 'guix download'...
<taylanub>maybe the guix package should propagate gnutls?
<civodul>taylanub: yes, it should (it's not even an input currently)
<civodul>OTOH, that would make the binary tarball bigger