Boost logo

Boost :

From: Sal Pamukcu (salimp2009_at_[hidden])
Date: 2022-03-11 18:13:36


---------- Forwarded message ---------
From: <boost-request_at_[hidden]>
Date: Fri, Mar 11, 2022 at 3:00 PM
Subject: Boost Digest, Vol 6656, Issue 1
To: <boost_at_[hidden]>

Send Boost mailing list submissions to
        boost_at_[hidden]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.boost.org/mailman/listinfo.cgi/boost
or, via email, send a message with subject or body 'help' to
        boost-request_at_[hidden]

You can reach the person managing the list at
        boost-owner_at_[hidden]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Boost digest..."
The boost archives may be found at: http://lists.boost.org/Archives/boost/
Today's Topics:

   1. Re: [Graph] Attempt to resolve open issue (Anne van de Graaf)
   2. Master branch now closed for 1.79.0 beta release (Marshall Clow)
   3. [release] Boost 1.79.0 Beta 1 Release Candidate 1 is
      available (Marshall Clow)
   4. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is
      available (Marshall Clow)
   5. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is
      available (Andrey Semashev)
   6. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is
      available (Marshall Clow)
   7. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is
      available (Andrey Semashev)
   8. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is
      available (Tom Kent)
   9. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is
      available (Matt Borland)
  10. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is
      available (Andrey Semashev)

---------- Forwarded message ----------
From: Anne van de Graaf <A.vandeGraaf_at_[hidden]>
To: Jeremy Murphy <jeremy.william.murphy_at_[hidden]>
Cc: "boost_at_[hidden]" <boost_at_[hidden]>, John Maddock <
jz.maddock_at_[hidden]>
Bcc:
Date: Thu, 10 Mar 2022 13:17:37 +0000
Subject: Re: [boost] [Graph] Attempt to resolve open issue
> This is fixed on the develop branch, btw, have you verified that it works
as expected now?

Apologies for my late reply. Yes, I have verified that the fix on the
develop branch works as expected. Thank you very much for the work that you
have done.

Best regards,
Anne

On Fri, 10 Dec 2021 at 18:56, Anne van de Graaf <A.vandeGraaf_at_[hidden]
<mailto:A.vandeGraaf_at_[hidden]>> wrote:
> Hi Anne,

> which issue or pull request # is it?
Hi Jeremy,

It is issue # 268: https://github.com/boostorg/graph/issues/268

Best regards, Anne

> Jeremy

On Sun, 5 Dec 2021 at 02:20, Anne van de Graaf via Boost <
boost_at_[hidden]<mailto:boost_at_[hidden]>> wrote:
> Hello all,
>
> I am trying to get an open issue in Boost.Graph resolved. Since I haven't
received any response at the corresponding GitHub page nor from the Boost
Users mailing list (where I posted the below message last Monday), I am
reaching out to you. My aim is to get in touch with the maintainer(s) of
Boost.Graph in order to discuss what is the preferred/most efficient way to
fix the issue. Since this is my first post to this mailing list, please
accept my apologies if you feel this is not the right way to get in touch
with the maintainers. In that case, I would appreciate it very much if you
could kindly explain what I should have done instead. Please find below a
copy of my message that I sent last Monday to the Boost Users mailing list.
Thank you very much for your attention and any replies.

> Unfortunately, Graph has no current maintainer. I have done some
> maintenance on that library in the past, and I know Jeremy Murphy will
> be trying to do some this next week, so hopefully one of us can get that
> one fixed!

Thanks a lot for your reply, John. I didn't know that Boost.Graph doesn't
have a current maintainer. It would be great if you or Jeremy could do some
maintenance on it. Feel free to contact me if I can help you in any way to
get things done. We could then discuss in what way I can contribute. Thanks.

Kind regards, Anne

> Best, John.

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
Unsubscribe & other changes:
http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________
Unsubscribe & other changes:
http://lists.boost.org/mailman/listinfo.cgi/boost
---------- Forwarded message ----------
From: Marshall Clow <mclow.lists_at_[hidden]>
To: Boost Developers List <boost_at_[hidden]>
Cc:
Bcc:
Date: Thu, 10 Mar 2022 06:31:06 -0800
Subject: [boost] Master branch now closed for 1.79.0 beta release
Please do not make any commits to the master branch.
— Marshall
---------- Forwarded message ----------
From: Marshall Clow <mclow.lists_at_[hidden]>
To: Boost Developers List <boost_at_[hidden]>
Cc:
Bcc:
Date: Thu, 10 Mar 2022 07:27:19 -0800
Subject: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is
available
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
It fails on Window 11 using GCC-11.2
command line ;
b2  cxxstd=20 toolset=gcc --build-type=complete stage
here is the error message ;
FailBoost1.79.0 Beta 1 Release Candidate 1 (github.com)
<https://gist.github.com/salimp2009/854b3c74295b2487c4585be35f8bfbd0>
Salim (a new bee in devel :)
---------- Forwarded message ----------
From: Marshall Clow <mclow.lists_at_[hidden]>
To: Boost Developers List <boost_at_[hidden]>
Cc:
Bcc:
Date: Thu, 10 Mar 2022 08:03:12 -0800
Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is
available
On Mar 10, 2022, at 7:27 AM, Marshall Clow <mclow.lists_at_[hidden]> 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
---------- Forwarded message ----------
From: Andrey Semashev <andrey.semashev_at_[hidden]>
To: boost_at_[hidden]
Cc:
Bcc:
Date: Thu, 10 Mar 2022 20:17:42 +0300
Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is
available
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?
---------- Forwarded message ----------
From: Marshall Clow <mclow.lists_at_[hidden]>
To: boost_at_[hidden]
Cc:
Bcc:
Date: Thu, 10 Mar 2022 09:53:08 -0800
Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is
available
On Mar 10, 2022, at 9:17 AM, Andrey Semashev via Boost <
boost_at_[hidden]> 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
---------- Forwarded message ----------
From: Andrey Semashev <andrey.semashev_at_[hidden]>
To: boost_at_[hidden]
Cc:
Bcc:
Date: Thu, 10 Mar 2022 21:25:53 +0300
Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is
available
On 3/10/22 20:53, Marshall Clow via Boost wrote:
> On Mar 10, 2022, at 9:17 AM, Andrey Semashev via Boost <
boost_at_[hidden]> 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
---------- Forwarded message ----------
From: Tom Kent <lists_at_[hidden]>
To: Boost Developers List <boost_at_[hidden]>
Cc:
Bcc:
Date: Thu, 10 Mar 2022 15:33:30 -0600
Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is
available
On Thu, Mar 10, 2022 at 9:27 AM Marshall Clow via Boost <
boost_at_[hidden]> 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
---------- Forwarded message ----------
From: Matt Borland <matt_at_[hidden]>
To: boost_at_[hidden]
Cc:
Bcc:
Date: Fri, 11 Mar 2022 10:57:15 +0000
Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is
available
> 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
---------- Forwarded message ----------
From: Andrey Semashev <andrey.semashev_at_[hidden]>
To: boost_at_[hidden]
Cc:
Bcc:
Date: Fri, 11 Mar 2022 14:09:22 +0300
Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is
available
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.
_______________________________________________
Unsubscribe &amp; other changes:
http://lists.boost.org/mailman/listinfo.cgi/boost
-- 
Salim Pamukcu

Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk