mochaa

if you really want a single elf that could link to system libraries with a foreign libc (you shouldn't), the somehow correct-ish way to do it is map your preferred ldso manually , setup stack, call DT_ENTRY etc etc like how kernel does it, and just yank the libdl symbols.

see cosmo_dlopen for an example implementation.

We already have language-specific files to define those keys, such as `package.json`, `pyproject.toml`, `Cargo.toml`, `deno.json` (and many more).

I don't see why you shouldn't integrate it into your project configuration instead of pretending that _'this is fine'_ and hiding all of it in a directory.

also: <https://xkcd.com/927>