Svante Signell writes: Hi Svante,
> I did build the bootstrap binaries some time ago. They were corrupt. Can you elaborate on that? Do you know which packages/programs were affected? Ah, wait you mean: > https://lists.gnu.org/archive/html/guix-devel/2019-09/msg00225.html I had to replace the following binaries in order to make ./pre-inst-env guix build -K -e '(@@ (gnu packages commencement) gnu-make- boot0))' work: bash, cat, cp, gawk, grep, install, mv, rm, rmdir, tar, xz, cpp, guile, mkdir, It seems these work for me. For now it seems that the binaries I'm building from core-updates are fine. > Down-grading from guile-2.2 to guile-2.0 did not improve the situation. Ah; yes I just found out as well :-) > Now I have a project to cross-build Hurd from a GNU/Linux box: hurd-cross, > using > the latest versions of the gnumach, hurd, glibc, gcc, etc. The built Hurd > boots > and runs fine in a VM :) The project will soon be available on Savannah. From > there I will again cross-build the bootstrap binaries for Hurd, in due time > though. (Other packages, like ones not yet available natively, can also be > cross-built. That's an interesting extension.) Okay, that's a whole different route but starting from a working situation can certainly help. I'm going to try the Guix route some bit more for now. > See > https://lists.gnu.org/archive/html/guix-devel/2019-08/msg00198.html > https://lists.gnu.org/archive/html/guix-devel/2019-09/msg00000.html > https://lists.gnu.org/archive/html/guix-devel/2019-09/msg00014.html > https://lists.gnu.org/archive/html/guix-devel/2019-09/msg00225.html > for some of the efforts to make Guix work on GNU/Hurd. Thanks for the pointers janneke -- Jan Nieuwenhuizen <jann...@gnu.org> | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
