https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: sci-electronics/geda-1.10.2-r2 fails to compile (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 795979 [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: awk: fatal: cannot open file `../../.desktop-i18n/libgeda47.LINGUAS' for reading: No such file or directory gtksheet_2_2.c:8447:25: error: 'area.y' may be used uninitialized [-Werror=maybe-uninitialized[https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wmaybe-uninitialized]]
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=12bd3b6d3f2239776739e854f01b4dbc02f3c91b commit 12bd3b6d3f2239776739e854f01b4dbc02f3c91b Author: Eli Schwartz <eschwartz93@gmail.com> AuthorDate: 2024-03-21 05:28:39 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-03-21 05:57:41 +0000 sci-electronics/geda: avoid fatal warning for maybe-uninitialized LTO makes the compiler better able to spot this. But it isn't something the entire build should fail due to, not for stable release tags of existing software. Closes: https://bugs.gentoo.org/862453 Signed-off-by: Eli Schwartz <eschwartz93@gmail.com> Signed-off-by: Sam James <sam@gentoo.org> sci-electronics/geda/geda-1.10.2-r2.ebuild | 4 ++++ 1 file changed, 4 insertions(+)
