https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: sci-mathematics/gfan-0.6.2-r4 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 796891 [details] build.log build log and emerge --info
Really Wishing Gfan Had A Bug Tracker Today
How likely is that error to be also in the libgfan copy inside singular?
(In reply to François Bissey from comment #3) > How likely is that error to be also in the libgfan copy inside singular? There's only one way to find out... wait to see if Agostino files a bug report about singular?
I just tested it. I can reproduce the gfan error. That's my baseline. I tried singular and it came clean. One shot avoided.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=46b9cf346a38c8ac7e937bb7f83680498292dfeb commit 46b9cf346a38c8ac7e937bb7f83680498292dfeb Author: Eli Schwartz <eschwartz93@gmail.com> AuthorDate: 2024-03-21 23:57:48 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-03-22 05:31:50 +0000 sci-mathematics/gfan: mark as LTO-unsafe Closes: https://bugs.gentoo.org/863044 Signed-off-by: Eli Schwartz <eschwartz93@gmail.com> Signed-off-by: Sam James <sam@gentoo.org> sci-mathematics/gfan/gfan-0.6.2-r4.ebuild | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
