Am 06.11.25 um 23:43 schrieb Marshall Clow via Boost:
The first release candidates for the 1.90.0 Beta 1 release are now available at: <https://archives.boost.io/beta/1.90.0.beta1/source/>
Builds fine with GCC 13.2, 13.3, 14.2 on Rocky 9.6 w/ AMD EPYC No blocker but 2 noteworthy issues: Confusing when MPI isn't explicitly enabled:
error: No best alternative for /dev/shm/boost_1_90_0/libs/mpi/build/boost_mpi with <abi>sysv <address-model>64 <architecture>x86 <asynch-exceptions>off <binary-format>elf <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <boost.cobalt.executor>any_io_executor <boost.cobalt.pmr>std <context-impl>fcontext <coverage>off <cxxstd-dialect>iso <cxxstd>14 <debug-symbols>on <exception-handling>on <extern-c-nothrow>off <inlining>off <known-warnings>hide <link>shared <optimization>off <os>LINUX <pch>on <preserve-test-targets>on <profiling>off <python-debugging>off <python>3.9 <rtti>on <runtime-debugging>on <runtime-link>shared <stdlib>native <strip>off <target-os>linux <testing.execute>on <threadapi>pthread <threading>multi <toolset-gcc:version>13 <toolset>gcc <variant>debug <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <x-deduced-platform>x86_64
a) Unusual message contrary to our usual b2 behavior: If requirement (e.g. C++ standard) is missing, don't build. b) "error" but build continues fine, just without Boost.MPI Similar for Boost Python:
./boost/python/detail/wrap_python.hpp:57:11: fatal error: pyconfig.h: No such file or directory 57 | # include <pyconfig.h> | ^~~~~~~~~~~~ It autodetected a system Python without dev-headers.