https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-util/lldb-14.0.6 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 791750 [details] build.log.xz build log and emerge --info (compressed because it exceeds attachment limit, use 'xzless' to read it)
Error(s) that match a know pattern in addition to what has been reported in the summary: -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE) -- Could NOT find Lua (missing: LUA_LIBRARIES LUA_INCLUDE_DIR) (Required is exact version "5.3") -- Could NOT find LuaAndSwig (missing: LUA_LIBRARIES LUA_INCLUDE_DIR) FAILED: bin/lldb-server FAILED: lib64/liblldb.so.14.0.6 /var/tmp/portage/dev-util/lldb-14.0.6/work/lldb/include/lldb/Utility/Cloneable.h:40: error: virtual table of type ‘struct Cloneable’ violates one definition rule [-Werror=odr]
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
lto_tinderbox has reproduced this issue with version 15.0.1 - Updating summary.
Created attachment 882966 [details] build.log gcc + lto . Seems to be more verbose than original build log. Reproducible with =dev-debug/lldb-17.0.6
Reported upstream: https://github.com/llvm/llvm-project/issues/83636.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=127dc03a3c8fa58347375f41795635594a47b2c6 commit 127dc03a3c8fa58347375f41795635594a47b2c6 Author: Sam James <sam@gentoo.org> AuthorDate: 2024-03-07 18:54:09 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-03-07 18:54:09 +0000 dev-debug/lldb: filter LTO (ODR violations) Bug: https://github.com/llvm/llvm-project/issues/83636 Bug: https://bugs.gentoo.org/914354 Closes: https://bugs.gentoo.org/858389 Signed-off-by: Sam James <sam@gentoo.org> dev-debug/lldb/lldb-15.0.7.ebuild | 5 ++++- dev-debug/lldb/lldb-16.0.6-r1.ebuild | 5 ++++- dev-debug/lldb/lldb-16.0.6.ebuild | 5 ++++- dev-debug/lldb/lldb-17.0.6.ebuild | 5 ++++- dev-debug/lldb/lldb-18.1.0.ebuild | 5 ++++- dev-debug/lldb/lldb-19.0.0.9999.ebuild | 5 ++++- dev-debug/lldb/lldb-19.0.0_pre20240302.ebuild | 5 ++++- 7 files changed, 28 insertions(+), 7 deletions(-)
