On 11/24/2017 07:59 AM, Dr. Werner Fink wrote:
I've some trouble with building mksh on PPC64 and
PPC64LE. Very often
it fails on PPC64 fails with:
sometimes it works perfect. Also I see sometimes a similar defect on PPC64LE at
exactly the same check of the test suite of mksh.
All build systems seems to be based on qemu/kvm, nevertheless there seem to be
some differences but how to detect those (virt-what does report nothing).
Maybe it depends on the real host on which qemu-system-ppc64 or qemu-system-ppc64le
will be executed. It could be a defect of qemu based on the hosting system.
This could actually be true provided that OBS actually builds on QEMU and not
really iron. Looking at the build logs for mksh for ppc64  and ppc64el 
in Debian, I don't see this particular testsuite failure in any of the builds
in the history.
And, knowing Thorsten Glaser, the upstream developer, personally, I am very
confident he would have spotted and fixed such a failure immediately. It might
also be a good idea to contact Thorsten direcly as he is always interested
in bug reports and fixing the bugs.
Do we have some real PPC64 and/or PPC64LE irons in our
build farm or all hosts
based on qemu/kvm?
If you don't happen to get access from someone at SUSE, I will be happy to
provide you with an account on a powerpc (32-bit) or ppc64 (64-bit, big-
endian) porterbox running Debian unstable. I have also an instance running
openSUSE Tumbleweed ppc64.
If you need access to a ppc64el machine, I could help you getting in touch
with people from IBM who I happen to know through Debian.
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org