Output of "uname -m", "cargo --version" and "rustc --version".

@p
No, your memory deceives you. Newer PowerPCs are little-endian — and that is the architecture still supported by a lot of distros, unlike BE.
64 PowerPC CPUs could switch endian-ness too: https://en.wikipedia.org/wiki/PowerPC#Endian_modes
That G5 just doesn't support it, at least I've never seen it done on real hardware and doing so would be trouble anyway as old Apple's OpenFirmware surely doesn't support that.
ppc64le is even supported by the reference Go toolchain, again, unlike BE — which is supported by gccgo though, but there's little use in it as most modules do not support that anyway and you'd have to do a lot of work porting those too. I think I've even succeeded building gccgo for 32-bit PowerPC, which is no longer possible as it looks like some definitions got removed from gcc's source. You can in theory add those back of course, but like I already said — there'd be little use in it as most modules won't work as is anyway.

Unlike Rust BTW! Which works on nearly anything and the kitchen sink, here's the machine this instance runs on. And it's probably a relatively recent version even.
I'm not even that sure that RISC-V machines aren't supported — they are probably worse supported than more mainstream architectures and have a similar problem — even more mainstream modules won't work. I have this problem on PowerPC too, e.g. ring is a pretty popular cryptography crate, but it can't even be built as is. IBM made a series of patches so it's possible for ppc64le and with a little effort I could make it build on this 32-bit machine even, but autotests still fail — looks like there are more underlying issues. I originally started these effort with intent to host libreddit — but as Reddit went to shit anyway, I've just given up :marseyshrug:

@allison @istvan

Public

Output of "uname -m", "cargo --version" and "rustc --version".

Notices where this attachment appears