| Summary: | app-crypt/mit-krb5-1.21.2 fails to compile (lto): kadmin_ct.c:98:13: error: type of kadmin_keytab_remove does not match original declaration [-Werror=lto-type-mismatch] | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
| Component: | Current packages | Assignee: | Gentoo Kerberos Maintainers <kerberos> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | anthonyryan1, gentoo, kocelfc, lg3dx6fd |
| 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-06-25 08:26:32 UTC
Created attachment 787568 [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 reproducible with =app-crypt/mit-krb5-1.20.1::gentoo lto_tinderbox has reproduced this issue with version 1.21.2 - Updating summary. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=953dc612be2c7c96ef5a5d1f0160253f0485e3c8 commit 953dc612be2c7c96ef5a5d1f0160253f0485e3c8 Author: Sam James <sam@gentoo.org> AuthorDate: 2024-03-01 03:41:02 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-03-01 03:41:58 +0000 app-crypt/mit-krb5: filter LTO Suffers from lto-type-mismatch. The codebase is pretty old. Closes: https://bugs.gentoo.org/854225 Signed-off-by: Sam James <sam@gentoo.org> app-crypt/mit-krb5/mit-krb5-1.21.2.ebuild | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) Also, Eli attempted to report this one upstream but it's stuck in mail purgatory. |
