Summary: | dev-util/wasm3-0.5.0 fails to compile: m3_code.c:89:16: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing] | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Maciej Barć <xgqt> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | eschwartz |
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
2024-03-01 19:26:13 UTC
Created attachment 886453 [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: FAILED: source/CMakeFiles/m3.dir/m3_code.c.o FAILED: source/CMakeFiles/m3.dir/m3_compile.c.o /var/tmp/portage/dev-util/wasm3-0.5.0/work/wasm3-0.5.0/source/m3_code.c:89:16: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing] The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7fb3a58a392a84bc577f602352d3350e2896805c commit 7fb3a58a392a84bc577f602352d3350e2896805c Author: Maciej Barć <xgqt@gentoo.org> AuthorDate: 2024-03-04 00:22:34 +0000 Commit: Maciej Barć <xgqt@gentoo.org> CommitDate: 2024-03-04 01:03:30 +0000 dev-util/wasm3: filter lto and strict-aliasing Closes: https://bugs.gentoo.org/925933 Signed-off-by: Maciej Barć <xgqt@gentoo.org> dev-util/wasm3/wasm3-0.5.0.ebuild | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) https://github.com/wasm3/wasm3/commit/22fa923eefed0038ca5b4ebec0462644c119848c https://github.com/wasm3/wasm3/commit/8e2db951d61c1fbc0f96e98e6d85a45277bafc32 Maybe fixed in git? (In reply to Eli Schwartz from comment #4) > https://github.com/wasm3/wasm3/commit/ > 22fa923eefed0038ca5b4ebec0462644c119848c > https://github.com/wasm3/wasm3/commit/ > 8e2db951d61c1fbc0f96e98e6d85a45277bafc32 > > Maybe fixed in git? Yeah, looks right at a glance. |