>>>> "JK" == Jan Kurik <jkurik(a)redhat.com>
This may be necessary, but it's sadly unfortunate as (so far as I can
tell) it leaves us with only one big-endian architecture (s390x). And
while it was not difficult to get a login on a ppc64 machine for
testing, I've not been able to get any shell access on s390x so far.
Having builds done on big-endian architectures has helped to point out
endianness-specific breakage with least one upsteam (which, hooray, did
get fixed). Having only one big-endian architecture makes it difficult
to know when you are facing an endianness problem versus something
specific to one architecture. I think we can all agree that "your code
is broken on all big-endian architectures" sounds serious while "your
code is broken on this weird mainframe thing that nobody actually has"
is far less likely to elicit action by a time-constrained upstream.