Add loongarch64 musllinux_1_2 #109
Conversation
Signed-off-by: 吴小白 <[email protected]>
wojiushixiaobai
force-pushed
the
main
branch
3 times, most recently
from
af931ae to
db2b3cc
Compare
Signed-off-by: 吴小白 <[email protected]>
There was a problem hiding this comment.
Thanks, we should also update https://github.com/rust-cross/manylinux-cross/blob/main/render.py to include the new targets (and some others we forget to add to it).
wojiushixiaobai
force-pushed
the
main
branch
2 times, most recently
from
cce3acd to
66dbb98
Compare
Dockerfile.j2
Outdated
| ENV CARGO_BUILD_TARGET={{ target | replace('ibm', 'unknown') | replace('riscv64', 'riscv64gc') }} | ||
| ENV CARGO_TARGET_{{ target | replace('ibm', 'unknown') | replace('-', '_') | replace('riscv64', 'riscv64gc') | upper }}_LINKER={{ target }}-gcc | ||
| {% if platform.startswith('musllinux') -%} | ||
| ENV CARGO_TARGET_{{ target | replace('ibm', 'unknown') | replace('-', '_') | upper }}_RUSTFLAGS='-C target-feature=+crt-static' |
There was a problem hiding this comment.
https://peps.python.org/pep-0656/#rationale
The musllinux platform tags only apply to Python interpreters dynamically linked against the musl libc and executed on the runtime shared library, on a Linux operating system. Statically linked interpreters or mixed builds with other libc implementations (such as glibc) are out of scope and not supported by platform tags defined in this document. Such interpreters should not claim compatibility with musllinux platform tags.
I don't think we should static link musl libc?
There was a problem hiding this comment.
OK, let me fix that.
Signed-off-by: 吴小白 <[email protected]>
I tested and it works.