[release] Boost 1.79.0 Beta 1 Release Candidate 1 is available

newer
Fwd: Boost Digest, Vol 6656, Issue...

Marshall Clow

10 Mar 2022 10 Mar '22

3:27 p.m.

are now available at: <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source> The SHA256 checksums are as follows: 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_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

Show replies by date

Marshall Clow

10 Mar 10 Mar

4:03 p.m.

On Mar 10, 2022, at 7:27 AM, Marshall Clow wrote:

...

are now available at: <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>

The SHA256 checksums are as follows:

8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_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 have successfully built the libraries: * On Mac OS 10.15, using Apple clang version 11.0.3, and and c++03/11/14/17/2a — Marshall

Andrey Semashev

5:17 p.m.

On 3/10/22 18:27, Marshall Clow via Boost wrote:

...

are now available at: <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>

The SHA256 checksums are as follows:

8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_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'm trying to download the source package now, and the download speed is terrible, ~30-60 KB/s. Is this expected?

Marshall Clow

5:53 p.m.

On Mar 10, 2022, at 9:17 AM, Andrey Semashev via Boost wrote:

...

On 3/10/22 18:27, Marshall Clow via Boost wrote:

...
are now available at: <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>

The SHA256 checksums are as follows:

8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_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'm trying to download the source package now, and the download speed is terrible, ~30-60 KB/s. Is this expected?

That’s not what I’m seeing. I’m getting > 1 MB/sec — Marshall

Andrey Semashev

6:25 p.m.

On 3/10/22 20:53, Marshall Clow via Boost wrote:

...

On Mar 10, 2022, at 9:17 AM, Andrey Semashev via Boost wrote:

...
On 3/10/22 18:27, Marshall Clow via Boost wrote:

...
are now available at: <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>

The SHA256 checksums are as follows:

8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_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'm trying to download the source package now, and the download speed is terrible, ~30-60 KB/s. Is this expected?

That’s not what I’m seeing. I’m getting > 1 MB/sec

Possibly, some regional restrictions on JFrog side? I'm not seeing bandwidth issues on other sites, including GitHub, which I assume is US based. BTW, building with gcc 11.2 in C++17 mode on Kubuntu 21.10 succeeds. There are quite a few warnings about auto_ptr being deprecated, and also some suspicious warnings about freeing non-heap-allocated objects in Boost.Wave: https://github.com/boostorg/wave/issues/159

Tom Kent

9:33 p.m.

On Thu, Mar 10, 2022 at 9:27 AM Marshall Clow via Boost < boost@lists.boost.org> wrote:

...

are now available at: <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source < https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>>

The SHA256 checksums are as follows:

8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_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

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 msvc-14.3 32 X X X msvc-14.3 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/acf919a716deeb001acaa2b4f12cb757 Tom

Matt Borland

11 Mar 11 Mar

10:57 a.m.

...

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

_______________________________________________

Boost.Filesystem fails to build using Apple Clang 13 with C++11/14/17/20 on M1 Pro Architecture. An issue has been opened here (https://github.com/boostorg/filesystem/issues/231). Matt

Andrey Semashev

11:09 a.m.

On 3/11/22 13:57, Matt Borland 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.

-- The Release Managers

_______________________________________________

Boost.Filesystem fails to build using Apple Clang 13 with C++11/14/17/20 on M1 Pro Architecture. An issue has been opened here (https://github.com/boostorg/filesystem/issues/231).

As replied in the issue, your build is picking up headers from a different Boost version in /usr/local/include.

Matt Borland

11:58 a.m.

On Friday, March 11th, 2022 at 12:09 PM, Andrey Semashev via Boost wrote:

...

On 3/11/22 13:57, Matt Borland 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.

-- The Release Managers

_______________________________________________

Boost.Filesystem fails to build using Apple Clang 13 with C++11/14/17/20 on M1 Pro Architecture. An issue has been opened here (https://github.com/boostorg/filesystem/issues/231).

As replied in the issue, your build is picking up headers from a

different Boost version in /usr/local/include.

That is my mistake. The libraries build successfully on MacOS 12.2.1 with M1 Architecture using Apple Clang 13 for C++11/14/17/20.

975

Age (days ago)

976

Last active (days ago)

List overview

Download

8 comments

4 participants

participants (4)

Andrey Semashev
Marshall Clow
Matt Borland
Tom Kent