Add riscv64 manylinux_2_31

[Xeonacid]

riscv64 first get supported in auditwheel at manylinux_2_31. [1]

Use Linux 5.4 as the first LTS kernel version which has a working glibc userspace support.

Backport patches [2][3] to get glibc 2.31, binutils 2.40 and gcc 7.5.0 work together.

Although pypa/manylinux has not added riscv64 image yet[4], adding here makes maturin-action to work, and other apps like uv can make use of that to build riscv64 releases! This may become a booster for advancing pypa/manylinux!

[1] https://github.com/pypa/auditwheel/blob/8964d1e5e5daee875c324c2e0b73cc8f3e5af1c9/src/auditwheel/policy/manylinux-policy.json#L326
[2] crosstool-ng/crosstool-ng#2315
[3] crosstool-ng/crosstool-ng#2316
[4] pypa/manylinux#1426

[Xeonacid]

Hi @messense, could you please release it to the Docker Hub? Thank you very much!

[messense]

Do we need to add these patches in this repo before crosstool-ng release a new version? Quoting https://crosstool-ng.github.io/docs/configuration/

CT_TOP_DIR: The top directory where crosstool-NG is running. You shouldn’t need it in most cases. One case where you may need it is if you have local patches or config files and you store them in your current working directory, you can refer to them by using CT_TOP_DIR, such as: ${CT_TOP_DIR}/patches.myproject.

[messense]

Hi @messense, could you please release it to the Docker Hub? Thank you very much!

https://github.com/rust-cross/manylinux-cross/actions/runs/14280472662

It's running, not sure whether it will succeed though.

[messense]

just noticed, the rust target should be riscv64gc-unknown-linux-gnu?

[messense]

Fixed in 474db27

[Xeonacid]

just noticed, the rust target should be riscv64gc-unknown-linux-gnu?

Oops. Nice catch!

[Xeonacid]

Do we need to add these patches in this repo before crosstool-ng release a new version? Quoting https://crosstool-ng.github.io/docs/configuration/

CT_TOP_DIR: The top directory where crosstool-NG is running. You shouldn’t need it in most cases. One case where you may need it is if you have local patches or config files and you store them in your current working directory, you can refer to them by using CT_TOP_DIR, such as: ${CT_TOP_DIR}/patches.myproject.

Thanks for the information. I'm new to the variable and will look into it. 🧐