[release] Boost 1.70.0 Release Candidate 1 available
The release candidates for the 1.70.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.70.0/source/> The SHA256 checksums are as follows: 6e5cba1269225395bb5e78dda48441ccadaf745e42638180015e9e6257068336 ./boost_1_70_0_rc1.7z 35d8e1361e2063f70aa3a6ca0dd8af0877ceb75477ebbd2c726bb1d039658c7a ./boost_1_70_0_rc1.tar.bz2 ec8ddbbee2fd61e2f78a1dfe9a07ad83ca8f6a2f4c704d6f297d89c6afdc4f2c ./boost_1_70_0_rc1.tar.gz ee2c3b97ce10f85a31b6a105ad8edf1c20fb4b936c9a6e6008206059cb98ab1b ./boost_1_70_0_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
On Thu, Apr 4, 2019 at 7:27 AM Marshall Clow <mclow.lists@gmail.com> wrote:
The release candidates for the 1.70.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.70.0/source/>
The SHA256 checksums are as follows: 6e5cba1269225395bb5e78dda48441ccadaf745e42638180015e9e6257068336 ./boost_1_70_0_rc1.7z 35d8e1361e2063f70aa3a6ca0dd8af0877ceb75477ebbd2c726bb1d039658c7a ./boost_1_70_0_rc1.tar.bz2 ec8ddbbee2fd61e2f78a1dfe9a07ad83ca8f6a2f4c704d6f297d89c6afdc4f2c ./boost_1_70_0_rc1.tar.gz ee2c3b97ce10f85a31b6a105ad8edf1c20fb4b936c9a6e6008206059cb98ab1b ./boost_1_70_0_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.
I got tired of the 'register' warnings in the python headers, and added '-Wno-register' to my user-config.jam. Given that, I have successfully 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 built from trunk: Successful build with C++03/11/14/17/2a -- Marshall
On Thu, Apr 4, 2019 at 10:03 AM Marshall Clow <mclow.lists@gmail.com> wrote:
On Thu, Apr 4, 2019 at 7:27 AM Marshall Clow <mclow.lists@gmail.com> wrote:
The release candidates for the 1.70.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.70.0/source/>
The SHA256 checksums are as follows: 6e5cba1269225395bb5e78dda48441ccadaf745e42638180015e9e6257068336 ./boost_1_70_0_rc1.7z 35d8e1361e2063f70aa3a6ca0dd8af0877ceb75477ebbd2c726bb1d039658c7a ./boost_1_70_0_rc1.tar.bz2 ec8ddbbee2fd61e2f78a1dfe9a07ad83ca8f6a2f4c704d6f297d89c6afdc4f2c ./boost_1_70_0_rc1.tar.gz ee2c3b97ce10f85a31b6a105ad8edf1c20fb4b936c9a6e6008206059cb98ab1b ./boost_1_70_0_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.
I got tired of the 'register' warnings in the python headers, and added '-Wno-register' to my user-config.jam. Given that, I have successfully 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 built from trunk: Successful build with C++03/11/14/17/2a
Mac OS X 10.14.3 with Apple Clang 10: Successful build with C++03/11/14/17/2a Mac OS X 10.14.3 with clang built from trunk: Successful build with C++03/11/14/17/2a -- Marshall
On Thu, Apr 4, 2019 at 9:27 AM Marshall Clow via Boost-users < boost-users@lists.boost.org> wrote:
The release candidates for the 1.70.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.70.0/source/>
The SHA256 checksums are as follows: 6e5cba1269225395bb5e78dda48441ccadaf745e42638180015e9e6257068336 ./boost_1_70_0_rc1.7z 35d8e1361e2063f70aa3a6ca0dd8af0877ceb75477ebbd2c726bb1d039658c7a ./boost_1_70_0_rc1.tar.bz2 ec8ddbbee2fd61e2f78a1dfe9a07ad83ca8f6a2f4c704d6f297d89c6afdc4f2c ./boost_1_70_0_rc1.tar.gz ee2c3b97ce10f85a31b6a105ad8edf1c20fb4b936c9a6e6008206059cb98ab1b ./boost_1_70_0_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.
Windows/Visual Studio (msvc 10.0, 11.0, 12.0, 14.0, 14.1) builds look good. 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 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 at: https://gist.github.com/teeks99/798df332c12ec98708e3710da35dd606 Tom
On Thu, Apr 4, 2019 at 9:27 AM Marshall Clow via Boost-users < boost-users@lists.boost.org> wrote:
The release candidates for the 1.70.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.70.0/source/>
The SHA256 checksums are as follows: 6e5cba1269225395bb5e78dda48441ccadaf745e42638180015e9e6257068336 ./boost_1_70_0_rc1.7z 35d8e1361e2063f70aa3a6ca0dd8af0877ceb75477ebbd2c726bb1d039658c7a ./boost_1_70_0_rc1.tar.bz2 ec8ddbbee2fd61e2f78a1dfe9a07ad83ca8f6a2f4c704d6f297d89c6afdc4f2c ./boost_1_70_0_rc1.tar.gz ee2c3b97ce10f85a31b6a105ad8edf1c20fb4b936c9a6e6008206059cb98ab1b ./boost_1_70_0_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
Building with msvc-14.2 seemed okay, but when I went to link the libaries the auto-library feature wasn't working. The build correctly generated "libboost_thread-vc142-mt-gd-x32-1_70.lib", but the auto-lib wanted "libboost_thread-vc141-mt-gd-x32-1_70.lib".
On Thu, Apr 4, 2019 at 7:28 AM Marshall Clow via Boost-users <boost-users@lists.boost.org> wrote:
Please report both success and failure, and anything else that is noteworthy.
A user reported a significant defect which renders the async_base utility largely unusable, if another release candidate is created I would like to incorporate the fix, which is here: <https://github.com/boostorg/beast/commit/ce986118f81443ea8947f4bfa32ea74002750451> Thanks
On 04.04.19 16:27, Marshall Clow via Boost-users 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.
boost::movelib::adaptive_merge continues to be broken if iterator_traits<RandIt>::size_type != std::size_t. This breaks boost::container::flat_map when cross-compiling for MacOS. I have previously reported this error here. I consider this a critical error - as in, I won't be able to upgrade to Boost 1.70 at all unless this error is fixed for the release. -- Rainer Deyke (rainerd@eldwood.com)
On Sat, Apr 6, 2019 at 10:53 AM Rainer Deyke via Boost-users < boost-users@lists.boost.org> wrote:
On 04.04.19 16:27, Marshall Clow via Boost-users 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.
boost::movelib::adaptive_merge continues to be broken if iterator_traits<RandIt>::size_type != std::size_t. This breaks boost::container::flat_map when cross-compiling for MacOS. I have previously reported this error here.
I consider this a critical error - as in, I won't be able to upgrade to Boost 1.70 at all unless this error is fixed for the release.
This is https://github.com/boostorg/move/issues/25, correct? -- Marshall
On 07.04.19 14:13, Marshall Clow via Boost-users wrote:
On Sat, Apr 6, 2019 at 10:53 AM Rainer Deyke via Boost-users < boost-users@lists.boost.org> wrote:
On 04.04.19 16:27, Marshall Clow via Boost-users 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.
boost::movelib::adaptive_merge continues to be broken if iterator_traits<RandIt>::size_type != std::size_t. This breaks boost::container::flat_map when cross-compiling for MacOS. I have previously reported this error here.
I consider this a critical error - as in, I won't be able to upgrade to Boost 1.70 at all unless this error is fixed for the release.
This is https://github.com/boostorg/move/issues/25, correct?
Yes. -- Rainer Deyke (rainerd@eldwood.com)
Also, unfortunately, https://github.com/boostorg/geometry/issues/566 is still present in the RC. Barend assured me the fix was already in Beta1; seeing as there are no notes for Boost.Geometry in the release, I’m wondering if the release process is actually skipping some portions of the codebase on purpose... El 7 abr. 2019, a la(s) 07:07, Rainer Deyke via Boost-users <boost-users@lists.boost.org> escribió:
On 07.04.19 14:13, Marshall Clow via Boost-users wrote:
On Sat, Apr 6, 2019 at 10:53 AM Rainer Deyke via Boost-users < boost-users@lists.boost.org> wrote:
On 04.04.19 16:27, Marshall Clow via Boost-users 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.
boost::movelib::adaptive_merge continues to be broken if iterator_traits<RandIt>::size_type != std::size_t. This breaks boost::container::flat_map when cross-compiling for MacOS. I have previously reported this error here.
I consider this a critical error - as in, I won't be able to upgrade to Boost 1.70 at all unless this error is fixed for the release.
This is https://github.com/boostorg/move/issues/25, correct?
Yes.
-- Rainer Deyke (rainerd@eldwood.com)
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users
On Sun, 7 Apr 2019 at 18:41, Heriberto Delgado via Boost-users <boost-users@lists.boost.org> wrote:
Also, unfortunately, https://github.com/boostorg/geometry/issues/566 is still present in the RC. Barend assured me the fix was already in Beta1; seeing as there are no notes for Boost.Geometry in the release, I’m wondering if the release process is actually skipping some portions of the codebase on purpose...
FYI, Adam has moved this issue to Boost 1.71 https://github.com/boostorg/geometry/issues/566#event-2249823632 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
On 07/04/2019 15:07, Rainer Deyke via Boost-users wrote:
On 07.04.19 14:13, Marshall Clow via Boost-users wrote:
On Sat, Apr 6, 2019 at 10:53 AM Rainer Deyke via Boost-users < boost-users@lists.boost.org> wrote:
On 04.04.19 16:27, Marshall Clow via Boost-users 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.
boost::movelib::adaptive_merge continues to be broken if iterator_traits<RandIt>::size_type != std::size_t. This breaks boost::container::flat_map when cross-compiling for MacOS. I have previously reported this error here.
I consider this a critical error - as in, I won't be able to upgrade to Boost 1.70 at all unless this error is fixed for the release.
This is https://github.com/boostorg/move/issues/25, correct?
Yes.
Sorry for note replying earlier, I was on a trip. The fix is not complicated but several files need to be modified. Committed to develop: https://github.com/boostorg/move/commit/bfdfca0b88fe1cf4e67b42fcacd5e126e937... @Rainer: I've checked this fix in several msvc and gcc's locally. The error report does not contain any example for the bug, so I don't know if I've fixed your use case. I don't know if we are still on time for 1.70. Best, Ion
On Mon, Apr 8, 2019 at 12:36 AM Ion Gaztañaga via Boost < boost@lists.boost.org> wrote:
On 07/04/2019 15:07, Rainer Deyke via Boost-users wrote:
On 07.04.19 14:13, Marshall Clow via Boost-users wrote:
On Sat, Apr 6, 2019 at 10:53 AM Rainer Deyke via Boost-users < boost-users@lists.boost.org> wrote:
On 04.04.19 16:27, Marshall Clow via Boost-users 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.
boost::movelib::adaptive_merge continues to be broken if iterator_traits<RandIt>::size_type != std::size_t. This breaks boost::container::flat_map when cross-compiling for MacOS. I have previously reported this error here.
I consider this a critical error - as in, I won't be able to upgrade to Boost 1.70 at all unless this error is fixed for the release.
This is https://github.com/boostorg/move/issues/25, correct?
Yes.
Sorry for note replying earlier, I was on a trip. The fix is not complicated but several files need to be modified. Committed to develop:
https://github.com/boostorg/move/commit/bfdfca0b88fe1cf4e67b42fcacd5e126e937...
@Rainer: I've checked this fix in several msvc and gcc's locally. The error report does not contain any example for the bug, so I don't know if I've fixed your use case.
I don't know if we are still on time for 1.70.
That's a more involved fix than I expected. [ and there's a typo in your docs now: "daptive_merge" ] How are the test bots looking? -- Marshall
On 08/04/2019 6:47, Marshall Clow wrote:
That's a more involved fix than I expected. [ and there's a typo in your docs now: "daptive_merge" ]
How are the test bots looking? -- Marshall
Few have cycled. Runners in the develop branch with date "Mon, 08" look ok in Move and Container. I've committed (also in develop) the fix for the typo. Ion
On Sun, Apr 7, 2019 at 9:47 PM Marshall Clow via Boost-users <boost-users@lists.boost.org> wrote:
How are the test bots looking?
Truth be told, they are looking worse for wear and could probably use a vacation to recharge, or perhaps some medical leave. In the meanwhile, you won't believe this - it is actually a rather funny story. Or short story rather, so.... ...it turns out, a user reported another eensy weensy tiny little buggy, this annoying duplicate function template definition problem that happens with friend function templates the fix for which is here: <https://github.com/vinniefalco/beast/commit/1de60a046292dcd42bb0097176e0139ba4ad051b> Who could have imagined that someone would report another bug in beast right before rc2 is built? Shocker...
On Mon, Apr 8, 2019 at 6:20 PM Vinnie Falco via Boost-users <boost-users@lists.boost.org> wrote:
On Sun, Apr 7, 2019 at 9:47 PM Marshall Clow via Boost-users <boost-users@lists.boost.org> wrote:
How are the test bots looking?
Truth be told, they are looking worse for wear and could probably use a vacation to recharge, or perhaps some medical leave.
In the meanwhile, you won't believe this - it is actually a rather funny story. Or short story rather, so....
...it turns out, a user reported another eensy weensy tiny little buggy, this annoying duplicate function template definition problem that happens with friend function templates the fix for which is here:
<https://github.com/vinniefalco/beast/commit/1de60a046292dcd42bb0097176e0139ba4ad051b>
Who could have imagined that someone would report another bug in beast right before rc2 is built? Shocker...
It's why it's called "candidate", no? If there is no opportunity to correct the issue, then it's not much of a candidate.
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users
participants (2)
-
Heriberto Delgado -
Ion Gaztañaga -
Marshall Clow -
Mateusz Loskot -
Michael Powell -
Rainer Deyke -
Tom Kent -
Vinnie Falco