00:59 <jaeger> I remember now, I was supposed to open an issue about the stage1 Makefile target, will do that now

01:09 <jaeger> Created issue 14

03:39 <jaeger> OK, finally had a little more time to work on it and I think I've got stage1 building, will make a pull request if it works properly

03:40 <jaeger> This does make me wonder, though, have you or sepen actually built a full bootstrap using crux-arm-release? Based on what I'm seeing here I don't see how it could work

03:44 <jaeger> I would expect stage1 to fail every time with errors from all executables linking against a nonexistent libcrypto.so.3 in the chroot

08:55 <pitillo> hey jaeger, don't worry, don't rush, there is no hurry

08:55 <pitillo> perfect that issue... let's see if sepen can take a look to it

08:56 <pitillo> I've been building from scratch and based on generic release (to jump directly to stage1) and I've see some problems with python3/openssl footprint mismatches, but no problem related to binaries linked to host's ssl

08:56 <pitillo> last problems we had were related to optimizations (gcc/glibc ASFLAGS)

08:59 <pitillo> the only problem I've noticed with stage1 is the fact of the rootfs-stage1 objective, which needs to be touched every time before launching again the build and the wrong prt-get.conf file pointing to /workspace/, so I need to remove that prefix to point to the real prt-get.conf file (it must be fixed reverting after going out the jail and using full path to point the right file)

17:44 <jaeger> I keep running into errors with every part of crux-arm-release

17:46 <jaeger> I get stage0 working... stage1 fails

17:46 <jaeger> I get stage1 working... bootstrap fails

17:49 <jaeger> Think I'll focus down to one thing at a time. First making sure stage0 works every time and is idempotent