https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: net-libs/quiche-0.14.0 fails to compile (lto). Discovered on: amd64 (internal ref: lto_tinderbox) NOTE: This machine uses lto with CFLAGS=-flto -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing 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
Created attachment 795080 [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: /usr/lib/gcc/x86_64-pc-linux-gnu/12.1.1/../../../../x86_64-pc-linux-gnu/bin/ld: ring.3929fa06-cgu.2:(.text._ZN4ring4aead3gcm7Context3new17h4641316bad79a10fE+0x230): undefined reference to `GFp_ia32cap_P' ring.3929fa06-cgu.15:(.text._ZN4ring4aead4quic12aes_init_12817h87ee8fb3fb93c1feE+0x9c): undefined reference to `GFp_ia32cap_P' ring.3929fa06-cgu.15:(.text._ZN4ring4aead4quic12aes_init_25617hcb2c6bd74ee52484E+0x9c): undefined reference to `GFp_ia32cap_P' ring.3929fa06-cgu.15:(.text._ZN4ring4aead4quic12aes_new_mask17he322cc94e0e74549E+0x17): undefined reference to `GFp_ia32cap_P' ring.3929fa06-cgu.2:(.text._ZN4ring4aead3gcm7Context3new17h4641316bad79a10fE+0x63): undefined reference to `GFp_ia32cap_P' error: linking with `x86_64-pc-linux-gnu-gcc` failed: exit status: 1
lto_tinderbox has reproduced this issue with version 0.16.0 - Updating summary.
Cannot reproduce anymore. cargo.eclass changes seem to have rendered this obsolete.