https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-lang/swig-4.0.2 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 789419 [details] build.log build log and emerge --info
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
https://github.com/swig/swig/commit/561a1d843d5877ec06265a6dbc96eefef5d0a945
There has been a release since the linked commit. I tested building with the -Werror flags and can't reproduce, so I think this can be closed
Yes, this is fixed. https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1efa03e16371bee79207072b135485ae7e8cdad4 commit 1efa03e16371bee79207072b135485ae7e8cdad4 Author: Sam James <sam@gentoo.org> AuthorDate: Tue Oct 25 06:43:42 2022 Commit: Sam James <sam@gentoo.org> CommitDate: Tue Oct 25 06:43:53 2022 dev-lang/swig: add 4.1.0 Signed-off-by: Sam James <sam@gentoo.org> dev-lang/swig/Manifest | 1 + dev-lang/swig/swig-4.1.0.ebuild | 46 ++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 47 insertions(+)