https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-python/iminuit-2.12.1 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 790460 [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: subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--config', 'Release', '-j16']' returned non-zero exit status 2. /var/tmp/portage/dev-python/iminuit-2.12.1/work/iminuit-2.12.1/src/type_caster.hpp:10:8: error: type ‘struct type_caster’ violates the C++ 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 2.16.0 - Updating summary.
lto_tinderbox has reproduced this issue with version 2.25.2 - Updating summary.
For great fun -- this package automatically builds with LTO regardless of the contents of my *FLAGS. So using filter-lto does NOT help.
commit ea21a04eebab613b0d2c8eabbea2127013ce56f8 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: Sun Aug 25 23:25:17 2024 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: Sun Aug 25 23:25:17 2024 dev-python/iminuit: Bump to 2.29.1 Signed-off-by: Michał Górny <mgorny@gentoo.org> dev-python/iminuit/Manifest | 1 + dev-python/iminuit/{iminuit-2.28.0.ebuild => iminuit-2.29.1.ebuild} | 7 +++++++ 2 files changed, 8 insertions(+) copy dev-python/iminuit/{iminuit-2.28.0.ebuild => iminuit-2.29.1.ebuild} (90%) Contains the upstream fix.
