<sir123>Hello, here t otry and resolve my Guix build problems and get some work done on here :) I downloaded the guix git source and am trying to build it, but I've got some issues. First: configure.ac:18: error: required file 'build-aux/config.rpath' not found
<sir123>And: config-daemon.ac:12: error: required file 'nix/config.h.in' not found
<mark_weaver>you have to hit TAB on those section headings to make them expand.
<sir123>Forgive my ignorance. I know I've asked a lot of stupid questions on this IRC
<mark_weaver>I don't think you've asked stupid questions. don't worry about it :)
<sir123>Btw, does anyone know if 32 bit packages are on the radar? Maybe I could be of use there
<mark_weaver>we already have a full 32-bit i686 system. my primary system is 32-bit.
<sir123>I meant cross-platform. I need some 32 bit packages to build in my 64-bit
<mark_weaver>just pass --system=i686-linux to any command that builds packages.
<mark_weaver>it is trivial for us to support this, because of the fact that everything lives in individual directories in /gnu/store with a hash. this design supports having many variants of the dynamic linker, shared libraries, compilers, core utilities, everything. so there's nothing special to do to also install a 32-bit system alongside a 64-bit one.
<sir123>I don't understand. So I rebuild the package using guix build, but pass --system=i686-linux to it? How do other packages know to go to the 32 bit instead of the 64-bit version?
<mark_weaver>you don't need a GNU email address, any email address will do. however, you need to subscribe to the list or else your posts will have to wait for moderation before they go through (a necessary measure to prevent huge amounts of spam coming through)
<mark_weaver>toothbrush0, bavier`: actually, it should go *after* unpack instead of before configure.
<mark_weaver>I was looking for an example that does it properly, but almost all of them get it wrong.
<mark_weaver>the problem is that there are some other phases that need to fix things up in the configure script before it is run, and if you add the new phase before configure, those phases can't do their jobs.
<bavier`>mark_weaver: yes, I recall that coming up in discussion previously
<bavier`>I thought something seemed wrong when I looked at that package.
<mark_weaver>in practice, those phases are usually only needed on non-Intel platforms, so most people don't notice the breakage.
<mark_weaver>I guess I should do a bit commit to fix all of those places, especially since it is so common for people to look to existing recipes for examples of how to do things.
<toothbrush0>um, silly question though; is it normal that `./pre-inst-env guix package -I` gives a different list than i see in ~/.guix-profile/.. ?
<taylanub>toothbrush0: ~/.guix-profile does not directly list the packages you have, though I guess all packages showing up in -I should appear somewhere within it (as symlink targets). how exactly are you comparing the two?
<toothbrush0>well, notably `guix package -I` shows version X of my package, and .guix-profile/bin/.. points to version Z, where Z older than X
<civodul>toothbrush0: could it be that both X and Z are installed, but Z took precedence?