Conversation
|
Rust supports JSON target spec files for unsupported platforms, which would be the correct thing to use here; cc @dramforever. |
|
I think this is the nicest way to get custom target JSON working - although having target JSON files in-tree doesn't look particularly nice, I'm hoping that at least it could be temporary, until maaaybe upstream rustc adds a elfv2 variant. |
fbac021 to
f5b1b6c
Compare
|
Changed this to instead add Do we have anything in |
f5b1b6c to
81d59f8
Compare
|
This will sadly be broken by #510674, which deprecates JSON target specs :( |
|
Hmm… So back to patching |
|
I don't know what the right thing is now. :(
They were asking for feedback on the target mechanism I think, so would be good to engage with that.
|
|
Based on the conversations in rust-lang/rust#151528, rust-lang/rust#155620, and LibreELEC/LibreELEC.tv#11205, I guess this should go back to making changes in I couldn't find an example of how to i.e. make a |
|
If you're not otherwise going to use it, does making any change here justify the complexity increase in our rustc packaging? I'm all for supporting exotic platforms, but it seems silly to go out of our way to support something upstream doesn't, and that is also not useful for other reasons. |
|
I know we have users of powerpc64-unknown-linux-gnuabielfv2 (#451088 (comment), CC @minijackson), and people who IIRC would prolly prefer for us to have gnuabielfv2 as our default ABI again (CC @amaanq). I'm fine with ELFv1 myself, but I can test ELFv2 stuff on hardware, so I don't mind doing a little bit of work to support it. |
|
Should maybe be possible to just change the target adjustment in |
…libc It is now properly supported by rustc, ABI component of the triplet just differs from the one recognised by GCC and Clang.
81d59f8 to
62b9f45
Compare
|
Switched to adjusting our |
Rustc 1.98 added official support for powerpc64-unknown-linux-gnuabielfv2! They just name it not quite that: https://doc.rust-lang.org/nightly/rustc/platform-support/powerpc64-unknown-linux-gnuelfv2.html
Fixes i.e.
pkgsCross.ppc64-elfv2.fd.I don't know if this has come up in your cross ppc64-elfv2 deployments for work, but CC @minijackson just in case.
Things done
pkgsCross.ppc64-elfv1.fd,pkgsCross.ppc64-elfv2.fd,pkgsCross.ppc64-musl.fd)passthru.tests.nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.