The result of musl's attitude is build systems assuming "__linux__ && !__glibc__ means musl".
I pity the compatibility nightmares any new libc pushing for mass adoption will have to deal with. Musl's approach adds cost to everybody but themselves.
I pity the compatibility nightmares any new libc pushing for mass adoption will have to deal with. Musl's approach adds cost to everybody but themselves.
The `backtrace` call is a great example. It is available in glibc and uClibc, but not musl.
Instead of checking if using musl, and removing the backtrace call, the lack a musl define forces you to check for all the other possible libc's and assume musl is the default. This is dumb.