https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-util/valgrind-3.19.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 791849 [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: /var/tmp/portage/dev-util/valgrind-3.19.0/work/valgrind-3.19.0/memcheck/../coregrind/m_debuginfo/readdwarf3.c:5777: undefined reference to `VG_MINIMAL_LONGJMP' /var/tmp/portage/dev-util/valgrind-3.19.0/work/valgrind-3.19.0/memcheck/../coregrind/m_debuginfo/readdwarf3.c:5806: undefined reference to `VG_MINIMAL_SETJMP' /var/tmp/portage/dev-util/valgrind-3.19.0/work/valgrind-3.19.0/memcheck/../coregrind/m_gdbserver/m_gdbserver.c:771: undefined reference to `VG_MINIMAL_LONGJMP' /var/tmp/portage/dev-util/valgrind-3.19.0/work/valgrind-3.19.0/memcheck/../coregrind/m_gdbserver/server.c:1190: undefined reference to `VG_MINIMAL_SETJMP' /var/tmp/portage/dev-util/valgrind-3.19.0/work/valgrind-3.19.0/memcheck/../coregrind/m_gdbserver/server.c:1208: undefined reference to `VG_MINIMAL_SETJMP' /var/tmp/portage/dev-util/valgrind-3.19.0/work/valgrind-3.19.0/memcheck/../coregrind/m_gdbserver/utils.c:51: undefined reference to `VG_MINIMAL_LONGJMP' /var/tmp/portage/dev-util/valgrind-3.19.0/work/valgrind-3.19.0/memcheck/../coregrind/m_main.c:85: undefined reference to `memcpy' /var/tmp/portage/dev-util/valgrind-3.19.0/work/valgrind-3.19.0/memcheck/../coregrind/m_scheduler/scheduler.c:1034: undefined reference to `VG_MINIMAL_SETJMP' /var/tmp/portage/dev-util/valgrind-3.19.0/work/valgrind-3.19.0/memcheck/../coregrind/m_scheduler/scheduler.c:1211: undefined reference to `VG_MINIMAL_SETJMP' /var/tmp/portage/dev-util/valgrind-3.19.0/work/valgrind-3.19.0/memcheck/../coregrind/m_signals.c:2163: undefined reference to `VG_MINIMAL_LONGJMP' /var/tmp/portage/dev-util/valgrind-3.19.0/work/valgrind-3.19.0/memcheck/mc_leakcheck.c:1092: undefined reference to `VG_MINIMAL_SETJMP' /var/tmp/portage/dev-util/valgrind-3.19.0/work/valgrind-3.19.0/memcheck/mc_leakcheck.c:726: undefined reference to `VG_MINIMAL_LONGJMP' /var/tmp/portage/dev-util/valgrind-3.19.0/work/valgrind-3.19.0/memcheck/mc_leakcheck.c:767: undefined reference to `VG_MINIMAL_SETJMP' <artificial>:(.text+0x1ea): undefined reference to `vgPlain_interim_stack' <artificial>:(.text+0xd3): undefined reference to `vgPlain_interim_stack' collect2: error: ld returned 1 exit status
Given https://bugs.kde.org/show_bug.cgi?id=338252, even though it's "fixed", I'd say we should filter LTO here given it seems fragile on Valgrind.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ed582fd4610e4cf1b5249d7e4a6127873e601bf4 commit ed582fd4610e4cf1b5249d7e4a6127873e601bf4 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-07-31 06:29:55 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-07-31 06:29:55 +0000 dev-util/valgrind: filter LTO Closes: https://bugs.gentoo.org/858509 Signed-off-by: Sam James <sam@gentoo.org> dev-util/valgrind/valgrind-3.19.0.ebuild | 2 ++ dev-util/valgrind/valgrind-9999.ebuild | 2 ++ 2 files changed, 4 insertions(+)
*** Bug 873001 has been marked as a duplicate of this bug. ***
