On Thu, Apr 9, 2020 at 6:36 AM Marshall Clow wrote:

I have built this with the following configurations: Ubuntu 18.04 with gcc 7.3.2: Successful build with C++03/11/14/17

Ubuntu 18.04 with clang trunk: Successful build with C++03/11/14/17

Boost.Wave failed to build with clang trunk and '-std=c++2a'

The Boost.Wave problem is https://github.com/boostorg/wave/issues/84 -- Marshall

There's fix for the aforementioned warning issue in date-time on develop. My RC compile test report: 2 platforms, 5 compilers, 5 c++ versions - All successfully compile, so pretty solid - All compilers in agreement the locale library has deprecated auto_ptr with copious warnings (most of the ~95 warnings on g++ compiles) - Warnings go up to ~255 on g++ with 98 due to math deprecation warning - Build system still incorrectly detects python on Mint when header is not available (old ticket is closed - I installed dev package to fix) Mint5 - 5.0.0-32-generic #34~18.04.2-Ubuntu SMP Thu Oct 10 10:36:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux g++9.2 (2a, 17, 14, 11, 98) g++7.5 (17, 14, 11, 98) clang6.0.0 (17, 14, 11, 98) RedHat8.1 - 4.18.0-147.5.1.el8_1.x86_64 #1 SMP Tue Jan 14 15:50:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux g++9.1.1 (2a, 17, 14, 11, 98) g++8.3.1 (17, 14, 11, 98) On Fri, Apr 10, 2020 at 6:23 AM Jeff Garland wrote:

There's a report of new date_time warnings in RC with MSVC 17 at warning 4 submitted today -- working on a trivial/safe fix for it now.

https://github.com/boostorg/date_time/issues/148

On Fri, Apr 10, 2020 at 5:38 AM Tom Kent via Boost wrote:

...

On Thu, Apr 9, 2020 at 1:20 AM Marshall Clow via Boost-users < boost-users@lists.boost.org> wrote:

...

The release candidates for the first 1.73.0 beta release are now available at: https://dl.bintray.com/boostorg/beta/1.73.0.beta.1/source/

The release notes are not yet available.

The SHA256 checksums are as follows: 44f323b42c4375ab3751b67ac5ce53ba5267af20cf375be75675d8952d3cca4e ./boost_1_73_0_b1_rc1.7z 5270fa89243a3508331bd3773800de6d2f98d1f160b95e362fa8269d9cd58773 ./boost_1_73_0_b1_rc1.tar.bz2 82ffcd4a2e558a31f1ddd6a54ef6c00dae28b95c2ddee575c285544085dcb004 ./boost_1_73_0_b1_rc1.tar.gz 910b7560ee239472cc69e6a0c680dc4d9d7ea234faad807738ec98e4811c63d4 ./boost_1_73_0_b1_rc1.zip

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.

-- The Boost Release Managers

Generally looks good on Windows/Visual Studio. However, it took me three tries to get here. My first two builds stalled out during the build. I didn't pay attention to where the first one stopped, but the second was in the build for wave, no failure just the build stopped on a compile step. I believe this only happened with msvc-14.2 - 32 bit.

After a couple restarts I was able to build without issues:

toolset arch compile Link Execute msvc-10.0 32 X X X msvc-10.0 64 X X X msvc-11.0 32 X X X msvc-11.0 64 X X X msvc-12.0 32 X X X msvc-12.0 64 X X X msvc-14.0 32 X X X msvc-14.0 64 X X X msvc-14.1 32 X X X msvc-14.1 64 X X X msvc-14.2 32 X X X msvc-14.2 64 X X X

Compile means that the b2 command completed without errors Link means that visual studio was able to link a sample executable to a library (libboost_thread-vcXXX-mt[-gd]-1_XX.lib) generated Execute means that the linked program executed without errors.

Full logs are available here: https://gist.github.com/teeks99/f4066721729a12403a8bf6f0499d7633

Tom

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost