<OriansJ>Based on previous input on the level of assumption made by my last attempt at lower level bootstrap binaries, I present a bootstrap that only requires basic 8086 system with IBM compatible BIOS
<grpala>I stumbled upon guix after reading some articles about nixos. Even though I've been using nixos for like a year, but I've only just barely managed to survive in it, haven't had the time to invest time in learning nix for real, though I have in my TODO list for when I do have the time. Anyway, it wouldn't hurt to ask how do you guys compare guix to nix (first thing that I noticed (and I liked) is the s-exp
<alezost>I guess you mean that "manually" doesn't mean "automatically". As for me the explanation is clear, but the patches to improve the documentation are always welcome :-)
<efraim>building out to hello on core-updates, testing out an update to isl and cloog
<efraim>hopefully with those updated we can also get aarch64-linux-gnu bootstrap-tarballs
<efraim>now that I've figured it out it seems obvious, but I updated isl to the version cloog bundles instead of testing every version out there
<OriansJ>janneke: well I don't know, since I have never written my own lisp before but it sounds like something fun I could also do
<janneke>OriansJ: I find it so fun and inspiring what you're doing that I'm looking into a minimal lisp interpreter now
<OriansJ>mark_weaver: Question, have you considered the possibility of a low level virtual machine in the bootstrap process. Since we would gain the ability of all hardware platforms to perform identical work and run the exact same binaries. Thus even if we didn't trust the bios or other low level functionality, we would still be able to compare its results with that produced by trusted hardware?
<efraim>/gnu/store/cj5jfwgvkpqf2kvcfnjjvzl9z8mjbzbv-hello-2.10/bin/hello: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, not stripped
<lfam>I'm not sure what's going on. Hopefully somebody with more knowledge than me will take a look.
<lfam>habs: Have you ever installed emacs? You could do something like `echo /gnu/store/*-emacs-* | tr ' ' '\\n'`, and then if there is some abortive emacs package, do `guix gc -d path/to/bad/package`. But first, I would submit a bug report to email@example.com.
<lfam>The system should be robust against this sort of failure
<lfam>Also, have you ever run `guix pull` since installing Guix?
<lfam>habs: I ask because there have been some changes to guix/ui.scm since 0.10.0 was released, and your problem seems to be in that code