Re: Progress on the Hurd; new state of wip-hurd-vm
Jan Nieuwenhuizen writes: > Like before, you should be able to run > > ./pre-inst-env guix build -f gnu/system/hurd.scm As reported by apteryx on IRC yesterday, this command may fail for you unless you have already built the bootstrap binaries for the Hurd. If you are new to the Hurd you must first build the bootstrap-binaries from the core-updates branch. The easiest to do that is by using the command above to build the VM. This should be fixed once we get the `guix' package to cross-builds without some of the hacks that are now used near the tip of the wip-hurd-vm branch. Greetings, janneke -- Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
Re: Progress on the Hurd; new state of wip-hurd-vm
Hello, On Mon, Apr 20, 2020 at 7:39 AM Jan Nieuwenhuizen wrote: > Yes, some of them (gnutls, git, python) have just been cleaned-up and > applied to core-updates. nice ! > > I'm looking at the first one (for perl) for example... > > Ah, that one took some review and effort, see https://bugs.gnu.org/40698 > and has now been applied too. Oh, funny, I stumbled upon perl-cross, just after having sent my email. > > So, what's the status of those patches ? > > Hard to tell! Some of those are ready, others need review, others need > work. > > The autotools patches need review, but they work. The patches to > cross-build guix need some discussion and worse, cross-compiling guix > currently uses a terrible kludge; so while also that "works", its still > under development. Thanks a lot for your work ! And also for the status update. -- Vincent Legoll
Re: Progress on the Hurd; new state of wip-hurd-vm
Vincent Legoll writes: Hello Vincent, > I just had a tour of that branch, it looks like there are interesting > patches wrt cross-building, aren't those ready for upstream (core- > updates maybe) ? Yes, some of them (gnutls, git, python) have just been cleaned-up and applied to core-updates. > I'm looking at the first one (for perl) for example... Ah, that one took some review and effort, see https://bugs.gnu.org/40698 and has now been applied too. > I've been trying to cross-compile the binary-tarball to new arches, > without any success, all failing the same way, on perl... > > And when it hit me that there is a recurring theme in those failures > I found a few issues and ML posts about the same problem. > > So, what's the status of those patches ? Hard to tell! Some of those are ready, others need review, others need work. The autotools patches need review, but they work. The patches to cross-build guix need some discussion and worse, cross-compiling guix currently uses a terrible kludge; so while also that "works", its still under development. Greetings, janneke -- Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
Re: Progress on the Hurd; new state of wip-hurd-vm
Hello, I just had a tour of that branch, it looks like there are interesting patches wrt cross-building, aren't those ready for upstream (core- updates maybe) ? I'm looking at the first one (for perl) for example... I've been trying to cross-compile the binary-tarball to new arches, without any success, all failing the same way, on perl... And when it hit me that there is a recurring theme in those failures I found a few issues and ML posts about the same problem. So, what's the status of those patches ? -- Vincent Legoll
Progress on the Hurd; new state of wip-hurd-vm
Hello, I just reset wip-hurd-vm to ba6bdb0d0b gnu: guix: Run `make update-guix-package'. Like before, you should be able to run ./pre-inst-env guix build -f gnu/system/hurd.scm on it to get a VM and start it doing something like guix environment --ad-hoc qemu -- qemu-system-i386 -enable-kvm \ -snapshot -hda $(./pre-inst-env guix build -f gnu/system/hurd.scm) -m 2G \ -device rtl8139,netdev=net0 -netdev user,id=net0,hostfwd=tcp:127.0.0.1:10022-: The VM now starts the Shepherd which starts the guix-daemon as well as an openssh daemon. root shares the system profile, which has been setup for minimalistic Guix development. You can build our first package ssh root@localhost -p 10022 guix build --no-offload -e '(@@ (gnu packages commencement) gnu-make-boot0)' and now also do that from git git clone gnu:guix cd guix ./bootstrap ./configure --localstatedir=/var --sysconfdir=/etc --with-courage make -j2 ./pre-inst-env guix build --no-offload -e '(@@ (gnu packages commencement) gnu-make-boot0)' Being able to build packages from git greatly reduces the round-trip time :-) The Shepherd integration needs more work. Also, the tip of that branch shows some troublesome commits that hack around cross-compiling guix to the Hurd. Greetings, janneke -- Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
