Bump musl libc and gcc version for *-musl targets

[Dirreke]

Close #1794

This PR updates the existing *-musl targets to use a newer musl toolchain while keeping the previous toolchain available for compatibility.

• Migrate the affected musl targets from musl-cross-make to crosstool-ng.
• Upgrade the default toolchain from musl 1.2.3 / GCC 9.2.0 to musl 1.2.5 / GCC 14.3.0.
• Keep the previous musl 1.2.3 / GCC 9.2.0 toolchain available through :legacy images.
• Refresh the target/toolchain table in the README and document how to use the legacy images.

[Emilgardis]

Thank you for the PR! I'm open to merge this, however it will double CI time for musl. Not sure if I like that. Will have to think about it

[Emilgardis]

we have a quick way to refer to these targets using just -<sub>

Suggested change

	[8] To use the legacy GCC 9.2 musl toolchain, set `image = "ghcr.io/cross-rs/x86_64-unknown-linux-gnu:main-legacy"` in the
	[8] To use the legacy GCC 9.2 musl toolchain, set `image = "-legacy"` in the

[Dirreke]

Thanks for the feedback! IMO, the *-legacy targets may not be necessary. For the *-musl targets, libc is statically linked, so the resulting binaries do not have a runtime dependency on the target system's libc version. Would it make sense to first try upgrading the existing *-musl targets without keeping the legacy images? This would also avoid doubling the musl CI time.

BTW, would it be possible to first run /ci try on the current changes, so I can check for any build or CI errors and finish the remaining work?

[Emilgardis]

Of course! My bad forgot :)

/ci try --target -musl

And yes, im ok with omitting the legacy targets

[Dirreke]

It seems that https://www.musl-libc.org is not stable.

[Dirreke]

@Emilgardis Would you like to give it another try?

[Emilgardis]

/ci try --target *-musl*

[Dirreke]

Looks like CI didn’t start successfully.

[Emilgardis]

/ci try --target -musl

[Dirreke]

@Emilgardis , Please help try x86_64-unknown-linux-musl again,thanks.

[Emilgardis]

/ci try --target x86_64-unknown-linux-musl

[Dirreke]

fixed

[Dirreke]

@Emilgardis Could you help try again?

[Emilgardis]

/ci try --target -musl

[github-actions]

Try run for comment

• try / conclusion - ❌ Result

Failed Jobs

List

• arm-unknown-linux-musleabi - ❌ Build Docker image
• riscv64gc-unknown-linux-musl - ❌ Build Docker image
• i686-unknown-linux-musl - ❌ Build Docker image
• armv5te-unknown-linux-musleabi - ❌ Build Docker image
• armv7-unknown-linux-musleabi - ❌ Build Docker image
• arm-unknown-linux-musleabihf - ❌ Build Docker image
• armv7-unknown-linux-musleabihf - ❌ Build Docker image
• i586-unknown-linux-musl - ❌ Build Docker image
• x86_64-unknown-linux-musl - ❌ Build Docker image
• aarch64-unknown-linux-musl - ❌ Build Docker image
• loongarch64-unknown-linux-musl - ❌ Build Docker image

[Dirreke]

Still network issue. Lets try it again tomorrow.

[Dirreke]

@Emilgardis