commit: 628886ee3e4364da8e389ba12b7c980073c6d656 Author: Eli Schwartz <eschwartz <AT> gentoo <DOT> org> AuthorDate: Tue Sep 3 22:21:43 2024 +0000 Commit: Eli Schwartz <eschwartz <AT> gentoo <DOT> org> CommitDate: Thu Sep 5 04:07:44 2024 +0000 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=628886ee
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 <AT> gentoo.org> dev-lang/gprolog/gprolog-1.5.0-r1.ebuild | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/dev-lang/gprolog/gprolog-1.5.0-r1.ebuild b/dev-lang/gprolog/gprolog-1.5.0-r1.ebuild index bab7b4d79adb..cb842b4a31b1 100644 --- a/dev-lang/gprolog/gprolog-1.5.0-r1.ebuild +++ b/dev-lang/gprolog/gprolog-1.5.0-r1.ebuild @@ -32,6 +32,11 @@ src_prepare() { } src_configure() { + # src/EnginePl/wam_archi.h:64:33: error: global register variable follows a function definition + # https://bugs.gentoo.org/855599 + # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68384 + filter-lto + CFLAGS_MACHINE="$(get-flag -march) $(get-flag -mcpu) $(get-flag -mtune)" use debug && append-flags -DDEBUG
