[release] Boost 1.64.0 Release Candidate 1
The release candidates for the 1.64.0 release are now available at: <https://dl.bintray.com/boostorg/beta/1.64.0.rc.1/> The SHA256 checksums are as follows: 49c6abfeb5b480f6a86119c0d57235966b4690ee6ff9e6401ee868244808d155 boost_1_64_0_rc1.7z 7bcc5caace97baa948931d712ea5f37038dbb1c5d89b43ad4def4ed7cb683332 boost_1_64_0_rc1.tar.bz2 0445c22a5ef3bd69f5dfb48354978421a85ab395254a26b1ffb0aa1bfd63a108 boost_1_64_0_rc1.tar.gz b99973c805f38b549dbeaf88701c0abeff8b0e8eaa4066df47cac10a32097523 boost_1_64_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 Team -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
On Mon, Apr 17, 2017 at 5:47 AM, Rene Rivera via Boost <boost@lists.boost.org> 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.
VS2017 / W7: ...updated 1122 targets... The Boost C++ Libraries were successfully built! Thanks! -- Olaf
On Sun, Apr 16, 2017 at 8:47 PM, Rene Rivera via Boost < boost@lists.boost.org> wrote:
The release candidates for the 1.64.0 release are now available at:
<https://dl.bintray.com/boostorg/beta/1.64.0.rc.1/>
The SHA256 checksums are as follows:
49c6abfeb5b480f6a86119c0d57235966b4690ee6ff9e6401ee868244808d155 boost_1_64_0_rc1.7z 7bcc5caace97baa948931d712ea5f37038dbb1c5d89b43ad4def4ed7cb683332 boost_1_64_0_rc1.tar.bz2 0445c22a5ef3bd69f5dfb48354978421a85ab395254a26b1ffb0aa1bfd63a108 boost_1_64_0_rc1.tar.gz b99973c805f38b549dbeaf88701c0abeff8b0e8eaa4066df47cac10a32097523 boost_1_64_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.
Successfully built from the .gz using * Apple LLVM version 8.0.0 (clang-800.0.42.1) * clang version 5.0.0 (trunk 300448) in C++03/11/14/1z modes. So: 8 successful builds, no failures. -- Marshall
On 17 April 2017 at 04:47, Rene Rivera via Boost <boost@lists.boost.org> wrote:
The release candidates for the 1.64.0 release are now available at:
I've put it on the website. Documentation: http://www.boost.org/doc/libs/1_64_0/ Release notes: http://www.boost.org/users/history/in_progress.html
On 17 Apr 2017, at 17:33, Daniel James via Boost <boost@lists.boost.org> wrote:
On 17 April 2017 at 04:47, Rene Rivera via Boost <boost@lists.boost.org> wrote: The release candidates for the 1.64.0 release are now available at:
I've put it on the website.
Documentation: http://www.boost.org/doc/libs/1_64_0/ Release notes: http://www.boost.org/users/history/in_progress.html
Looks set to be another extremely useful release. Thanks to all. I checked out the list of tested compilers (slightly morbid curiosity about how VC14.1 had ended up!). The list of "additional" tested compilers is quite close to being a duplicate of the "primary" compilers and so the whole section is not that easy to read. Would it be a better layout to just list the compilers /once/ with the primary ones shown in bold? (Clearly not a stopper for 1.64, just a thought for a future release)
On Sun, Apr 16, 2017 at 10:47 PM, Rene Rivera via Boost < boost@lists.boost.org> wrote:
The release candidates for the 1.64.0 release are now available at:
<https://dl.bintray.com/boostorg/beta/1.64.0.rc.1/>
The SHA256 checksums are as follows:
49c6abfeb5b480f6a86119c0d57235966b4690ee6ff9e6401ee868244808d155 boost_1_64_0_rc1.7z 7bcc5caace97baa948931d712ea5f37038dbb1c5d89b43ad4def4ed7cb683332 boost_1_64_0_rc1.tar.bz2 0445c22a5ef3bd69f5dfb48354978421a85ab395254a26b1ffb0aa1bfd63a108 boost_1_64_0_rc1.tar.gz b99973c805f38b549dbeaf88701c0abeff8b0e8eaa4066df47cac10a32097523 boost_1_64_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 Builds look good. toolset arch compile Link Execute msvc-8.0 32 X X X msvc-8.0 64 X X X msvc-9.0 32 X X X msvc-9.0 64 X X X 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 Install means that the installers for the respective version were generated 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. Tom
"Rene Rivera 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 cross-compiles for QNX 6.6.0 from a Linux host with this command line: ./b2 toolset=qcc target-os=qnxnto --without-python cxxflags="-DBOOST_NO_CXX11_NUMERIC_LIMITS" Without -DBOOST_NO_CXX11_NUMERIC_LIMITS, I get: ...failed updating 41 targets... This is a long-standing problem. Boost.Config needs to learn the difference between Dinkumware for QNX 6.6.0 and Dinkumware for Visual C++. Regards, Niklas Angare
Boost - Dev mailing list 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.
Works fine for me with MSVC 12, 14, and 14.1. But having to delete the b2_msvc_*.cmd files in the Temp directory after every Visual Studio or Windows SDK update is pretty annoying. Marcel -- View this message in context: http://boost.2283326.n4.nabble.com/release-Boost-1-64-0-Release-Candidate-1-... Sent from the Boost - Dev mailing list archive at Nabble.com.
-----Original Message----- From: Boost [mailto:boost-bounces@wowbagger.crest.iu.edu] On Behalf Of Marcel Raad via Boost Sent: 19 April 2017 08:30 To: boost@lists.boost.org Cc: Marcel Raad Subject: Re: [boost] [release] Boost 1.64.0 Release Candidate 1
Boost - Dev mailing list 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.
Works fine for me with MSVC 12, 14, and 14.1.
But having to delete the b2_msvc_*.cmd files in the Temp directory after every Visual Studio or Windows SDK update is pretty annoying.
+1 What can I do to help get this unwanted featurette fixed? Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830
participants (9)
-
Daniel James -
Marcel Raad -
Marshall Clow -
Niklas Angare -
Olaf van der Spek -
Paul A. Bristow -
Pete Bartlett -
Rene Rivera -
Tom Kent