Solo – a .so loader for static Linux binaries

If you dynamically sold an SO are you still static even if you did it "custom" ? At that point it's a dynamic loader in another name?

How this differs (is better!) from prior art - https://github.com/pg83/solo#how-this-differs-from-prior-wor...

I don't know much about musl.

> GPU: Vulkan and OpenGL drivers are supplied by the host as shared objects, usually built against glibc, and a fully static musl binary cannot normally dlopen() them.

Why? Have people managed to break the ancient concept of shared libraries, and this is a fix for that?

It is a testament to the complete failure of the GNU/Linux userland that something like this seems at all attractive to spend time on (or, it seems, LLM tokens).

Actually, scratch that, because Windows and macOS have historically struggled with ABI compatibility as well (macOS less so, due to not caring about backward compatibility in the first place).

How did we get to the point where people feel they need to go to the length of embedding an ELF loader in their binary (!!) rather than just linking with glibc?

Why not just pass the GPU to a docker container?

> backed by its own ELF loader (x86-64 and aarch64) and a glibc ABI bridge

Yacks

So not completely static, since it must link against a libc :P

How are we supposed to take this stuff seriously if the author (sic) isn't even willing to write the readme? Claude exists! If I want some slop I can push the button myself.