<kevinfish>mange: ok now it complains about no bootable devices. I hit esc to get the boot menu and then I hit 2. Unlike in the manual, it didn't require me to hit enter, it just took right off. I'm feeding it the *.xz file I downloaded (rather than uncompressing it first)
<kevinfish>I don't know how to copy that in a pastebin cuz once it scrolls off I don't know how to scroll it back and as soon as I click on it my mouse cursor disappears and the only way I can get back control again is to switch over to a text console and kill the qemu process
<mange>You have to uncompress it first. There are two patches in git to fix the docs for both of those issues (mentioning to decompress it, and changing 'default' to 'user'.
<kevinfish>mange: when do you think those patches will be applied to the website?
<mange>I have no idea how the docs are updated, so I don't know.
<kevinfish>mange: ahh, well that appears to have done it. Thanks!
<mange>No worries! Let us know if you run into any other issues.
<kevinfish>mange: actually, I have another. I found out my ethernet is the typical eth0. I tried ifconfig eth0 up and it just prints the little ifconfig report for that interface but still doesn't connect it to anything (e.g. ping 184.108.40.206 says network is unreachable).
<kevinfish>but 220.127.116.11 is reachable from my host machine
<skaria>ok, so this keeps happening. my guix profile borks, as in guix creates a .guix-profile-1-link which .guix-profile points to. and .guix-profile-1-link points to /gnu/store/blf1hy58v46n7gyfxakgzr58n7kxizkd-profile instead of /var/guix/profiles/per-user/luser/guix-profile
<skaria>what this does is fuck up the symlinking of the binaries in packages /gnu/store directory
<kevinfish>Ok, I'm trying to install to a VM according to the manual. I started by trying to configure the desktop with a 5G virtual drive and it tells me the disk is full, so then I went back and did a 10G with the barebones and it still says no space left on device. This is while it was trying to process binutils. I'm doing the 32 bit version. Any idea what could be wrong?
<kevinfish>on the 10G virtual drive I created two partitions, a 9.5G ext4 my-root and the rest as /dev/sda2 swap that's enabled.
<buenouanq>this seems to be a common issue with vm installs
<buenouanq>no idea how others have gotten around it though
<buenouanq>I recommend diving in head first and installing it on your real machine (-‿‿ - )
<kevinfish>buenouanq: Well, I was hoping to play with it a bit first to see if I wanted to.
<kevinfish>buenouanq: heard of anyone getting it running under VirtualBox?
<sneek>skaria, efraim says: in your package definition you need to add #:make-flags '("cc=gcc") or something like that
<sneek>skaria, alezost says: I guess you are not making a package, so I think efraim misunderstood your question. Anyway "make CC=gcc" will likely help. However, if all you need is a working EMMS package, you can simply install it with guix: "guix package -i emacs-emms".
<atw>If anyone's around, I would appreciate some feedback. I'm trying to package leiningen, a build tool for clojure projects. The recommended way to manually install leiningen is to use a script that will download a .jar (https://github.com/technomancy/leiningen/blob/stable/bin/lein#L65). This is also the recommended way to bootstrap: use an older version of leiningen to build the newer version
<atw>Anyway, I'm trying to do this right, so my plan is to make a leiningen-bootstrap package (based on an old version of leiningen) that will be built "manually", then using that to build a modern leiningen. Is this the right idea?