IRC channel logs
2025-01-31.log
back to list of logs
<ludocode>Has anyone bootstrapped re2c without generated files? It uses itself to generate its lexer and bison to generate its parsers. It's used in tools like ninja and cmark <plasma41>This 1993 paper on re2c may prove useful to anyone attempting to write bootstrapping code for re2c from scratch. <lanodan>Although I feel like this one could be replaced with a hand-written version <aggi>ninja utility got a drop-in replacement implemented in ANSI C, that's samurai <lanodan>Anyway, tried to see how far I could get but old C++ made me give up and then later versions like 0.14 is a bit more complex and requires autotools which probably ought to be tossed out <aggi>the development baseline to built upon implies a no-c++ profile fully supported with alternative toolchain, including required development utilties to bootstrap any further _optional_ c++ dependency <aggi>so far, i got linux2.4 back on board, sanitized musl-libc for linux2 ABI, and a _complete_ @system package set containing all required development utilities <aggi>musl-libc patches reside inside an uncommitted git-workspace still, besides a complete fork of a gentoo hotfix-overlay for tinycc/static-linking support <aggi>i've had a phone interview just today, with some job placement coaches, explaining some labor market compliant contracting was necessary asap <matrix_bridge><Andrius Štikonas> and ninja is quite common tool... So hard to avoid re2c <lanodan>ninja can be replaced by samurai at least <stikonas>lanodan: for you own builds yes, but I guess it's harder to avoid hardcoded dependencies in distro packages <stikonas>on Gentoo it seems that you can use alternatives mechanism <lanodan>Yeah works fine on gentoo and Alpine (which I also use) has been defaulting to samurai as well. <stikonas>maybe worth switching in your instructions too? <jackdk>also note: muon is a c99 pseudo-replacement for meson