Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 879513 - sci-visualization/labplot-2.9.0-r1 fails tests (LTO-SYSTEM)
Summary: sci-visualization/labplot-2.9.0-r1 fails tests (LTO-SYSTEM)
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Andreas K. Hüttel
URL:
Whiteboard: lto
Keywords:
Depends on:
Blocks: lto
  Show dependency tree
 
Reported: 2022-11-04 05:21 UTC by Agostino Sarubbo
Modified: 2023-07-12 13:35 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log.xz (build.log.xz,39.29 KB, application/x-xz)
2022-11-04 05:21 UTC, Agostino Sarubbo
Details
1-LastTest.log.xz (1-LastTest.log.xz,118.46 KB, application/x-xz)
2022-11-04 05:21 UTC, Agostino Sarubbo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2022-11-04 05:21:08 UTC
https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: sci-visualization/labplot-2.9.0-r1 fails tests (LTO-SYSTEM).
Discovered on: amd64 (internal ref: lto_tinderbox)

NOTE:
(LTO-SYSTEM) in the summary means that bug was found on a machine that runs lto but this bug MAY or MAY NOT BE related to lto.

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 gentoo-dev 2022-11-04 05:21:11 UTC
Created attachment 826903 [details]
build.log.xz

build log and emerge --info (compressed because it exceeds attachment limit, use 'xzless' to read it)
Comment 2 Agostino Sarubbo gentoo-dev 2022-11-04 05:21:14 UTC
Created attachment 826905 [details]
1-LastTest.log.xz

1-LastTest.log (compressed because it exceeds attachment limit, use 'xzless' to read it)
Comment 3 Agostino Sarubbo gentoo-dev 2022-11-04 05:21:16 UTC
Error(s) that match a know pattern:


	  9 - ParserTest (Failed)
	 19 - ReadStatFilterTest (Failed)
-- Could NOT find KF5Parts (missing: KF5Parts_DIR)
-- Could NOT find KF5Parts: found neither KF5PartsConfig.cmake nor kf5parts-config.cmake 
-- Could NOT find Poppler (missing: Qt5) (found suitable version "22.10.0", minimum required is "0.62.0")
-- Could NOT find Poppler_Qt5 (missing: Poppler_Qt5_LIBRARY Poppler_Qt5_INCLUDE_DIR) (found version "")
fatal: not a git repository (or any parent up to mount point /var/tmp)
Comment 4 luzpaz 2023-07-12 13:25:11 UTC
Note, current stable is 2.10.1 https://bugs.gentoo.org/910259
Is this issue still reproducible ?
Comment 5 Andrew Ammerlaan gentoo-dev 2023-07-12 13:35:06 UTC
(In reply to luzpaz from comment #4)
> Note, current stable is 2.10.1 https://bugs.gentoo.org/910259
> Is this issue still reproducible ?

yeah the test still fails