I think musl is stronger than glibc because it tries to follow POSIX standards more quickly, and make standard function more secure.
By keeping everything simpler, they make the code easier to review/maintain, so the libc is much stronger overall. Now that's just my POV and some would probably disagree. I don't care much about them.

So what have I done so far?

I have a cross compiler installed in $HOME/cross/gcc-x86_64:


It links everything statically, and use only what's in $HOME/cross/gcc-x86_64/bin/x86_64-linux-musl/{lib,include}
So if I want to compile something against, let's say libressl, I first need to install libressl's headers and libs to my toolchain's root.

I have written a dumb package manager which can install packages to whatever root the $PMROOT variable points to. It makes everything stupidly easy to work with
Here is what happens when compiling curl alone, with --with-ssl flag:


SSL is disabled as the configure script couldn't find the appropriate libs.
Now if I build libressl, and install it to the cross-compiler directory:


SSL support is now compiled in, yay!
I can then just remove the libressl package from the cross environment:


Next step is to figure out what are the base packages that are needed on a fresh install. If you have any suggestion, they're welcome!