dev-libs/boost: exclude dodgy test in boost::system

The throws_assign_fail test is supposed to crash, but instead may or
may not even compile correctly any longer; just skip it completely.

Closes: https://bugs.gentoo.org/955831
Signed-off-by: Holger Hoffstätte <holger@applied-asynchrony.com>
Part-of: https://github.com/gentoo/gentoo/pull/42025
Signed-off-by: Sam James <sam@gentoo.org>
This commit is contained in:
Holger Hoffstätte
2025-05-11 14:46:14 +02:00
committed by Sam James
parent 926f55053d
commit 70a026bf4b
2 changed files with 17 additions and 0 deletions

View File

@@ -54,6 +54,7 @@ PATCHES=(
"${FILESDIR}"/${PN}-1.88.0-bind-no-Werror.patch
"${FILESDIR}"/${PN}-1.88.0-mysql-cstdint.patch
"${FILESDIR}"/${PN}-1.88.0-range-any_iterator.patch
"${FILESDIR}"/${PN}-1.88.0-system-crashing-test.patch
"${FILESDIR}"/${PN}-1.88.0-yap-cstdint.patch
)

View File

@@ -0,0 +1,16 @@
Do not build a supposed-to-crash test which may or may not even compile
correctly any longer.
Bug: https://bugs.gentoo.org/955831
--- boost_1_88_0/libs/system/test/Jamfile.v2~ 2025-04-03 13:37:30.000000000 +0200
+++ boost_1_88_0/libs/system/test/Jamfile.v2 2025-05-11 14:28:16.187753266 +0200
@@ -68,7 +68,7 @@ system-run before_main_test.cpp ;
run-fail throws_assign_fail.cpp : : :
# GCC 12 catches this at compile time with a warning
- <toolset>gcc,<variant>release:<build>no ;
+ <toolset>gcc:<build>no ;
system-run constexpr_test.cpp ;
system-run win32_hresult_test.cpp ;