dev-scheme/ypsilon: mark as LTO-unsafe, strict-aliasing unsafe

If someone cares about this ancient 2008 package, there's a new 2.0.8
version from 2022 which may or may not have fixed the issue. It's a
non-trivial update and I don't do scheme.

Do enough to unblock the LTO tracker.

Closes: https://bugs.gentoo.org/858257
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
This commit is contained in:
Eli Schwartz
2024-03-17 01:39:12 -04:00
committed by Sam James
parent cae95f75ea
commit 8dce093158

View File

@@ -31,6 +31,16 @@ src_prepare() {
append-flags -pthread
# fix build with >=sys-devel/gcc-11, bug #787866
sed -i "/^CPPFLAGS/s/=/= -DNO_TLS/" Makefile
# -Werror=strict-aliasing
# https://bugs.gentoo.org/858257
#
# There is an upstream update to 2.0.8 (lotta new versions!) but it changes
# way too much to trivially update. The issue may or may not be fixed.
# Before multiple other things bombed out, the erroring source file
# *seemed* to compile ok.
append-flags -fno-strict-aliasing
filter-lto
}
src_compile() {