Description of problem: Trying to build commit dcf7368eeab15e2affc6256f0bb1e84dd46a34de from github.com/containernetworking/plugins and scratch build fails on s390x with the following buildlog Mock Version: 1.3.4 Mock Version: 1.3.4 ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target s390x --nodeps /builddir/build/SPECS/containernetworking-cni.spec'], chrootPath='/var/lib/mock/f27-build-8955210-764754/root'logger=<mockbuild.trace_decorator.getLog object at 0x3ff786e26d8>shell=Falsetimeout=172800user='mockbuild'nspawn_args=[]printOutput=Falsegid=425env={'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"'}uid=1000) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target s390x --nodeps /builddir/build/SPECS/containernetworking-cni.spec'] with env {'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"'} and shell False Building target platforms: s390x Building for target s390x Wrote: /builddir/build/SRPMS/containernetworking-cni-0.5.2-2.fc27.src.rpm Child return code was: 0 ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --target s390x --nodeps /builddir/build/SPECS/containernetworking-cni.spec'], chrootPath='/var/lib/mock/f27-build-8955210-764754/root'logger=<mockbuild.trace_decorator.getLog object at 0x3ff786e26d8>shell=Falsetimeout=172800user='mockbuild'nspawn_args=[]printOutput=Falsegid=425env={'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"'}uid=1000) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --target s390x --nodeps /builddir/build/SPECS/containernetworking-cni.spec'] with env {'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"'} and shell False Building target platforms: s390x Building for target s390x Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.LIOtoU + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf plugins-dcf7368eeab15e2affc6256f0bb1e84dd46a34de + /usr/bin/gzip -dc /builddir/build/SOURCES/plugins-dcf7368.tar.gz + /usr/bin/tar -xof - + STATUS=0 + '[' 0 -ne 0 ']' + cd plugins-dcf7368eeab15e2affc6256f0bb1e84dd46a34de + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.yFw2PG + umask 022 + cd /builddir/build/BUILD + cd plugins-dcf7368eeab15e2affc6256f0bb1e84dd46a34de + ./build.sh Building plugins flannel # github.com/containernetworking/plugins/plugins/meta/flannel L0: $WORK/runtime/cgo.a(_all.o): sym#625: ignoring symbol in section 17 (type 0) L0: $WORK/runtime/cgo.a(_all.o): sym#626: ignoring symbol in section 17 (type 0) L0: $WORK/runtime/cgo.a(_all.o): sym#627: ignoring symbol in section 17 (type 0) error: Bad exit status from /var/tmp/rpm-tmp.yFw2PG (%build) Bad exit status from /var/tmp/rpm-tmp.yFw2PG (%build) RPM build errors: Child return code was: 1 EXCEPTION: [Error()] Traceback (most recent call last): File "/usr/lib/python3.5/site-packages/mockbuild/trace_decorator.py", line 89, in trace result = func(*args, **kw) File "/usr/lib/python3.5/site-packages/mockbuild/util.py", line 582, in do raise exception.Error("Command failed. See logs for output.\n # %s" % (command,), child.returncode) mockbuild.exception.Error: Command failed. See logs for output. # bash --login -c /usr/bin/rpmbuild -bb --target s390x --nodeps /builddir/build/SPECS/containernetworking-cni.spec This works on other arches though. Adding ExcludeArch: s390x until this is fixed.
There is a s390x golang/binutils issue causing the problem.
Hi Lokesh, you can re-enable s390x in the various builds, the new golang-1.9-0.beta2.1.fc27 contains a workaround for the s390x build failures.
Thanks Dan, closing this ..