galera fails to build on ppc64 due to lack of support for ppc64 in chromium/build_config.h.
Note that I attempted to patch this by adding the following to chromium/build_config.h: ... #elif defined(__PPC64__) #define ARCH_CPU_64_BITS 1 #define ARCH_CPU_BIG_ENDIAN 1 ... While this clears up the previous compiler warnings, two of the tests fail. Running suite(s): CRC32C implementation 0%: Checks: 2, Failures: 2, Errors: 0 galerautils/tests/gu_crc32c_test.c:56:F:test:test_software:0: Input '123456789' resulted in 0x10065321, expected 0xe3069283 galerautils/tests/gu_crc32c_test.c:56:F:test:test_hardware:0: Input '123456789' resulted in 0x10065321, expected 0xe3069283 Need to investigate further.
This also affects fedora package. I posted link to this ticket upstream. Upstream bug tracker ticket https://bugs.launchpad.net/galera/+bug/1257803.
This is fixed in 25.3.12, but some arches require an additional patch due to -march=native. Fedora 25.3.12-2 builds successfully on aarch64, ppc64*, and s390*: http://arm.koji.fedoraproject.org/koji/buildinfo?buildID=328764 http://ppc.koji.fedoraproject.org/koji/buildinfo?buildID=353746 http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=2004118 http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=2004155 Please merge from master into epel7 and update.
*** Bug 1269628 has been marked as a duplicate of this bug. ***
Ryan, Any objections to merging master into epel7 for the secondary arches?
galera-25.3.12-2.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-c1f0e4564e
galera-25.3.12-2.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-c1f0e4564e
galera-25.3.12-2.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.