On 5.10.2018 04:58, Jerry James wrote:
I am trying to determine why the latest version of bigloo segfaults on
s390x during the build. I launched a mock build with mock -r
fedora-rawhide-s390x --forcearch=s390x --rebuild
bigloo-4.3c-1.fc30.src.rpm, then went away for several hours. I came
back to see this:
Running scriptlet: desktop-file-utils-0.23-9.fc29.s390x 570/570
Running scriptlet: fontconfig-2.13.1-1.fc30.s390x 570/570
Running scriptlet: adwaita-icon-theme-3.30.0-1.fc30.noarch 570/570
Running scriptlet: hicolor-icon-theme-0.17-3.fc29.noarch 570/570
Running scriptlet: shared-mime-info-1.10-2.fc29.s390x 570/570
Running scriptlet: gdk-pixbuf2-2.38.0-4.fc30.s390x 570/570
And there it sits. Running ps shows:
root 27051 15060 0 Oct4 ? 00:00:00
/usr/bin/qemu-s390x-static /bin/sh /var/tmp/rpm-tmp.WNZJDC 0 0
root 27053 27051 99 Oct4 ? 10:09:31
/usr/bin/qemu-s390x-static /bin/gdk-pixbuf-query-loaders-64
--update-cache
So apparently gdk-pixbuf-query-loaders-64 has hung. This didn't
happen during the koji build, so it must be some artifact of building
with qemu-static. Does anybody have any idea how I can either
diagnose or avoid the hang?
You could --copyin the rpms and use rpm --noscripts (in mock shell) to
install them. Not sure if it would function later, but should avoid the
scriptlet being run.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
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
