Removed the -fcf-protection gcc workaround

Required because of
https://github.com/boostorg/context/issues/263
This commit is contained in:
Anarthal (Rubén Pérez) 2025-01-03 11:36:47 +01:00 committed by GitHub
parent 41597b782a
commit 94e3d4c282
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -136,15 +136,7 @@ alias common_test_sources
# Boost.Context causes failures with warnings-as-errors
# under libc++, because it builds objects that raise a -stdlib=libc++ unused warning
alias boost_context_lib
:
/boost/context//boost_context/<warnings-as-errors>off
: usage-requirements
# gcc-13+ seem to enable CET by default, which causes warnings with Boost.Context.
# Disable CET until https://github.com/boostorg/context/issues/263 gets fixed
<toolset>gcc-13:<cxxflags>-fcf-protection=none
<toolset>gcc-14:<cxxflags>-fcf-protection=none
;
alias boost_context_lib : /boost/context//boost_context/<warnings-as-errors>off ;
# Beast and JSON depend on Container, which causes trouble with <warnings-as-errors>on
alias boost_beast_lib : /boost/beast//boost_beast/<warnings-as-errors>off ;