See:
.NET RIDs like linux-musl-x64 (and friends) are meant for systems with a dynamic musl libc, such as Alpine. Linking musl statically is not what we want and is likely to blow up in 'fun' ways. As a result, our support for musl-based RIDs for C/C++ code is effectively unusable right now (but should work fine for Zig code).
I think this is strictly an upstream Zig bug; we pass all the right flags on our end.
See:
.NET RIDs like
linux-musl-x64(and friends) are meant for systems with a dynamic musl libc, such as Alpine. Linking musl statically is not what we want and is likely to blow up in 'fun' ways. As a result, our support for musl-based RIDs for C/C++ code is effectively unusable right now (but should work fine for Zig code).I think this is strictly an upstream Zig bug; we pass all the right flags on our end.