From 964782bb7a7fb0759c03a727c2b83f8439030d10 Mon Sep 17 00:00:00 2001 From: Josh Triplett Date: Thu, 19 Nov 2020 13:27:04 -0800 Subject: [PATCH] Update notes about static linking and MUSL People often use the edition guide as general documentation of capabilities, not just for Rust 2018. There is extensive information on the web suggesting that Rust *only* supports static linking with MUSL. Add a note documenting current capabilities, so that people know they have a choice of libc implementations even if they need static linking. --- .../musl-support-for-fully-static-binaries.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/rust-2018/platform-and-target-support/musl-support-for-fully-static-binaries.md b/src/rust-2018/platform-and-target-support/musl-support-for-fully-static-binaries.md index 65381e36..7ef0566b 100644 --- a/src/rust-2018/platform-and-target-support/musl-support-for-fully-static-binaries.md +++ b/src/rust-2018/platform-and-target-support/musl-support-for-fully-static-binaries.md @@ -2,6 +2,9 @@ ![Minimum Rust version: 1.1](https://img.shields.io/badge/Minimum%20Rust%20Version-1.1-brightgreen.svg) +(Note: current Rust (as of 1.48) supports static linking with either glibc or +MUSL, so you can select whichever libc you need or prefer.) + By default, Rust will statically link all Rust code. However, if you use the standard library, it will dynamically link to the system's `libc` implementation.