today in "why do I keep putting up with musl" I can't use Sublime because it's glibc only I can't use Atom because it depends on minidump which depends on Google's breakpad, which isn't theoretically glibc only but is effectively glibc only
Chromium also uses breakpad do surely there's either a patch to fix it or an easy way to disable it, no?
-
-
my googling suggests that a simple
#define _GNU_SOURCE would do it, which I'd do on the command line if the command line wasn't obfuscated by npm hell I'd change the source myself, but... it's nowhere to be found, again obfuscated by npm -
And that is why you keep putting up with musl: because you know musl isn't the problem, but *other software* doing effective vendor lock-in for glibc via obfuscation and general ignorance is.
-
that's actually one of the reasons I'm glad I found musl/Void Linux early in the stages of my current project; makes it easier to ensure it's compatible with musl (said project is also for a boot CD I want to be able to load to RAM; musl and Void are both pretty good for that!)
-
Yes! There are now at least 4 distros using musl (Sabotage, Void, Alpine, and Adélie). As more software is ported to them, glibcisms also get fixed upstream. This is great dynamics
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.