Bug 861668 – [guru] dev-cpp/mastodonpp-0.5.7 fails to compile (lto): main.cpp:19:10: fatal error: catch.hpp: No such file or directory

• Product: GURU
• Status: RESOLVED FIXED

[Description Agostino Sarubbo 2022-07-28 08:04:31 UTC]

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

Issue: dev-cpp/mastodonpp-0.5.7 fails to compile (lto).
Discovered on: amd64 (internal ref: guru_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-07-28 08:04:33 UTC]

Created attachment 795212 [details]
build.log

build log and emerge --info

[Comment 2 Agostino Sarubbo 2022-07-28 08:04:35 UTC]

Error(s) that match a know pattern in addition to what has been reported in the summary:


/var/tmp/portage/dev-cpp/mastodonpp-0.5.7/work/mastodonpp/tests/main.cpp:19:10: fatal error: catch.hpp: No such file or directory
FAILED: tests/CMakeFiles/all_tests.dir/main.cpp.o 
/var/tmp/portage/dev-cpp/mastodonpp-0.5.7/work/mastodonpp/tests/main.cpp:19:10: fatal error: catch.hpp: No such file or directory

[Comment 3 Larry the Git Cow 2022-08-02 10:55:09 UTC]

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=07bf3c91f77f1f1be8ae4c40af34415c2d7738ee

commit 07bf3c91f77f1f1be8ae4c40af34415c2d7738ee
Author:     Ronny (tastytea) Gutbrod <[e-mail]>
AuthorDate: 2022-08-01 12:33:39 +0000
Commit:     Ronny (tastytea) Gutbrod <[e-mail]>
CommitDate: 2022-08-01 12:33:39 +0000

    dev-cpp/mastodonpp: add patch for catch 3
    
    Closes: https://bugs.gentoo.org/861668
    Signed-off-by: Ronny (tastytea) Gutbrod <[e-mail]>

 .../mastodonpp-0.5.7-add-support-for-catch-3.patch | 139 +++++++++++++++++++++
 dev-cpp/mastodonpp/mastodonpp-0.5.7-r1.ebuild      |  61 +++++++++
 2 files changed, 200 insertions(+)