Paulo Ferreira de Castro

> What if instead of using the temporary directory, we used the cache directory? You mean, _always_ using the cache directory and never the temporary directory? Interesting. Well, it might...

Is this related to what `pkg` calls V8 bytecode? - > https://www.npmjs.com/package/pkg > **Bytecode (reproducibility)** > By default, your source code is precompiled to v8 bytecode before being written to...

Thanks for looking into this issue @leafac 👍 I was able to reproduce the error with the `arm32v7/node:16` image you've suggested. Here are the "steps to reproduce", generating a trivial...

> I kept running into new issues. It turned into whack-a-mole. After whacking enough moles and waiting enough hours, :-) I can share some early, encouraging results. With very similar...

Other notes: * `make -j4`, instead of just `make`, specifies 4 compilation jobs in parallel, significantly reducing the overall compilation time if you have at least that many CPU cores....

> We could use `timeout` to compile as much as possible in ~5.8 hours and then pass the directory along to the next job and so on until it finishes....

> I haven't yet tested using the statically compiled Node.js versions with `caxa`, but the results above are encouraging. :-) Quoting myself, I often say, _"if it's not tested, it's...

A new chapter in this saga. @maxb2 managed to fix the openssl issue on ARMv7 (maxb2/static-node-binaries#6), 🎉  and I went on to test it further. Caxa's code executes all right...

Nice ideas. 👍   Just adding / emphasising that there are still alternatives to be explored further: * In `./configure --fully-static --enable-static`, what exactly is "fully-static" doing? Could the configure script,...

> I believe we could just pack our own libatomic in the caxa binary. The script would then copy it to the right location if necessary. How distro-specific is `libatomic`,...