Three tests are failing on ppc64 during build: http://ppc.koji.fedoraproject.org/koji/getfile?taskID=126442&name=build.log Two times it is expecting -1 as return value and the test returned 255. This could be a simple signed/unsigned mix-up. The third error is: -85984 MULTIPOLYGON 0 POINT(-114.87787186923313 36.33101763469059) +85984 MULTIPOLYGON 0 POINT(-114.87787186923326 36.33101763469053)
Workarounds added in mysql-5.5.8-7. Filed these issues upstream, too: http://bugs.mysql.com/bug.php?id=59905 http://bugs.mysql.com/bug.php?id=59908
Thanks, for the fixes! Unfortunately the third error still exists during a scratch build: http://ppc.koji.fedoraproject.org/koji/getfile?taskID=127127&name=build.log
How annoying. The -ffloat-store hack did fix it in a test on a RHEL-6 machine, but of course that was not using gcc 4.6.0 (RHEL-6 is at 4.4.4 or 4.4.5). I guess the only reliable workaround is to disable that regression test.
Try mysql-5.5.8-8 ...
So, now something fails on ppc 32 bit: http://ppc.koji.fedoraproject.org/koji/getfile?taskID=127754&name=build.log
5.5.9-1 also fails: http://ppc.koji.fedoraproject.org/koji/getfile?taskID=131205&name=build.log
mysql-5.5.9-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/mysql-5.5.9-2.fc15
New problem in 5.5.9, filed at http://bugs.mysql.com/bug.php?id=60155. In general it appears that upstream isn't testing on any non-Intel architectures ...
mysql-5.5.9-2.fc15 has been pushed to the Fedora 15 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update mysql'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/mysql-5.5.9-2.fc15
mysql-5.5.9-2.fc15 was successfully built on ppc and ppc64: http://ppc.koji.fedoraproject.org/koji/buildinfo?buildID=28977 Thanks!
mysql-5.5.9-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.