On Wed, Aug 31, 2016 at 6:44 PM, Tom Kent wrote:

On Wed, Aug 31, 2016 at 12:01 PM, 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

Just to clarify, is the process going forward going to be to not have RCs for betas? How about final releases?

I don't think it makes sense to make RCs for a beta. If there's something wrong we just make another beta. But we'll have them for release since it's not easy to redo those. (Or did I miss the message with the RC?)

Didn't miss it. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

2016-09-03 22:11 GMT+02:00 Tom Kent :

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

algortihm.hpp(10) == #include <chrono> header chrono is part of C++11 and should be found by MSVC maybe a broken MSVC installation? unit-tests succeed on ' teeks99-08l-win2012R2-64on64' (msvc-14) but fail on 'teeks99-09l-win2012R2-64on64' (msvc-14 too)

On Sun, Sep 4, 2016 at 4:22 AM, Ion Gaztañaga wrote:

El 04/09/2016 a las 10:02, Oliver Kowalke escribió:

...

2016-09-03 22:11 GMT+02:00 Tom Kent mailto:lists@teeks99.com>:

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

algortihm.hpp(10) == #include <chrono>

header chrono is part of C++11 and should be found by MSVC maybe a broken MSVC installation?

MSVC-8.0 (Visual 2005) does not support C++11. Header <chrono> is introduced by Visual 2012, aka MSVC-11.0.

At minimum the Fiber build file should avoid building on platforms it doesn't support. It does that for the tests with the following: [ requires cxx11_auto_declarations cxx11_constexpr cxx11_defaulted_functions cxx11_final cxx11_hdr_tuple cxx11_lambdas cxx11_noexcept cxx11_nullptr cxx11_rvalue_references cxx11_template_aliases cxx11_variadic_templates ] But doesn't do the same for the libs/fiber/build/jamfile.v2. Oliver you should add that requires to the "boost_fiber" lib target. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

On 05/09/2016 17:33, Oliver Kowalke wrote:

2016-09-04 17:24 GMT+02:00 Rene Rivera mailto:grafikrobot@gmail.com>:

At minimum the Fiber build file should avoid building on platforms it doesn't support. It does that for the tests with the following:

[ requires cxx11_auto_declarations cxx11_constexpr cxx11_defaulted_functions cxx11_final cxx11_hdr_tuple cxx11_lambdas cxx11_noexcept cxx11_nullptr cxx11_rvalue_references cxx11_template_aliases cxx11_variadic_templates ]

But doesn't do the same for the libs/fiber/build/jamfile.v2. Oliver you should add that requires to the "boost_fiber" lib target.

thx for the hint. I've pushed the commit. without a clean checkout --reconfigure as to be applied to b2 (otherwise cached check results are used)

That stops it from trying to be built with any msvc version prior to 14.0 update 3, which fixes most of the errors users will see. Static library builds with VC14 are OK, but shared library builds fail with: M:\data\boost\boost\boost/fiber/context.hpp(153): error C2492: 'boost::fibers::context::active_': data with thread storage duration may not have dll interface M:\data\boost\boost\boost/fiber/context.hpp(153): error C2492: 'private: static boost::fibers::context * boost::fibers::context::active_': data with thread storage duration may not have dll interface I guess since the std says nothing about shared libraries, you're into implementation defined behaviour here? Do these variables need to be exported from the dll as part of the interface or are they implementation details? Either way a quick fix for this release would be to disable shared lib builds for msvc. HTH, John.

2016-09-05 20:20 GMT+02:00 John Maddock :

Static library builds with VC14 are OK, but shared library builds fail with:

M:\data\boost\boost\boost/fiber/context.hpp(153): error C2492: 'boost::fibers::context::active_': data with thread storage duration may not have dll interface M:\data\boost\boost\boost/fiber/context.hpp(153): error C2492: 'private: static boost::fibers::context * boost::fibers::context::active_': data with thread storage duration may not have dll interface

I guess since the std says nothing about shared libraries, you're into implementation defined behaviour here? Do these variables need to be exported from the dll as part of the interface or are they implementation details?

I've pushed a commit that should solve this issue

On Sun, Sep 4, 2016 at 11:49 AM, Rene Rivera wrote:

On Sun, Sep 4, 2016 at 4:22 AM, Ion Gaztañaga wrote:

...

El 04/09/2016 a las 10:02, Oliver Kowalke escribió:

...

2016-09-03 22:11 GMT+02:00 Tom Kent mailto:lists@teeks99.com>:

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

algortihm.hpp(10) == #include <chrono>

header chrono is part of C++11 and should be found by MSVC maybe a broken MSVC installation?

MSVC-8.0 (Visual 2005) does not support C++11. Header <chrono> is introduced by Visual 2012, aka MSVC-11.0.

Note that the chrono header is not the only error. There are other headers, and even with the chrono header present, there are other errors. I expect Oliver to look at them ASAP and try and address them.

I suggest disabling the Fiber part of the Boost build until it can be resolved one way or another. Of course, that Microsoft updates its compiler(s) with its feature complete forward progress.

-- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

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? -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

On Sun, Sep 4, 2016 at 6:08 PM, Tom Kent wrote:

On Sun, Sep 4, 2016 at 11:47 AM, Rene Rivera wrote:

...

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.

Now that I'm back with a decent connection, I've uploaded the B1 binaries to sourceforge. https://sourceforge.net/projects/boost/files/boost-binaries/1.62.0_b1/ Since the fiber build was a failure, I'm still in favor of a beta 2 build to make sure that gets flushed out before going to RCs. Tom