https://bugzilla.redhat.com/show_bug.cgi?id=2098398
--- Comment #11 from Jason Vas Dias jason.vas.dias@gmail.com --- Here is what the build does :
../pil lib/llvm.l main.l -bye > base.ll mv base.map ../lib/map opt -O3 -opaque-pointers -o base.bc base.ll clang -O3 -w -fPIC -c -o lib.bc -D_OS='"Linux"' -D_CPU='"x86_64"' `pkg-config --cflags libffi` -emit-llvm lib.c llvm-link -o picolisp.bc base.bc lib.bc mkdir -p ../bin ../lib llc picolisp.bc -relocation-model=pic -o picolisp.s clang picolisp.s -o ../bin/picolisp -rdynamic -lc -lutil -lm -ldl -lreadline -lffi strip ../bin/picolisp
But ../bin/picolisp is referenced by ../pil, to produce 'base.ll' in the first step ;
I believe 'base.ll' left over from previous build and with earlier timestamp could also be shippped, then if this was a Bootstrap build, (no picolisp found), then that pre-generated base.ll could be used to produce a non-generated build of picolisp , skipping a most important build step for build customization, and expecting a Debian / Ubuntu libc. So ../bin/picolisp must exist, be the 32-bit simulator runner script, or be an SSH script that SSHes to an instance of Ubuntu running picolisp and which mounts the same build directory using NFS, eg. an Ubuntu VM, but 'picolisp' must be found in $PATH before building from generated base.ll will work.