Skip to content

Commit 03eb597

Browse files
committed
Merge pull request #100 from aidanhs/patch-1
It is possible (if difficult) to statically link glibc
2 parents 550bd8f + befc677 commit 03eb597

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

_posts/2016-05-13-rustup.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -183,10 +183,10 @@ libraries they have installed.
183183
[ELF]: https://en.wikipedia.org/wiki/Executable_and_Linkable_Format
184184

185185
Today's Rust depends on libc, and on most Linuxes that means
186-
glibc. For technical reasons, glibc cannot be fully statically linked,
187-
making it unusable for producing a truly standalone
186+
glibc. It's technically challenging to fully statically link glibc,
187+
which presents difficulties when using it to produce a truly standalone
188188
binary. Fortunately, an alternative exists: [musl], a small, modern
189-
implementation of libc that *can* be statically linked. Rust has been
189+
implementation of libc that can be easily statically linked. Rust has been
190190
compatible with musl since version 1.1, but until recently developers
191191
have needed to build their own compiler to benefit from it.
192192

0 commit comments

Comments
 (0)