Summary: | app-text/multitail-6.4.2-r1 fails to compile (lto): selbox.h:1:5: error: type of [-Werror=lto-type-mismatch] | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Gentoo Shell Tools project <shell-tools> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | PullRequest |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://github.com/gentoo/gentoo/pull/28089 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 618550 | ||
Attachments: | build.log |
Description
Agostino Sarubbo
![]() Created attachment 788600 [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 The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0bf5477633a6a83e1d90666fad2187a1dc608eea commit 0bf5477633a6a83e1d90666fad2187a1dc608eea Author: Pascal Jäger <pascal.jaeger@leimstift.de> AuthorDate: 2022-11-01 15:36:10 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-11-22 06:49:03 +0000 app-text/multitail: version bump to 7.0.0 - fix build for clang16 - fix build for LTO's -Werror=lto-type-mismatch Closes: https://bugs.gentoo.org/874102 Closes: https://bugs.gentoo.org/855017 Signed-off-by: Pascal Jäger <pascal.jaeger@leimstift.de> Closes: https://github.com/gentoo/gentoo/pull/28089 Signed-off-by: Sam James <sam@gentoo.org> app-text/multitail/Manifest | 1 + .../files/multitail-7.0.0-fix-clang16-build.patch | 34 ++++++++++++ .../multitail-7.0.0-fix-lto-type-mismatch.patch | 29 ++++++++++ .../multitail/files/multitail-7.0.0-gentoo.patch | 32 +++++++++++ app-text/multitail/multitail-7.0.0.ebuild | 63 ++++++++++++++++++++++ 5 files changed, 159 insertions(+) |