On Sun, Sep 4, 2016 at 11:47 AM, Rene Rivera
On Sat, Sep 3, 2016 at 3:11 PM, Tom Kent
wrote: On Wed, Aug 31, 2016 at 11:01 AM, Rene Rivera
wrote: The first beta packages for 1.62.0 beta 1 are now available:
https://sourceforge.net/projects/boost/files/boost/1.61.0.beta.1/
The SHA256 checksums are as follows:
f7cc83e6a3b03cd7aa8822992aa3e36422cc2214644d69277ef55a4db51f44bd boost_1_62_0_b1.7z 4057993811e40b1fd4719675e44c2550b6c2379546192da2299c17fec9a3dddf boost_1_62_0_b1.tar.bz2 fb0c10b625c5ec47cc837b54740540e400c59571b2eabf427c00f32bffc6ca70 boost_1_62_0_b1.tar.gz b38ef21c43c5ff814a2144bc23871c134164e7f51c71672d0f49a44636fb50b5 boost_1_62_0_b1.zip
As always, the release managers would appreciate it if you download the archive of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
Thanks!
-- The release managers
There were numerous build errors on windows for all versions of visual studio.
They seem to all be around the fiber library, for example:
compile-c-c++ bin.v2\libs\fiber\build\msvc-8.0\release\address-model-64\link-static\threading-multi\algo\algorithm.obj algorithm.cpp .\boost/fiber/algo/algorithm.hpp(10) : fatal error C1083: Cannot open include file: 'chrono': No such file or directory
call "C:\Users\tomkent\AppData\Local\Temp\b2_msvc_8.0_vcvarsall_amd64.cmd" >nul cl /Zm800 -nologo @"bin.v2\libs\fiber\build\msvc-8.0\release\address-model-64\link-static\threading-multi\algo\algorithm.obj.rsp"
The full build logs can be found here: https://gist.github.com/teeks99/339f2768d09449c30e9cd9a20f749100
toolset arch compile Link Execute msvc-8.0 32 ERROR X X msvc-8.0 64 ERROR X X msvc-9.0 32 ERROR X X msvc-9.0 64 ERROR X X msvc-10.0 32 ERROR X X msvc-10.0 64 ERROR X X msvc-11.0 32 ERROR X X msvc-11.0 64 ERROR X X msvc-12.0 32 ERROR X X msvc-12.0 64 ERROR X X msvc-14.0 32 ERROR X X msvc-14.0 64 ERROR 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.
Is it possible to produce binary downloads even with the above errors? Or should we be thinking of creating a beta2 release?
Yes, the binaries did build, with the exception of fiber (I belive that was the only failing library), so if we want to exclude fiber from the beta, then we don't need a beta2. It might be better to do a beta 2 that includes fiber support on windows though. Tom