@lanodan not really no, the issue is having a `NEEDED libc.so` at all. you can't really have a process that loads another one that then depends on libc.so (libGL and loading the graphics stack then also depends on like another 20 libraries and for some drivers even libLLVM, etc, just for posterity). the only way to have 'portably loaded .so plugins' that you can open anywhere from any executable (whether static or dynamic against glibc/musl/whatever) is when they don't depend on libc, and every random library people distribute would have the dependency

https://www.openwall.com/lists/musl/2022/01/18/5 is somewhat analogous, but there's probably even more stuff that doesn't work on top of this, and aside from the thought experiment all anyone can really do is say "it doesn't work, don't even try it"