[release] Boost 1.68.0 Release Candidate 1
The release candidates for the 1.68.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.68.0/source/> The SHA256 checksums are as follows: 59804d8fad02cf3b09485f3dbc0f9097c05fc1e0123f0c133b35a6c6f601109a boost_1_68_0_rc1.7z 7f6130bc3cf65f56a618888ce9d5ea704fa10b462be126ad053e80e553d6d8b7 boost_1_68_0_rc1.tar.bz2 da3411ea45622579d419bfda66f45cd0f8c32a181d84adfa936f5688388995cf boost_1_68_0_rc1.tar.gz 3b1db0b67079266c40b98329d85916e910bbadfc3db3e860c049056788d4d5cd boost_1_68_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 web site will be updated today as well.
On Thu, Aug 2, 2018 at 9:40 AM, Marshall Clow <mclow.lists@gmail.com> wrote:
The release candidates for the 1.68.0 release are now available at:
<https://dl.bintray.com/boostorg/release/1.68.0/source/>
The SHA256 checksums are as follows:
59804d8fad02cf3b09485f3dbc0f9097c05fc1e0123f0c133b35a6c6f601109a boost_1_68_0_rc1.7z 7f6130bc3cf65f56a618888ce9d5ea704fa10b462be126ad053e80e553d6d8b7 boost_1_68_0_rc1.tar.bz2 da3411ea45622579d419bfda66f45cd0f8c32a181d84adfa936f5688388995cf boost_1_68_0_rc1.tar.gz 3b1db0b67079266c40b98329d85916e910bbadfc3db3e860c049056788d4d5cd boost_1_68_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 have successfully built with apple clang 8.0 on Mac OS X 10.11 using -std=c++03/11/14/1z I have successfully built with apple clang 9.1 on Mac OS X 10.13 using -std=c++03/11/14/17/2a -- Marshall
On Thu, Aug 2, 2018 at 11:40 AM, Marshall Clow via Boost < boost@lists.boost.org> wrote:
The release candidates for the 1.68.0 release are now available at:
<https://dl.bintray.com/boostorg/release/1.68.0/source/>
The SHA256 checksums are as follows:
59804d8fad02cf3b09485f3dbc0f9097c05fc1e0123f0c133b35a6c6f601109a boost_1_68_0_rc1.7z 7f6130bc3cf65f56a618888ce9d5ea704fa10b462be126ad053e80e553d6d8b7 boost_1_68_0_rc1.tar.bz2 da3411ea45622579d419bfda66f45cd0f8c32a181d84adfa936f5688388995cf boost_1_68_0_rc1.tar.gz 3b1db0b67079266c40b98329d85916e910bbadfc3db3e860c049056788d4d5cd boost_1_68_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 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
[Tom Kent]
Windows/Visual Studio builds look good. msvc-14.1 32 X X X msvc-14.1 64 X X X
Thanks! Please note that VS 2017 15.8's production release will be available very soon, and it supports feature-test macros which may affect Boost.Config; I am not sure if your 14.1 testing was performed with 15.7 or 15.8 Preview, but I thought I'd mention it. STL
[Tom Kent]
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.
Does this also cover the use of the /std:c++17 option ? Or is this only with the default /std:c++14 setting ? John. Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.
On Fri, Aug 3, 2018 at 9:58 AM, Tytgat, John via Boost < boost@lists.boost.org> wrote:
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
[Tom Kent] 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.
Does this also cover the use of the /std:c++17 option ? Or is this only with the default /std:c++14 setting ?
The windows builds (that the above reference) only use the default toolset options/flags, so c++14. Tom
On 5 August 2018 at 15:28, Tom Kent via Boost <boost@lists.boost.org> wrote:
The windows builds (that the above reference) only use the default toolset options/flags, so c++14.
I know it's the default, but that's not best effort (depending a bit on the VC version 15.?.?) and not helping ms (and therefor the user) to move forward. degski -- *"If something cannot go on forever, it will stop" - Herbert Stein*
The release candidates for the 1.68.0 release are now available
I successfully built 1.68.0 RC1 on x86_64 linux with g++ 8.2.0 and clang 5.0.2 in release and debug mode. However note that - boost::log does not build with -DBOOST_ASIO_NO_DEPRECATED because it still uses the old ASIO API (for example io_service instead of io_context). I have submitted an issue: https://github.com/boostorg/log/issues/59 Thanks for this new release, F
participants (6)
-
degski -
Frédéric -
Marshall Clow -
Stephan T. Lavavej -
Tom Kent -
Tytgat, John