https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: media-gfx/blender-2.93.9 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 792689 [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 Clang (missing: _CLANG_LIBRARIES CLANG_INCLUDE_DIR) FAILED: bin/blender /var/tmp/portage/media-gfx/blender-2.93.9/work/blender-2.93.9/source/blender/makesdna/DNA_image_types.h:135:16: error: type ‘struct Image’ violates the C++ One Definition Rule [-Werror=odr]
I'm guessing the `-Werror` defines are because these warning will cause issue when doing link time optimization? If that is the case, this seems to be an issue for upstream and not the ebuild itself?
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
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=df523208fa8693f7a79da43a7d2283414c7ba9b4 commit df523208fa8693f7a79da43a7d2283414c7ba9b4 Author: Eli Schwartz <eschwartz93@gmail.com> AuthorDate: 2024-04-09 22:32:51 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-04-09 23:00:43 +0000 media-gfx/blender: mark as LTO-unsafe Closes: https://bugs.gentoo.org/859607 Signed-off-by: Eli Schwartz <eschwartz93@gmail.com> Signed-off-by: Sam James <sam@gentoo.org> media-gfx/blender/blender-3.3.15.ebuild | 5 +++++ media-gfx/blender/blender-3.3.6-r1.ebuild | 5 +++++ media-gfx/blender/blender-3.3.8.ebuild | 5 +++++ media-gfx/blender/blender-3.6.0.ebuild | 5 +++++ media-gfx/blender/blender-3.6.5.ebuild | 5 +++++ media-gfx/blender/blender-3.6.8.ebuild | 5 +++++ media-gfx/blender/blender-4.0.1-r1.ebuild | 5 +++++ media-gfx/blender/blender-4.0.2.ebuild | 5 +++++ media-gfx/blender/blender-9999.ebuild | 5 +++++ 9 files changed, 45 insertions(+)
