[boost] [release] Boost 1.76.0 Beta 1 Release Candidate 1

[Marshall Clow via Boost]

The first release candidates for the 1.76.0 beta release are now available
at:

<https://dl.bintray.com/boostorg/beta/1.76.0.beta1/source/>

The SHA256 checksums are as follows:

a222d325cd3c9f66951ec9026eca6ff6f48dd563c9a025911d598d2aca8770ce
boost_1_76_0_b1_rc1.tar.bz2
6b90b510a3de38fc30a071ac798da37545fb60a1d6b21aed1130b47c9c598977
boost_1_76_0_b1_rc1.zip
b01627bd9ce934b092037da81696bb4482a44e6a31c8791dbed82eafe04b69fa
boost_1_76_0_b1_rc1.tar.gz
dbef57adbab1d4395d14000f0a2420fc82f87476e10d48359ceff7125a74b77a
boost_1_76_0_b1_rc1.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.

-- The Release managers

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

[Matt Borland via Boost]

On Thu, 2021-03-11 at 07:58 -0800, Marshall Clow via Boost wrote:
> 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.

Successfully builds on Fedora 33 using cxxstd=11,14,17,20 and GCC10
(gcc version 10.2.1 20201125 (Red Hat 10.2.1-9) (GCC)).

Matt

[Marshall Clow via Boost]

On Mar 11, 2021, at 7:58 AM, Marshall Clow <mclow...@gmail.com> wrote:
>
> The first release candidates for the 1.76.0 beta release are now available at:
>

> <https://dl.bintray.com/boostorg/beta/1.76.0.beta1/source/ <https://dl.bintray.com/boostorg/beta/1.76.0.beta1/source/>>

>
> The SHA256 checksums are as follows:
>
> a222d325cd3c9f66951ec9026eca6ff6f48dd563c9a025911d598d2aca8770ce boost_1_76_0_b1_rc1.tar.bz2
> 6b90b510a3de38fc30a071ac798da37545fb60a1d6b21aed1130b47c9c598977 boost_1_76_0_b1_rc1.zip
> b01627bd9ce934b092037da81696bb4482a44e6a31c8791dbed82eafe04b69fa boost_1_76_0_b1_rc1.tar.gz
> dbef57adbab1d4395d14000f0a2420fc82f87476e10d48359ceff7125a74b77a boost_1_76_0_b1_rc1.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 attempted to build the RC on Mac OS 10.15 using Apple clang version 11.0.3 (clang-1103.0.32.62).
I got compile errors, and Boost.Log failed to build - but the errors appeared to be from Boost.Interprocess.

Investigating…

— Marshall

[Marshall Clow via Boost]

On Mar 11, 2021, at 7:58 AM, Marshall Clow <mclow...@gmail.com> wrote:
>

> The first release candidates for the 1.76.0 beta release are now available at:
>

> <https://dl.bintray.com/boostorg/beta/1.76.0.beta1/source/ <https://dl.bintray.com/boostorg/beta/1.76.0.beta1/source/>>

>
> The SHA256 checksums are as follows:
>
> a222d325cd3c9f66951ec9026eca6ff6f48dd563c9a025911d598d2aca8770ce boost_1_76_0_b1_rc1.tar.bz2
> 6b90b510a3de38fc30a071ac798da37545fb60a1d6b21aed1130b47c9c598977 boost_1_76_0_b1_rc1.zip
> b01627bd9ce934b092037da81696bb4482a44e6a31c8791dbed82eafe04b69fa boost_1_76_0_b1_rc1.tar.gz
> dbef57adbab1d4395d14000f0a2420fc82f87476e10d48359ceff7125a74b77a boost_1_76_0_b1_rc1.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.

Successfully built the libraries on Ubuntu 18.04 using gcc 7.5.0 for C++03/11/14/17

— Marshall

[Marshall Clow via Boost]

On Mar 11, 2021, at 7:58 AM, Marshall Clow <mclow...@gmail.com> wrote:
>

> The first release candidates for the 1.76.0 beta release are now available at:
>

> <https://dl.bintray.com/boostorg/beta/1.76.0.beta1/source/ <https://dl.bintray.com/boostorg/beta/1.76.0.beta1/source/>>

>
> The SHA256 checksums are as follows:
>
> a222d325cd3c9f66951ec9026eca6ff6f48dd563c9a025911d598d2aca8770ce boost_1_76_0_b1_rc1.tar.bz2
> 6b90b510a3de38fc30a071ac798da37545fb60a1d6b21aed1130b47c9c598977 boost_1_76_0_b1_rc1.zip
> b01627bd9ce934b092037da81696bb4482a44e6a31c8791dbed82eafe04b69fa boost_1_76_0_b1_rc1.tar.gz
> dbef57adbab1d4395d14000f0a2420fc82f87476e10d48359ceff7125a74b77a boost_1_76_0_b1_rc1.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.

Successfully built the libraries on Ubuntu 18.04 using clang tip-of-tree for C++03/11/14/17/20

— Marshall

[Tom Kent via Boost]

Looks good on Windows/Visual Studio.

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 build logs can be found here:
https://gist.github.com/teeks99/57637d4b399a34c50aa16730c289267f



For the 1.76.0 release, since bintray is going away May 1, are we going to
have the primary download location be somewhere else? If so, it seems like
we'd want to do that for the beta as well, so we can give a beta-run to
whatever site we choose.

Tom

[Samuel DEBIONNE 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.

The Boost C++ Libraries were successfully built on IBM Power9 running
Ubuntu 20.04, toolset gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

- default address-model : 64-bit [1]
- default architecture : power [1]

Samuel

[Löw, Tobias (STEAG Energy Services GmbH) via Boost]

Boost libraries were built successfully on Windows Server 2016 with VS 2019 16.9.1
Command line:
.\b2.exe --toolset=msvc-14.2 variant=debug,release runtime-link=shared,static


But I get the following unpleasant warnings, when compiling my projects:

boost\concept_check.hpp(355,12): warning C4834: discarding return value of function with 'nodiscard' attribute

boost\unordered\detail\implementation.hpp(1452,7): warning C4996: 'std::allocator<T>::is_always_equal': warning STL4010: Various members of std::allocator are deprecated in C++17. Use std::allocator_traits instead of accessing these members directly. You can define _SILENCE_CXX17_OLD_ALLOCATOR_MEMBERS_DEPRECATION_WARNING or _SILENCE_ALL_CXX17_DEPRECATION_WARNINGS to acknowledge that you have received this warning.

[Marshall Clow via Boost]

On Mar 12, 2021, at 6:59 AM, Löw, Tobias (STEAG Energy Services GmbH) via Boost <bo...@lists.boost.org> wrote:
>
> Boost libraries were built successfully on Windows Server 2016 with VS 2019 16.9.1
> Command line:
> .\b2.exe --toolset=msvc-14.2 variant=debug,release runtime-link=shared,static
>
>
> But I get the following unpleasant warnings, when compiling my projects:
>
> boost\concept_check.hpp(355,12): warning C4834: discarding return value of function with 'nodiscard' attribute

This has been fixed in develop, and will be in the final release.

> boost\unordered\detail\implementation.hpp(1452,7): warning C4996: 'std::allocator<T>::is_always_equal': warning STL4010: Various members of std::allocator are deprecated in C++17. Use std::allocator_traits instead of accessing these members directly. You can define _SILENCE_CXX17_OLD_ALLOCATOR_MEMBERS_DEPRECATION_WARNING or _SILENCE_ALL_CXX17_DEPRECATION_WARNINGS to acknowledge that you have received this warning.

I have no information about this one.

— Marshall

[Glen Fernandes via Boost]

On Fri, Mar 12, 2021 at 10:17 AM Marshall Clow via Boost
<bo...@lists.boost.org> wrote:
>
> > boost\unordered\detail\implementation.hpp(1452,7): warning C4996: 'std::allocator<T>::is_always_equal': warning STL4010: Various members of std::allocator are deprecated in C++17. Use std::allocator_traits instead of accessing these members directly. You can define _SILENCE_CXX17_OLD_ALLOCATOR_MEMBERS_DEPRECATION_WARNING or _SILENCE_ALL_CXX17_DEPRECATION_WARNINGS to acknowledge that you have received this warning.
>
> I have no information about this one.
>
> — Marshall

I can take care of that one by having unordered use
boost::allocator_is_always_equal from
<boost/core/allocator_access.hpp>.

Glen

[Gregor Jasny via Boost]

Hello,

On 11.03.21 16:58, Marshall Clow via Boost wrote:
> 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 found three issues:

1) Boost interprocess does not compile on macOS. Fixed on develop with

https://github.com/boostorg/interprocess/commit/dc115156203ae2d3576326bf4ab2c6c6eb99235c
https://github.com/boostorg/interprocess/commit/3a856a0343f5432cc72d4a08ad7edba09249806c

are those automatically part of the next beta release?

2) Boost ASIO unconditionally includes regex v4 headers which conflics
with v5

Reported here:
https://github.com/chriskohlhoff/asio/issues/797

3) Boost math has enabled PCH which broke my iOS build. There I use
cxxflags="-arch armv7 -arch arm64" which clang does not like:

> clang: error: cannot use 'precompiled-header' output with multiple -arch options

I worked around with pch=off but I'm wonder what the proper build2 way
of building universal libraries is?

Thanks,
Gregor