@neon would mean include / being aware of graphics drivers or things like that, huge binary uguu
@Technowix I suppose, bah
@neon libre api/processors arch when
@caseyp Well I could statically link with just musl (I think?), but I'm not sure how useful that would be if I'm dynamically linking to other stuff. I suppose the less dynamic linking the better, but I'd just really like to not dynamically link anything.
@caseyp That's good to hear, I won't give up now then 😄
@pea Last time I tried compiling a Rust program where I used glutin, which uses dlopen, it threw up an error about using dlopen, so I kinda assumed that musl doesn't support that.
@neon ... and get static libs of the whole X11 implementation ? Am I wrong?
@jsa I suppose yeah, I guess the question is more "is that legit?"
@neon re: "X11 seems really married to glibc" — it's most definitely not.
X11 the protocol itself does not care (nor does the overall "X window system") about what libraries you use.
libX11, aka Xlib, may care, but I don't think it does.
/usr/lib/libX11.so, your system's build of Xlib as a shared library linked against glibc, of course does. Precisely because it's your system's build of Xlib as a shared library linked against glibc.
@bugaevc Ah, good point.