http://bugzilla.suse.com/show_bug.cgi?id=1141059 Bug ID: 1141059 Summary: Recent zlib changes cause build failure of qemu-linux-user on ppc64le Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: brogers@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- At:https://build.opensuse.org/package/show/Virtualization:Staging/qemu building qemu-linux-user for ppc64le, I get the following build error now: [ 757s] /usr/lib64/gcc/powerpc64le-suse-linux/9/../../../../powerpc64le-suse-linux/bin/ld: /usr/lib64/gcc/powerpc64le-suse-linux/9/../../../../lib64/libc.a(dl-sysdep.o) and /usr/lib64/gcc/powerpc64le-suse-linux/9/../../../../lib64/libc.a(libc-start.o): warning: multiple common of `__cache_line_size' [ 757s] crc32.c:247:15: error: type of 'crc32_vpmsum' does not match original declaration [-Werror=lto-type-mismatch] [ 757s] contrib/power8-crc/vec_crc32.c:73:14: note: return value type mismatch [ 757s] contrib/power8-crc/vec_crc32.c:73:14: note: type 'unsigned int' should match type 'long unsigned int' [ 757s] contrib/power8-crc/vec_crc32.c:73:14: note: 'crc32_vpmsum' was previously declared here [ 757s] contrib/power8-crc/vec_crc32.c:73:14: note: code may be misoptimized unless '-fno-strict-aliasing' is used [ 757s] lto1: all warnings being treated as errors [ 757s] lto-wrapper: fatal error: c++ returned 1 exit status [ 757s] compilation terminated. [ 757s] /usr/lib64/gcc/powerpc64le-suse-linux/9/../../../../powerpc64le-suse-linux/bin/ld: error: lto-wrapper failed [ 757s] collect2: error: ld returned 1 exit status [ 757s] make[1]: *** [Makefile:218: qemu-aarch64_be] Error 1 [ 757s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/qemu-4.1.0-rc0/aarch64_be-linux-user' [ 757s] make: *** [Makefile:472: aarch64_be-linux-user/all] Error 2 [ 757s] error: Bad exit status from /var/tmp/rpm-tmp.yplz4T (%build) It appears to be related to our settings that warnings are errors, and recent lto enabling activity in zlib. At least, that is my analysis so far. Please investigate. -- You are receiving this mail because: You are on the CC list for the bug.