Bugzilla – Bug 1213224
illegal instruction while building ppc64le
Last modified: 2023-08-17 10:17:38 UTC
Visit https://build.opensuse.org/package/live_build_log/hardware/libplist/openSUSE_Factory_PPC/ppc64le Package hardware/libplist failed to build in openSUSE_Factory_PPC/ppc64le Check out the package for editing: osc checkout hardware libplist Last lines of build log: [ 37s] post-build-checks-84.87+git20230328.de######################################## [ 37s] attr-2.5.1-1.23 ######################################## [ 37s] build-mkbaselibs-20230628-1.1 ######################################## [ 38s] kernel-obs-build-6.3.9-1.1 ######################################## [ 39s] now finalizing build dir... [ 39s] ... running 01-add_abuild_user_to_trusted_group [ 39s] ... running 02-set_timezone_to_utc [ 39s] ... running 03-set-permissions-secure [ 39s] ... running 11-hack_uname_version_to_kernel_version [ 40s] ----------------------------------------------------------------- [ 40s] I have the following modifications for libplist.spec: [ 40s] 23c23 [ 40s] < Release: 0 [ 40s] --- [ 40s] > Release: 2.5 [ 42s] ----------------------------------------------------------------- [ 42s] ----- building libplist.spec (user abuild) [ 42s] ----------------------------------------------------------------- [ 42s] ----------------------------------------------------------------- [ 42s] /.build/build-recipe-spec: line 170: 1079 Illegal instruction chroot $BUILD_ROOT $rpmbuild --undefine --help >&/dev/null [ 42s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --define 'disturl obs://build.opensuse.org/hardware/openSUSE_Factory_PPC/7934553a10bfea6c1c507ad1acc536bf-libplist' /home/abuild/rpmbuild/SOURCES/libplist.spec [ 42s] Illegal instruction [ 42s] ### VM INTERACTION START ### [ 42s] [ 28.122495][ T1] sysrq: Power Off [ 42s] [ 28.123277][ T55] reboot: Power down [ 42s] ### VM INTERACTION END ### [ 42s] [ 42s] obs-power8-05 failed "build libplist.spec" at Tue Jul 11 16:48:09 UTC 2023. [ 42s]
Looks like the same problem. *** This bug has been marked as a duplicate of bug 1213915 ***