

Now that we have `crt-static` target-feature (the user can choose dynamic link for musl targets), and libunwind ( ) add support to mips, we do not need to assume dynamic linking.ĭiff -git a/src/Cargo.lock b/src/Cargo.lock When the musl/mips targets was ( ), dynamic linking was chosen because of binary size concerns, and probably also because libunwind ( ) supported mips.

21882aad7299e8e859785845ac12374990f24dae Ģ875f825fd5a29d94bbfd78b1019ebdedd8d2444 Īuto merge of #47663 - malbarbo:mips-crt-static, r=alexcrichtonĭo not assume dynamic linking for musl/mips targetsĪll musl targets except mips assume static linking by default.
