lld linker error on mips64[el] linux targets.
Open
Nobody has claimed this yet.
-Zfixed-x18
A-cross
S-needs-repro
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
When cross-compiling to mips64[el] linux targets using -Zbuild-stdgot lld linking error:
linking with `mips64-linux-gnuabi64-gcc` failed: exit status: 1
rust-lld: error: /usr/lib/gcc-cross/mips64el-linux-gnuabi64/12/../../../../mips64el-linux-gnuabi64/lib/../lib/crtn.o: requires an executable stack, but -z execstack is not specified
rust-lld: error: /usr/lib/gcc-cross/mips64el-linux-gnuabi64/12/../../../../mips64el-linux-gnuabi64/lib/../lib/crti.o: requires an executable stack, but -z execstack is not specified
rust-lld: error: /usr/lib/gcc-cross/mips64el-linux-gnuabi64/12/../../../../mips64el-linux-gnuabi64/lib/../lib/Scrt1.o: requires an executable stack, but -z execstack is not specified
Rust 1.87.0-nightly (cbfdf0b01 2025-03-13)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report provides a cross-compilation reproduction using -Zbuild-std and mips64[el] Linux targets, with failures from rust-lld while linking through mips64-linux-gnuabi64-gcc. Start by reproducing the link and tracing the handling of the executable-stack requirement; done means the affected target links successfully without the reported lld errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, rust
- Domain
- compilers, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100