Am 22.07.25 um 20:32 schrieb oliver.kowalke--- via Boost:
Am 22.07.25 um 14:07 schrieb Alexander Grund via Boost:
All good here too.
Just an "error" during the "configure step" which is irritating:
error: No best alternative for /dev/shm/boost_1_89_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>11 <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 matched: (empty) matched: (empty)
Unlikely worth fixing now but later as it might confuse users
Works for me (Linux x86):
Do you have MPI enabled? E.g. `using mpi;` in the project config? I guess that is what the error/warning should be about: Boost.MPI not being built. I just take issue in the build showing an (unclear) "error" but finishing nonetheless.