https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-lang/gprolog-1.5.0 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
Created attachment 789383 [details] build.log build log and emerge --info
I'm not 100% sure that it is an lto fault. After if you dig into it, please remove the blocker bug if you think this has nothing to do with lto. Thanks
(In reply to Agostino Sarubbo from comment #2) > I'm not 100% sure that it is an lto fault. After if you dig into it, please > remove the blocker bug if you think this has nothing to do with lto. Thanks It is, see e.g. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68384.
lto_tinderbox has reproduced this issue with version 1.5.0-r1 - Updating summary.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=628886ee3e4364da8e389ba12b7c980073c6d656 commit 628886ee3e4364da8e389ba12b7c980073c6d656 Author: Eli Schwartz <eschwartz@gentoo.org> AuthorDate: 2024-09-03 22:21:43 +0000 Commit: Eli Schwartz <eschwartz@gentoo.org> CommitDate: 2024-09-05 04:07:44 +0000 dev-lang/gprolog: mark as LTO-unsafe It is using global register variables, and there's a GCC bug that makes this not work with LTO. Closes: https://bugs.gentoo.org/855599 Signed-off-by: Eli Schwartz <eschwartz@gentoo.org> dev-lang/gprolog/gprolog-1.5.0-r1.ebuild | 5 +++++ 1 file changed, 5 insertions(+)
