Summary: | dev-lang/julia-1.7.3 fails to compile (lto): julia_internal.h:159:26: error: type of jl_cumulative_compile_time does not match original declaration [-Werror=lto-type-mismatch] | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Gentoo Science Related Packages <sci> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jeffrey, patrick, tamiko |
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-01 20:15:27 UTC
Created attachment 789386 [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: rm: cannot remove '/var/tmp/portage/dev-lang/julia-1.7.3/work/julia-1.7.3/usr/manifest/SuiteSparse': No such file or directory /var/tmp/portage/dev-lang/julia-1.7.3/work/julia-1.7.3/src/julia_internal.h:159:26: error: type of 'jl_cumulative_compile_time' does not match original declaration [-Werror=lto-type-mismatch[https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wlto-type-mismatch]] 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=5fa56a38ce0a5ae9d983c795fe98cf2245726de1 commit 5fa56a38ce0a5ae9d983c795fe98cf2245726de1 Author: Maciej Barć <xgqt@gentoo.org> AuthorDate: 2022-07-26 21:39:19 +0000 Commit: Maciej Barć <xgqt@gentoo.org> CommitDate: 2022-07-26 21:40:47 +0000 dev-lang/julia: filter LTO (type mismatch) Closes: https://bugs.gentoo.org/855602 Signed-off-by: Maciej Barć <xgqt@gentoo.org> dev-lang/julia/julia-1.7.1-r4.ebuild | 5 ++++- dev-lang/julia/julia-1.7.3.ebuild | 5 ++++- 2 files changed, 8 insertions(+), 2 deletions(-) |