<stikonas>actually, I can just test knight0-native in a vm... <stikonas>I haven't tested knight and armv7 though <stikonas>it probably works because instructions are coppied from ">" instruction <Hagfish>it lists reproducible builds as a goal, and signed releases <pabs3>time to get bootstrappable builds listed there? <Hagfish>but what would that mean in practice? <Hagfish>"there has to be a documented path from Guix to building the latest release of your software?" <pabs3>I'd go with the simpler: "tools used in build processes must be buildable without the tool being built yet" <pabs3>ie isolate the requirements to the individual package <Hagfish>there could still be cycles between packages, so i guess the definition of "tool" would have to be understood in a sensible way <pabs3>yeah, Debian has lots of cycles <oriansj>stikonas: what build problem exists with stage0? I have gcc (GCC) 11.2.0 locally. Can you provide an error message for me to dig into? <oriansj>make clean test is the standard build and test routine <oriansj>and I am doing the armv7l testing right now and the knight-posix testing shortly after ***jjardon_ is now known as jjardon