https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: x11-plugins/lurch-0.7.0 fails tests (LTO-SYSTEM). Discovered on: amd64 (internal ref: lto_tinderbox) NOTE: (LTO-SYSTEM) in the summary means that bug was found on a machine that runs lto but this bug MAY or MAY NOT BE related to lto. 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 832783 [details] build.log build log and emerge --info
Error(s) that match a know pattern in addition to what has been reported in the summary: [ ERROR ] --- Test failed with exception: Segmentation fault(11) [ LINE ] --- ./test/test_lurch_api.c:580: error: Failure!
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7f79601a3867491168d944ccfb6de3a18b0c0be3 commit 7f79601a3867491168d944ccfb6de3a18b0c0be3 Author: Florian Schmaus <flow@gentoo.org> AuthorDate: 2024-11-08 21:53:33 +0000 Commit: Florian Schmaus <flow@gentoo.org> CommitDate: 2024-11-08 21:53:33 +0000 x11-plugins/lurch net-libs/libomemo net-libs/libaxc: treeclean Signed-off-by: Florian Schmaus <flow@gentoo.org> Closes: https://bugs.gentoo.org/940725 (pkgremoved) Closes: https://bugs.gentoo.org/881373 (pkgremoved) Closes: https://bugs.gentoo.org/930527 (pkgremoved) Closes: https://bugs.gentoo.org/930528 (pkgremoved) Closes: https://bugs.gentoo.org/939759 (pkgremoved) net-libs/libaxc/Manifest | 4 - .../libaxc/files/libaxc-0.3.4-so-symlinks.patch | 25 ------ net-libs/libaxc/libaxc-0.3.4-r2.ebuild | 66 ---------------- net-libs/libaxc/libaxc-0.3.5.ebuild | 62 --------------- net-libs/libaxc/libaxc-0.3.6.ebuild | 73 ----------------- net-libs/libaxc/libaxc-0.3.7-r1.ebuild | 75 ------------------ net-libs/libaxc/libaxc-0.3.7.ebuild | 73 ----------------- net-libs/libaxc/metadata.xml | 8 -- net-libs/libomemo/Manifest | 1 - net-libs/libomemo/libomemo-0.8.1-r1.ebuild | 38 --------- net-libs/libomemo/metadata.xml | 8 -- profiles/package.mask | 9 --- x11-plugins/lurch/Manifest | 4 - ...urch-0.6.8-axc-0.3.3-libsignal-protocol-c.patch | 91 --------------------- .../files/lurch-0.6.8-libsignal-protocol-c.patch | 92 ---------------------- x11-plugins/lurch/lurch-0.6.8-r3.ebuild | 75 ------------------ x11-plugins/lurch/lurch-0.7.0-r1.ebuild | 52 ------------ x11-plugins/lurch/metadata.xml | 8 -- 18 files changed, 764 deletions(-)
