Bug 872989 – dev-util/autoproject-0.20_p5 fails tests (lto): getopt_core.h:91:12: error: declaration of int getopt(int, char const, const char) noexcept has a different exception specifier

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Agostino Sarubbo 2022-09-26 08:51:41 UTC]

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

Issue: dev-util/autoproject-0.20_p5 fails tests (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-09-26 08:51:44 UTC]

Created attachment 814195 [details]
build.log

build log and emerge --info

[Comment 2 Agostino Sarubbo 2022-09-26 08:51:46 UTC]

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


FAIL: chk
FAIL: chkag
FAIL: chkar
FAIL: chkcc
FAIL: chkclig
make[3]: autogen: No such file or directory
make[3]: clig: No such file or directory
/usr/include/bits/getopt_core.h:91:12: error: declaration of ‘int getopt(int, char* const*, const char*) noexcept’ has a different exception specifier

[Comment 3 Larry the Git Cow 2024-03-15 02:20:17 UTC]

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

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=01e19560620d39e0ab0ada96d7b12b21f80b950e

commit 01e19560620d39e0ab0ada96d7b12b21f80b950e
Author:     Sam James <[e-mail]>
AuthorDate: 2024-03-15 02:19:16 +0000
Commit:     Sam James <[e-mail]>
CommitDate: 2024-03-15 02:19:39 +0000

    dev-util/autoproject: add 0.20_p15
    
    Closes: https://bugs.gentoo.org/296630
    Closes: https://bugs.gentoo.org/631312
    Closes: https://bugs.gentoo.org/632255
    Closes: https://bugs.gentoo.org/872989
    Closes: https://bugs.gentoo.org/898578
    Signed-off-by: Sam James <[e-mail]>

 dev-util/autoproject/Manifest                      |  1 +
 dev-util/autoproject/autoproject-0.20_p15.ebuild   | 54 ++++++++++++++++++++++
 ...ect-0.20_p15-getopt-cxx-conflict-noexcept.patch | 12 +++++
 3 files changed, 67 insertions(+)