>>>>> "JK" == Jan Kurik <jku...@redhat.com> writes:
JK> https://fedoraproject.org/wiki/Changes/DiscontinuePPC64 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. - J< _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/5YS4U3RQ3C6YIOUDR74VE4BOW2XM5YAG/
