alethkit

> Good luck! Fyi, things are buildable on Ubuntu 25.04, gcc 14, ocaml 4.11.1 as they are in the repo. It is, however, quite a tricky task! going to try...

Odd. stuck when building `contrib`: ``` configure: creating ./config.status config.status: creating Makefile config.status: creating liballocstool.pc config.status: creating config.mk config.status: creating config.h config.status: config.h is unchanged config.status: executing libtool commands config.status:...

Yes: x86 VM on Apple silicon. It's slightly confusing, because there are 3 zombie gcc processes that are listed as descendants of make, and 3 duplicates that are direct children...

Even curioser, the duplicates come back, even when the main processes in question have been killed.

Not sure which order is correct: 1 (readme): ``` ./autogen.sh && \ . contrib/env.sh && \ ./configure && \ ``` 2(circleci) ``` . contrib/env.sh ./autogen.sh ./configure ```

`/usr/bin/ld: cannot find -lallocstool: No such file or directory` hmm... I thought I did compile this. must have missed a step somewhere. will come back to this tomorrow, at which...

>About the missing lallocstool: this is due to an incorrect 'env.sh', build contrib again and hopefully it will fix it! So reproducibility does actually have benefits in practice!

``` /usr/bin/ld: cannot find -lallocstool: No such file or directory collect2: error: ld returned 1 exit status make: *** [Makefile:1307: tools/pervasive-types] Error 1 builder@liballocs-builder:~/liballocs$ ls /home/builder/liballocs/contrib/liballocstool/lib liballocstool.a Makefile builder@liballocs-builder:~/liballocs$ ls...

Contents of relevant `env.sh` files (including previous line for history context): ``` builder@liballocs-builder:~/liballocs$ ls /home/builder/liballocs/contrib/liballocstool/include allocmeta-defs.h allocsites-info.hpp frame-element.hpp stickyroot.hpp uniqtype-defs.h uniqtype.h uniqtypes.hpp builder@liballocs-builder:~/liballocs$ cat contrib/env.sh . /home/builder/liballocs/contrib/libsystrap/contrib/env.sh . /home/builder/liballocs/contrib/liballocstool/contrib/env.sh export...

This seems quite promising as a place to start!