musl is not always dynamically linked

[alexrp]

See:

• support dynamic linking musl libc ziglang/zig#5364
• [zig cc] unable to dynamically link musl executables ziglang/zig#11909

.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.

[alexrp]

Need to try the workaround mentioned here: ziglang/zig#11909 (comment)

[alexrp]

Need to try the workaround mentioned here: ziglang/zig#11909 (comment)

This appears to work. We can do this as a temporary workaround.

Also, as I noted in ziglang/zig#11909 (comment), this bug does not actually affect shared libraries.

[alexrp]

This appears to work. We can do this as a temporary workaround.

This won't actually work in our case after all, as it requires the dynamic linker to be present at the given path (e.g. /usr/lib/ld-musl-x86_64.so.1) at build time, which is fundamentally incompatible with cross-compilation.