Bug 879169 – sci-mathematics/alectryon-1.4.0-r2 [doc] fails to compile - AssertionError

• Product: Gentoo Linux
• Status: CONFIRMED ---

[Description Agostino Sarubbo 2022-11-02 13:44:44 UTC]

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: sci-mathematics/alectryon-1.4.0-r1 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

[Comment 1 Agostino Sarubbo 2022-11-02 13:44:46 UTC]

Created attachment 826697 [details]
build.log

build log and emerge --info

[Comment 2 Agostino Sarubbo 2022-11-02 13:44:48 UTC]

Error(s) that match a know pattern:


AssertionError: \PYG{k+kn}{Compute} \PYG{o}{((}\PYG{k+kr}{fun} \PYG{o}{(}\PYG{+nv}{n}\PYG{o}{:} nat\PYG{o}{)} \PYG{o}{(}\PYG{+nv}{opt}\PYG{o}{:} option nat\PYG{o}{)} \PYG{o}{(}\PYG{+nv}{eq}\PYG{o}{:} opt \PYG{o}{=} Some n\PYG{o}{)} \PYG{o}{=\PYGZgt{}} n\PYG{o}{)}

[Comment 3 Maciej Barć 2022-11-03 00:22:45 UTC]

>  File "/var/tmp/portage/sci-mathematics/alectryon-1.4.0-r1/work/alectryon-1.4.0/alectryon/pygments.py", line 198, in highlight_latex

This is most likely a documentation build error.
Removing lto blocker.

[Comment 4 Agostino Sarubbo 2024-04-30 07:05:40 UTC]

ci has reproduced this issue with version 1.4.0-r2 - Updating summary.