On 4/12/23 01:02, Marshall Clow wrote:

On Apr 11, 2023, at 2:17 PM, Andrey Semashev via Boost wrote:

...

On 4/10/23 17:36, Marshall Clow via Boost wrote:

...

The second release candidates for the 1.82.0 release are now available at: <https://boostorg.jfrog.io/artifactory/main/release/1.82.0/source/ https://boostorg.jfrog.io/artifactory/main/release/1.82.0/source/>

There is only one change from RC1 - a fix to ASIO that caused some compile failures. Thanks to Ruben Perez for the report, and to Chris for the fix.

The SHA256 checksums are as follows:

66a469b6e608a51f8347236f4912e27dc5c60c60d7d53ae9bfe4683316c6f04c boost_1_82_0_rc2.tar.gz f7c9e28d242abcd7a2c1b962039fcdd463ca149d1883c3a950bbcc0ce6f7c6d9 boost_1_82_0_rc2.zip a6e1ab9b0860e6a2881dd7b21fe9f737a095e5f33a3a874afc6a345228597ee6 boost_1_82_0_rc2.tar.bz2 e72ff100482d4b371327b6c550dbd244d49c0186860ccc3b8c093dd621537e39 boost_1_82_0_rc2.7z

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 would like the following last minute fix to be merged to Boost.Filesystem master:

https://github.com/boostorg/filesystem/commit/176fce8e4d2016e864a0b9193cc4e9...

This should fix compilation on OpenBSD due to broken -Wl,--no-undefined flag on this platform.

This problem was reported very late:

https://github.com/boostorg/filesystem/issues/283

Is this a new problem in this release?

Yes.