https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: app-emulation/qemu-7.0.0-r3 fails tests (lto). Discovered on: amd64 (internal ref: lto_tinderbox) NOTE: This machine uses lto with CFLAGS=-flto -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing Here is a bit of explanation: -Werror=lto-type-mismatch: User to find possible runtime issues in packages. It likely means the package is unsafe to build & use with LTO. For projects using the same identifier but with different types across different files, they must be fixed to be consistent across the codebase. -Werror=odr: Used to find possible runtime issues in packages. These bugs are a problem anyway but may be even worse when combined with LTO. C++ code must comply with the One Definition Rule (ODR) - see https://en.cppreference.com/w/cpp/language/definition#One_Definition_Rule. -Werror=strict-aliasing: Used to find possible runtime issues in packages. These bugs are a problem anyway but may be even worse when combined with LTO. Workarounds: - If upstream is friendly and still active, file a bug upstream. For emulators, codecs, games, or multimedia packages, it may be worth just applying a workaround instead, as upstreams sometimes aren't receptive to these bugs (VALID FOR ALL). - Use the new 'filter-lto' from flag-o-matic.eclass as it's likely to be unsafe with LTO (VALID FOR lto-type-mismatch - odr). - Fix it yourself if interested, of course (VALID FOR ALL). - Append-flags -fno-strict-aliasing (VALID FOR strict-aliasing). - Use memcpy() but a union is sometimes suitable too (VALID FOR strict-aliasing). - -fstrict-aliasing is implied by -O2, so this must be addressed in some form (VALID FOR strict-aliasing). See also: https://marc.info/?l=gentoo-dev&m=165639574126280&w=2
Created attachment 800011 [details] build.log.xz build log and emerge --info (compressed because it exceeds attachment limit, use 'xzless' to read it)
Created attachment 800013 [details] 1-testlog.txt.xz 1-testlog.txt (compressed because it exceeds attachment limit, use 'xzless' to read it)
Error(s) that match a know pattern in addition to what has been reported in the summary: 7/171 qemu:qtest+qtest-x86_64 / qtest-x86_64/qos-test ERROR 0.30s killed by signal 6 SIGABRT 7/171 qemu:qtest+qtest-x86_64 / qtest-x86_64/qos-test ERROR 0.30s killed by signal 6 SIGABRT Could not access KVM kernel module: Permission denied Program cgcc found: NO Run-time dependency appleframeworks found: NO (tried framework) Run-time dependency libdaxctl found: NO (tried pkgconfig) Run-time dependency libkeyutils found: NO (tried pkgconfig) Run-time dependency libpmem found: NO (tried pkgconfig) Run-time dependency spice-protocol found: NO (tried pkgconfig) Run-time dependency u2f-emu found: NO (tried pkgconfig) qemu-system-x86_64: -accel kvm: failed to initialize kvm: Permission denied
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ce974471d1bc7a9b33fa138f54f35f0e9bc7a77b commit ce974471d1bc7a9b33fa138f54f35f0e9bc7a77b Author: Sam James <sam@gentoo.org> AuthorDate: 2023-08-26 03:49:00 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-08-26 03:49:00 +0000 app-emulation/qemu: add 8.1.0 Fix some test failures too (skip a test which fails for me, probably kernel config or network-sandbox related + crank up timeouts). Closes: https://bugs.gentoo.org/865647 Closes: https://bugs.gentoo.org/867766 Signed-off-by: Sam James <sam@gentoo.org> app-emulation/qemu/Manifest | 2 + .../qemu/files/qemu-8.1.0-find-sphinx.patch | 10 + .../qemu/files/qemu-8.1.0-skip-tests.patch | 64 ++ app-emulation/qemu/qemu-8.1.0.ebuild | 963 +++++++++++++++++++++ app-emulation/qemu/qemu-9999.ebuild | 19 +- 5 files changed, 1047 insertions(+), 11 deletions(-)
