`powerpc64-unknown-linux-musl` target linking error, ABI ELFv1/2 conflict.

[Wyvern]

Using Rust nightly on linux build with -Zbuild-std, got linking error:

error: linking with `powerpc64-linux-gnu-gcc` failed: exit status: 1
= note: /usr/lib/gcc-cross/powerpc64-linux-gnu/13/../../../../powerpc64-linux-gnu/bin/ld: /home/runner/work/Img/Img/build-dir/powerpc64-unknown-linux-musl/src/deps/Img-7d148067c837aa56.Img.b388e7fa58e03b87-cgu.0.rcgu.o: ABI version 2 is not compatible with ABI version 1 output
          /usr/lib/gcc-cross/powerpc64-linux-gnu/13/../../../../powerpc64-linux-gnu/bin/ld: failed to merge target specific data of file /home/runner/work/Img/Img/build-dir/powerpc64-unknown-linux-musl/src/deps/Img-7d148067c837aa56.Img.b388e7fa58e03b87-cgu.0.rcgu.o
          collect2: error: ld returned 1 exit status

[workingjubilee]

headscratch

Can you give the precise build setup? I would like to be able to refer this to the target maintainer, but I feel bad about pinging them when we don't have repro instructions yet.

[workingjubilee]

I assume it repros with helloworld, to be clear, so I am just wondering what the exact command used to trigger the build was.

[bjorn3]

At least in rustc the -gnu target uses the ELFv1 ABI. powerpc64-linux-gnu-gcc probably does the same. The -musl target however uses the ELFv2 ABI. You will have to get a toolchain which uses the ELFv2 ABI if you want to compile for powerpc64-unknown-linux-musl.

[workingjubilee]

Ah yeah, looking at the target docs, they specify a musl-specific toolchain: https://doc.rust-lang.org/nightly/rustc/platform-support/powerpc64-unknown-linux-musl.html#building-the-target

Classing this as working-as-intended (by not working).