https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: gui-apps/eww-0.3.0 fails to compile (lto). Discovered on: amd64 (internal ref: guru_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 797017 [details] build.log build log and emerge --info
it happens on non-lto as well
guru_ci has reproduced this issue with version 0.4.0 - Updating summary.
This commit will fix this: https://github.com/gentoo/guru/commit/a25082b184e7867c4fffaee69e22996dce1a8ef1 This is because the old ebuild does not require rust[nightly] USE-flag, yet eww needs that to compile. Once we drop 0.4.0 this bug should be closed.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=e677aba9653d7a6ea8fb283605f75590ca6ec019 commit e677aba9653d7a6ea8fb283605f75590ca6ec019 Author: Gonçalo Negrier Duarte <gonegrier.duarte@gmail.com> AuthorDate: 2024-02-25 13:25:15 +0000 Commit: Gonçalo Negrier Duarte <gonegrier.duarte@gmail.com> CommitDate: 2024-02-25 13:31:59 +0000 gui-apps/eww: drop 0.5.0, add 0.5.0-r1 * improve how features are enable using cargo.eclass * fix SRC_URI 0.5.0 * improving src_unpack (not sure is really need but just to be safe) * closing old bug of 0.4.0 since was drop Closes: https://bugs.gentoo.org/925317 Closes: https://bugs.gentoo.org/925426 Closes: https://bugs.gentoo.org/884457 Closes: https://bugs.gentoo.org/884455 Closes: https://bugs.gentoo.org/877675 Closes: https://bugs.gentoo.org/863095 Signed-off-by: Gonçalo Negrier Duarte <gonegrier.duarte@gmail.com> .../eww/{eww-0.5.0.ebuild => eww-0.5.0-r1.ebuild} | 35 +++++++++++++--------- gui-apps/eww/eww-9999.ebuild | 35 +++++++++++++--------- 2 files changed, 42 insertions(+), 28 deletions(-)
