-
Notifications
You must be signed in to change notification settings - Fork 303
Create Updating-musl-1.2.5.md #1641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Gankra
wants to merge
2
commits into
rust-lang:master
Choose a base branch
from
Gankra:patch-1
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
+++ | ||
path = "2025/07/01/Updating-musl-1.2.5" | ||
title = "Updating Rust's Linux musl targets to 1.2.5" | ||
authors = ["Aria Desires"] | ||
description = "musl targets will soon ship with musl 1.2.5" | ||
|
||
[extra] | ||
team = "The Compiler Team" | ||
team_url = "https://www.rust-lang.org/governance/teams/compiler" | ||
+++ | ||
|
||
# Updating Rust's Linux musl targets to 1.2.5 | ||
|
||
Beginning with Rust 1.90 (slated for stable release on 2025-09-18), the various `*-linux-musl` targets will [ship](https://github.com/rust-lang/rust/pull/142682) with musl 1.2.5. These targets currently use musl 1.2.3. This update comes with [several fixes and improvements](https://musl.libc.org/releases.html), and a breaking change that affects the Rust ecosystem. | ||
|
||
For the Rust ecosystem, the primary motivation for this update is to receive major improvements to musl's DNS resolver which shipped in 1.2.4 and received bug fixes in 1.2.5. When using `musl` targets for static linking, this should make portable linux binaries that do networking more reliable, particularly in the face of large DNS records and recursive nameservers. | ||
|
||
However, 1.2.4 also comes with a breaking change: [the removal of several legacy compatibility symbols that the Rust libc crate was using](https://github.com/rust-lang/libc/issues/2934). A fix for this [was shipped in libc 0.2.146 in June 2023 (2 years ago)](https://github.com/rust-lang/libc/pull/2935), and we have been waiting for newer versions of the libc crate to propagate throughout the ecosystem before shipping the musl update. | ||
|
||
A crater run in July 2024 (a year ago) [found only about 2% of rust projects were still affected](https://github.com/rust-lang/rust/pull/125692#issuecomment-2245182085). At this point we expect there will be minimal breakage, and most breakage should be resolved by a `cargo update`. We believe this update shouldn't be held back any longer, as it contains critical fixes for the musl target. | ||
|
||
# Updated targets | ||
|
||
The following targets will be updated (this is just "all musl targets except [`loongarch64-unknown-linux-musl`](https://doc.rust-lang.org/rustc/platform-support/loongarch-linux.html) which already was on 1.2.5, and [WALI](https://github.com/arjunr2/WALI) which doesn't use our bundled musl"): | ||
|
||
|
||
## Tier 2 with Host Tools | ||
|
||
target | notes | ||
-------|------- | ||
`aarch64-unknown-linux-musl` | ARM64 Linux with musl 1.2.3 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. is it intended to put the old musl versions here? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It was but I can change it or omit the version entirely. |
||
[`powerpc64le-unknown-linux-musl`](https://doc.rust-lang.org/rustc/platform-support/powerpc64le-unknown-linux-musl.html) | PPC64LE Linux (kernel 4.19, musl 1.2.3) | ||
[`riscv64gc-unknown-linux-musl`](https://doc.rust-lang.org/rustc/platform-support/riscv64gc-unknown-linux-musl.html) | RISC-V Linux (kernel 4.20, musl 1.2.3) | ||
`x86_64-unknown-linux-musl` | 64-bit Linux with musl 1.2.3 | ||
|
||
|
||
## Tier 2 without Host Tools | ||
|
||
|
||
target | std | notes | ||
-------|:---:|------- | ||
`arm-unknown-linux-musleabi` | ✓ | Armv6 Linux with musl 1.2.3 | ||
`arm-unknown-linux-musleabihf` | ✓ | Armv6 Linux with musl 1.2.3, hardfloat | ||
`armv5te-unknown-linux-musleabi` | ✓ | Armv5TE Linux with musl 1.2.3 | ||
`armv7-unknown-linux-musleabi` | ✓ | Armv7-A Linux with musl 1.2.3 | ||
`armv7-unknown-linux-musleabihf` | ✓ | Armv7-A Linux with musl 1.2.3, hardfloat | ||
`i586-unknown-linux-musl` | ✓ | 32-bit Linux (musl 1.2.3, original Pentium) | ||
`i686-unknown-linux-musl` | ✓ | 32-bit Linux with musl 1.2.3 (Pentium 4) | ||
|
||
## Tier 3 | ||
|
||
|
||
target | std | host | notes | ||
-------|:---:|:----:|------- | ||
[`hexagon-unknown-linux-musl`](https://doc.rust-lang.org/rustc/platform-support/hexagon-unknown-linux-musl.html) | ✓ | | Hexagon Linux with musl 1.2.3 | ||
`mips-unknown-linux-musl` | ✓ | | MIPS Linux with musl 1.2.3 | ||
[`mips64-openwrt-linux-musl`](https://doc.rust-lang.org/rustc/platform-support/mips64-openwrt-linux-musl.html) | ? | | MIPS64 for OpenWrt Linux musl 1.2.3 | ||
`mips64-unknown-linux-muslabi64` | ✓ | | MIPS64 Linux, N64 ABI, musl 1.2.3 | ||
`mips64el-unknown-linux-muslabi64` | ✓ | | MIPS64 (little endian) Linux, N64 ABI, musl 1.2.3 | ||
`mipsel-unknown-linux-musl` | ✓ | | MIPS (little endian) Linux with musl 1.2.3 | ||
`powerpc-unknown-linux-musl` | ? | | PowerPC Linux with musl 1.2.3 | ||
[`powerpc-unknown-linux-muslspe`](https://doc.rust-lang.org/rustc/platform-support/powerpc-unknown-linux-muslspe.html) | ? | | PowerPC SPE Linux with musl 1.2.3 | ||
[`powerpc64-unknown-linux-musl`](https://doc.rust-lang.org/rustc/platform-support/powerpc64-unknown-linux-musl.html) | ✓ | ✓ | PPC64 Linux (kernel 4.19, musl 1.2.3) | ||
`riscv32gc-unknown-linux-musl` | ? | | RISC-V Linux (kernel 5.4, musl 1.2.3 + RISCV32 support patches) | ||
[`s390x-unknown-linux-musl`](https://doc.rust-lang.org/rustc/platform-support/s390x-unknown-linux-musl.html) | ✓ | | S390x Linux (kernel 3.2, musl 1.2.3) | ||
`thumbv7neon-unknown-linux-musleabihf` | ? | | Thumb2-mode Armv7-A Linux with NEON, musl 1.2.3 | ||
[`x86_64-unikraft-linux-musl`](https://doc.rust-lang.org/rustc/platform-support/unikraft-linux-musl.html) | ✓ | | 64-bit Unikraft with musl 1.2.3 |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be worth to quote an example error one might encounter, as the error message is not 100% obvious (it's a linker error). You can look around the crater run's logs to extract it.