Summary: | dev-libs/libcroco-0.6.13-r1 fails to compile (lto): csslint.c:458:55: error: dereferencing type-punned pointer might break strict-aliasing rules [-Werror=strict-aliasing] | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 618550 | ||
Attachments: | build.log |
Description
Agostino Sarubbo
2022-07-02 09:35:20 UTC
Created attachment 789455 [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=d9dce45487c3a80c68400fb690e86faaa4afe48f commit d9dce45487c3a80c68400fb690e86faaa4afe48f Author: Sam James <sam@gentoo.org> AuthorDate: 2024-03-11 22:52:41 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-03-11 22:53:14 +0000 dev-libs/libcroco: filter LTO, no-SA Archived upstream and a complicated situation with all the bundled copies too.. Closes: https://bugs.gentoo.org/855704 Signed-off-by: Sam James <sam@gentoo.org> dev-libs/libcroco/libcroco-0.6.13-r1.ebuild | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) |