Re: [release] Boost 1.91.0 Beta 1 Release Candidate 1 is available

Dmitry Arkhipov via Boost <[email protected]>
Newsgroups gmane.comp.lib.boost.devel
Message-ID <3935024.kQq0lBPeGt@stupidpad2>
В письме от пятница, 6 марта 2026 г. 05:39:02 MSK пользователь Marshall Clow via Boost написал:
> As always, the release managers would appreciate it if you download the
> candidate of your choice and give building it a try. Please report both
> success and failure, and anything else that is noteworthy.

I've successfully built and installed the libraries using
* Linux x86_64 with gcc-14,
* Linux x86_64 with clang-22,
* cross-compiling with Mingw-w64 11.0.1 (gcc-13, win32 threading model, 
address-model 32, 64),
* cross-compiling with GCC 13 targeting arm-linux-gnueabi

For each target I tried each of  C++ 11, 14, 17, 20, 23, and 26.

For cross-builds I had to disable Python, as I don't have versions of 
libpython for those targets.

MPI emitted a build system warning. There is a fix for this in develop since a few months ago, but it hasn't been merged to master.

GraphParallel emitted a similar warning. There isn't currently a fix for it merged into the project, so I created a PR.

Cobalt also emitted a build system warning.

Log, Python, Serialization, and Url emitted warnings when building with GCC. Additionally Process and Stacktrace emitted warnings when building for Arm and Asio (via Cobalt), Cobalt, Fiber, and Process emitted warnings when building for Windows.

Cobalt, FunctionTypes (via Log), Proto (via Log), Python, and Spirit (via Serialization) emitted warnings when building with clang.


_______________________________________________
Boost mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.boost.org/mailman3/lists/boost.lists.boost.org/
Archived at: https://lists.boost.org/archives/list/[email protected]/message/RTEOE4EDJIIXLDQYNU5GD53UBCADWEQI/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.