The more awareness musl gets, the better. See also Sabotage Linux, a musl-based distro: <a href="https://github.com/sabotage-linux/sabotage" rel="nofollow">https://github.com/sabotage-linux/sabotage</a>
I've been digging musl + clang too. Here's my wrapper script that I use to compile a number of projects: <a href="https://github.com/esjeon/musl-clang" rel="nofollow">https://github.com/esjeon/musl-clang</a><p>This isn't perfect, but kinda works (even with autoconf). I also tried to add musl support into LLVM/clang, but I've been too busy recently, and won't be able to work on it for a while.<p>A side note: Clang is such a beauty whose structure is so easy to understand yet very extendible. There are actually few things to be done on clang to support musl. Just implement a proper frontend, and you're mostly done. But it's kinda difficult to patch codes which assume glibc, and the fact that musl refuses to export __MUSL__ macro makes the job even harder.
Excuse the noob question, but why are there different libc implementations at all? I mean, their featureset is defined by standard, so all implementations should strive for the maximum performance - so where comes the bloat from?<p>Support for multiple archs is of course a valid source for percieved bloat, but that should matter only at compile time?
You will after a bit run into issues using Musl with a wrapper script, in my experience, and you are better off using a Musl based distro. You can run one in a chroot, I used to use Sabotage like that quite a bit, or if you use Docker you can just use "FROM alpine" and everything will be nice and statically linked, or you can do an install in a VM.
musl is great, but it would great if there was something at the compiler level that is better than both gcc and LLVM/Clang.<p>LLVM/Clang is a step in the right direction but it's quite bloated because of support for C++, Objective-C etc (for C standards at least); not to mention it's written in C++.<p>Being a Python/C hybrid enthusiast, I looked into taking something like Eli Bendersky's pycparser and making it featureful (preprocesser parsing at the minimum), but haven't done anything in that direction. Maybe some way of combining pycparser and tcc.