IRC channel logs

2016-05-22.log

back to list of logs

<emyles>How long should this take?: guix environment --ad-hoc python
<emyles>or even just: guix environment
<emyles>think im out of disk space.
<kyamashita>Is guix currently runnable using GNU/Hurd?
<roelj>Does guix system disk-image ... work?
<kyamashita>roelj: Though it /should/, I've yet to test it. Is it doing something funny?
<roelj>It kernel panics, after failing to copy a file because it runs out of disk space (but there is still 34G free!)
<kyamashita>roelj: Ooh, that's quite funny alright. Do other guix commands complain about not having enough disk space?
<roelj>kyamashita: No, I've run the same operating-system configuration as a VM.
<kyamashita>roelj: I wouldn't know where to start looking in this case...
<kyamashita>roelj: Guix does this in the VM, too?
<roelj>kyamashita: The VM works fine.
<roelj>I'll dig deeper then.. Thanks!
<kyamashita>roelj: Interesting. You're welcome. I may have to try this soon!
<roelj>Oh great: ERROR: In procedure copy-file: Success
<kyamashita>roelj: lol, my favorite type of error.
<roelj>This also happens when running 'guix system disk-image gnu/system/examples/bare-bones.tmpl'
***calher is now known as Emacsite
<roelj>So I finally got the usb image for 0.10 to work.. I hoped it'd work with UEFI, but that doesn't seem to be the case.
<roelj>Is there any work being done to boot GuixSD in UEFI mode?
<roelj>That would be awesome :D
<kyamashita>roelj: I'm not aware of any, though I might just be ignorant of any work being done.
<roelj>I'm not sure how much work it would be, but I am interested in taking a look at it.
<roelj>Probably a month from now though.. As I will be very busy
<kyamashita>roelj: That would be great if it could be done!
<kyamashita>s/could/would
<koosha>phant0mas: Hi , I executed Debian/hurd on Qemu . Now I want to install Guix . Do you suggest to do that with binary or source ?
<jmd>koosha: Do you want to install GuixSD (the operating system) or Guix (the package manager) ?
<koosha>Guix
<jmd>Then I recommend from source.
<efraim>I don't know that the i686 binary will work on Hurd
<janneke>indeed, I don't think there are any binaries for Guix/GuixSD for hurd yet
<efraim>from the source there's i686-linux and separate i686/i586-gnu conditionals
<jmd>How does https://www.gnu.org/software/guix/packages/ decide which packages are GNU and which are not?
<efraim>I think all are eligible to build, it comes into effect more during the building the base system phases
<jmd>efraim: How would, for example, postgresql faire in building for Hurd?
<efraim>I don't believe there are any binary substitutes on Hurd so it'll have to build out to it
<efraim>The main difference should be that it substitutes hurd equivilants when otherwise it would use linux-headers
<jmd>But hurd doesn't have SysV shared memory, and Postgres depends heavily on it.
<efraim>oh, I have no idea then
<habs>Hi, how can I compile a 32-bit program on a 64-bit Guix installation? On debian I would install something like gcc-multilib, but what is the Guix equivalent? Currently I get the error "ld: cannot find -lgcc" if I try.
<jmd>habs: I'm not sure what you mean by a "32-bit program".
<jmd>All programs (almost all) can be as many bits as the host platform allows.
<habs>jmd: In this specific case I'm trying to compile wine as a 32-bit executable, but my system is x86_64. Here is the relevant portion of config.log that describes the problem I'm having: http://sprunge.us/djVB
<jmd>If you take the source of any program (for example GNU Hello) and build it on a i586 machine, the resulting binary is 32 bit. If you build it on Amd64, then it is 32 bit.
<jmd>Well, the last line is obvioisly pertinent: configure:5062: error: Cannot build a 32-bit program, you need to install 32-bit development libraries.
<jmd>But I would have to ask why are you wanting to do that?
<jmd>If you have a 64 bit system, then why not build as a 64 bit binary?
<efraim>you want gcc-toolchain and not just gcc
<efraim>if you have your package definition you can build it with --system i686-linux
<jmd>efraim: But I suspect what habs actually wants is to specify the wine _target_ as 32 bits. He probably doesn't wan't it hosted as 32 bits.
<efraim>ah
<habs>jmd: Thanks for the help all, I'm still trying to understnad the difference between build / host / target arches. I want to do it this way because it's the "default" way to compile wine, I think because wine works better in 32-bit mode than 64-bit?
<jmd>habs: Those kind of questions might be better answered in #wine
<jmd>But as I understand it, "target" means the type of binaries you want to run under wine.
<jmd>"host" means the platform on which you want to run wine.
<jmd>and "build" means the platform on which you are building wine.
<habs>jmd: Yes, I guess my question boils down to: Is there a way to install the i386 development libraries on an i586 system using the Guix package manager? Similar to the package "ia32-libs" on other distros
***kelsoo1 is now known as kelsoo
<koosha>I've installed Debian/hurd on vm and now I want to install Guix from source . On of the requirements is Guile with the version 2.0.7 or later but the newest version available in debian repositories is 2.0 .
<efraim>testing and sid have 2.0.11
<koosha>So when it says 2.0 , it means 2.0.11 ?
<efraim>you can run 'apt-cache policy guile-2.0' and it'll tell you what version is available
<koosha>Thank you .
<efraim>does anyone know how to load bournish? either straight out or from guile?
<iyzsong>use the module and then ',bournish'?
<jmd>guix lint gives me this error:
<jmd>guix/build/download.scm:280:17: In procedure tls-wrap:
<jmd>guix/build/download.scm:280:17: In procedure module-lookup: Unbound variable: make-session
<jmd>Is that normal?
<koosha>It seems that guix is not supported on i686 . Is it fine with X86_64 ?
<jmd>koosha: Guix is not "supported" on anything unless you made special arrangements for such a service.
<jmd>However I have successfully installed it on i686
<efraim>you need guile-gnutls
<koosha>efraim: I've installed that .
<efraim>hmm
<koosha>jmd: so what should I do ?
<jmd>koosha: As I recall, ./configure ; make; make install worked for me.
<jmd>koosha: But it would be worth looking at README first.
<koosha>jdm: Okay , let me put the exact Error ...
<koosha>jmd: The error is : "configure: error: 'i686-gnu0.6' is not a supported platform."
<efraim>iirc for hurd you need i586
<koosha>efraim: But jmd says that he could install it on i686 .
<efraim>there was a point a year ago where i686 caused bugs, but looking at the git history I see it's targeting i686 now
<efraim>that's configure from installing guix from source?
<efraim>koosha ^
<koosha>Yes
<efraim>I assume the 0.6 after gnu is the hurd version or something
<efraim>I would try adding '--with-system=i686-gnu'
<koosha>I have the 0.6 version
<jmd>koosha: I've neverheard of i686-gnu0.6
<koosha>Let put my "uname -a" output ...
<jmd>I have i586-linux-gnu
<koosha>"GNU debian 0.6 GNU-Mach 1.4+git20150409-486/Hurd-0.6 i686-AT386 GNU "
<phant0mas>hello
<jmd>Interesting.
<koosha>phant0mas: Hi :)
<phant0mas>first use guix from my repo
<jmd>koosha: I haven't played with Hurd for a long time.
<phant0mas>it has some patches not in upstream
<phant0mas>clone the source
<jmd>koosha: Do other simplepackages (like GNU Hello) build on your system?
<jmd>If so, what does config.status tell you?
<koosha>What architecture should I use in my vm ?
<phant0mas>koosha: inside the guix source run ./bootstrap && ./configure --with-courage && make
<phant0mas>the arch is i586-gnu
<phant0mas>for hurd
<koosha>And debian ?
<phant0mas>yes
<phant0mas>koosha: which sources are you using
<phant0mas>from where>
<phant0mas>?
<koosha>I have i686 . So first I should use i586
<koosha>phant0mas: guix sources ?
<phant0mas>koosha: I have lost you
<phant0mas>first do you have debian-hurd on qemu?
<efraim>your guix source with your patches
<koosha>Yes
<phant0mas>efraim: I am asking if he is useing wip-hurd from savannah or from my github
<phant0mas>koosha: ok
<phant0mas>which repo did you clone?
<phant0mas>koosha: clone wip-hurd from https://github.com/Phant0mas/Guix-on-Hurd
<koosha>I've got debian/hurd from here "http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd-20150424.img.tar.xz" and guix source from here "http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd-20150424.img.tar.xz" . But I was using i686 that is completely wrong , right ?
<phant0mas>inside the vm
<phant0mas>no it's not
<phant0mas>i686 vm is perfect
<phant0mas>the vm is okay
<phant0mas>inside the vm clone wip-hurd from https://github.com/Phant0mas/Guix-on-Hurd
<koosha>Okay
<phant0mas>koosha: did you clone it?
<koosha>phant0mas: I've just installed git , now I'm going to do that .
<phant0mas>ok
<phant0mas>koosha: I am going afk for a bit
<phant0mas>when you finish cloning run ./bootstrap && ./configure --with-courage && make
<phant0mas>there will be some dependencies missing, install them with apt
<phant0mas>guile-2.0-dev libsqlite3-dev libgcrypt20-dev will be some of them
<koosha>I finished cloning . I'm going to do them .
<koosha>phant0mas: When running bootstrap : "./bootstrap: 5: exec: autoreconf: not found"
<efraim>koosha: autoconf
<koosha>Thank you but another error :
<koosha>"configure.ac:68: error: possibly undefined macro: PKG_CHECK_MODULES
<koosha>IF this token and others are legitimate, please use m4_pattern_allow.
<koosha>See the Autoconf documentation.
<koosha>configure.ac:69: error: possibly undefiend macro: GUILE_MODULES_AVAILABLE
<koosha>autoreconf: /usr/bin/autoconf failed with exit status: 1 "
<koosha>That's all the error .
<efraim>maybe pkg-config
<emyles>hello, why does 'guix environment guile' not finish?
<efraim>you want an environment with guile or an environment with the packages used to build guile?
<efraim>is there a display or did it just stop?
<emyles>either, that was just to test
<emyles>says its going to build profile.drv, ca-certificate-bundle.drv, info-dir.drv
<emyles>downloads bash then just waits there
<emyles>ps aux | grep guix shows thre guix-daemons
<koosha>efraim: I've got this : "configure.ac:69: error: possibly undefiend macro: GUILE_MODULES_AVAILABLE
<koosha>IF this token and others are legitimate, please use m4_pattern_allow.
<koosha>See the Autoconf documentation.
<efraim>do you have guile-2.0-dev?
<koosha>autoreconf: /usr/bin/autoconf failed with exit status: 1 "
<emyles>guile-2.0.11
<koosha>Wierd . I remember that I downloaded it , but ... No it wasn't installed .
<efraim>does `apt-cache policy guile-2.0-dev' list it as installed?
<emyles> yes, pacman -Ss guile show it is installed, but the guix-daemon are using
<emyles>/gnu/store/x-guile-2.0.11/bin/guile (where x is a hashe)
<emyles>hash
<koosha>emyles: I think that was for me :)
<emyles>ha
<koosha>efraim: I installed it now .
<efraim>ok
<efraim>when I tried installing guile in guix on debian I kept on running into issues with my debian's guile, maybe that is connected to having issues with offloading to my other guix-on-debian box
<phant0mas>koosha: did you install guile and guile dev?
***pastaf is now known as Pastaf
<joshuaBPMan_>hello, I'm dual booting guix and parabala. In my config.scm file, I commented out the grub section, because arch already has grub installed. What is the best way to dual boot guix and parabala?
<kyamashita>Is there a guix package that pulls from multiple git repos?
<jmd>kyamashita: Not that I'm aware of. Do you know of such a program in any other system?
<jlicht>kyamashita: are you talking about submodules?
<kyamashita>jmd: android-tools requires it. I'm asking because I want to package android-tools for Guix.
<kyamashita>jlicht: Not quite. I'm thinking of something akin to what was done in the red-eclipse package, but for Git repos.
<janneke>thanks for your annotated sicp fixes civodul!
<civodul>janneke: yw! :-)
<roelj>How does GuixSD do the partition setup for a new install? Should I create the partitions seperately and create labels for them, so that the operating-system declaration can populate the partitions?
<civodul>roelj: GuixSD does nothing, it's up to you :-)
<civodul>see https://www.gnu.org/software/guix/manual/html_node/Preparing-for-Installation.html#Disk-Partitioning
<roelj>Right. I'm a bit lost on how I can then create a GuixSD install with separate /home and / partitions..
<civodul>just create them in "the usual way" using cfdisk or similar
<civodul>and then make sure to declare them in the 'operating-system' confi
<civodul>+g
<roelj>Should I mount the /home partition in /mnt/home then in the next step?
<civodul>no, /home doesn't need to be mounted during installation
<civodul>only the target root needs to be mounted
<roelj>Ok. What about a seperate /boot and /boot/efi?
<roelj>(I'm trying to figure out what is needed for EFI btw)
<roelj>Linux-libre seems to support UEFI. Grub too.
<civodul>i don't know, i think you'll have to tell us ;-)
<roelj>Right. I'll experiment further :)
<civodul>Steap: seen https://lists.gnu.org/archive/html/guix-devel/2016-05/msg00447.html ? :-)
<jlicht>Is there some cache of knowledge concerning native-search-paths? I can't seem to wrap my mind around the why and how of them, and for once, the manual is not helping me either
<roelj>My 'guix system disk-image ...' keeps ending up with a kernel panic.. Has anyone encountered this too?