Boost 1.60.0 beta 1 Release Candidate 4 available for testing
After far too long, release candidate files for 1.60.0 beta 4 are available at http://boost.cowic.de/rc/ 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. This helps ensure the candidates build OK before we push them out to SourceForge. Changes since rc3: * Boost.Test has been updated and now builds on Visual Studio Changes since rc1: * Boost.Sprit has been updated and Boost.Log now builds. * Boost.Math has been updated and now builds. Known issues (which will not be fixed for the beta): * Errors when building Boost.TypeErasure for older versions of Visual Studio. * Boost.Test fails when building on Darwin with gcc 4.9.2 The files (and associated md5s) are: MD5 (boost_1_60_0_b1_rc4.7z) = 63530c9594b24f56e5df79d910c9daeb MD5 (boost_1_60_0_b1_rc4.tar.bz2) = 29af12a1028536219a21517e953df4eb MD5 (boost_1_60_0_b1_rc4.tar.gz) = 74df7f5eb5e32f3a92b6141af3c6f541 MD5 (boost_1_60_0_b1_rc4.zip) = 90c25c34b64eb6cc88845ec5372938d7 Thanks! -- The release managers
On Sun, Dec 6, 2015 at 10:29 PM, Marshall Clow <mclow.lists@gmail.com> wrote:
After far too long, release candidate files for 1.60.0 beta 4 are available at http://boost.cowic.de/rc/
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 the RC4 libraries on Mac OS X with Apple LLVM version 7.0.0 (clang-700.1.76) in both C++03 and C++11 modes. -- Marshall
On 07/12/2015 07:30, Marshall Clow wrote:
On Sun, Dec 6, 2015 at 10:29 PM, Marshall Clow <mclow.lists@gmail.com> wrote:
After far too long, release candidate files for 1.60.0 beta 4 are available at http://boost.cowic.de/rc/
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 the RC4 libraries on Mac OS X with Apple LLVM version 7.0.0 (clang-700.1.76) in both C++03 and C++11 modes.
It build on CentOS 6.5 wth Intel 15. Still trying to remember the name of the global test target (the thing still requires bjam, which does not provide the list on available targets).
-- Marshall
___________________________
-- --- Alain
On Mon, Dec 7, 2015 at 6:29 AM, Marshall Clow <mclow.lists@gmail.com> wrote:
After far too long, release candidate files for 1.60.0 beta 4 are available at http://boost.cowic.de/rc/
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.
This helps ensure the candidates build OK before we push them out to SourceForge.
Changes since rc3: * Boost.Test has been updated and now builds on Visual Studio
Changes since rc1: * Boost.Sprit has been updated and Boost.Log now builds. * Boost.Math has been updated and now builds.
Known issues (which will not be fixed for the beta): * Errors when building Boost.TypeErasure for older versions of Visual Studio. * Boost.Test fails when building on Darwin with gcc 4.9.2
The files (and associated md5s) are: MD5 (boost_1_60_0_b1_rc4.7z) = 63530c9594b24f56e5df79d910c9daeb MD5 (boost_1_60_0_b1_rc4.tar.bz2) = 29af12a1028536219a21517e953df4eb MD5 (boost_1_60_0_b1_rc4.tar.gz) = 74df7f5eb5e32f3a92b6141af3c6f541 MD5 (boost_1_60_0_b1_rc4.zip) = 90c25c34b64eb6cc88845ec5372938d7
As expected, the Visual Studio builds have failures with msvc-8.0, 9.0, and 10.0 in type_erasure: compile-c-c++ bin.v2\libs\type_erasure\build\msvc-8.0\debug\link-static\runtime-link-static\threading-multi\dynamic_binding.obj dynamic_binding.cpp C:\Program Files (x86)\Microsoft Visual Studio 8\VC\INCLUDE\utility(32) : error C2248: 'boost::shared_mutex::shared_mutex' : cannot access private member declared in class 'boost::shared_mutex' .\boost/thread/win32/shared_mutex.hpp(87) : see declaration of 'boost::shared_mutex::shared_mutex' .\boost/thread/win32/shared_mutex.hpp(28) : see declaration of 'boost::shared_mutex' C:\Program Files (x86)\Microsoft Visual Studio 8\VC\INCLUDE\utility(30) : while compiling class template member function 'std::pair<_Ty1,_Ty2>::pair(void)' with [ _Ty1=`anonymous-namespace'::map_type, _Ty2=`anonymous-namespace'::mutex_type ] libs\type_erasure\src\dynamic_binding.cpp(30) : see reference to class template instantiation 'std::pair<_Ty1,_Ty2>' being compiled with [ _Ty1=`anonymous-namespace'::map_type, _Ty2=`anonymous-namespace'::mutex_type ] call "C:\Users\tomkent\AppData\Local\Temp\2\b2_msvc_8.0_vcvarsall_x86.cmd" >nul cl /Zm800 -nologo @"bin.v2\libs\type_erasure\build\msvc-8.0\debug\link-static\runtime-link-static\threading-multi\dynamic_binding.obj.rsp" ...failed compile-c-c++ bin.v2\libs\type_erasure\build\msvc-8.0\debug\link-static\runtime-link-static\threading-multi\dynamic_binding.obj... Everything else looks good. Here's the full logs. 32-bit: https://gist.github.com/teeks99/6247c2e4ade8966e47bb 64-bit: https://gist.github.com/teeks99/35db7c88053624f1b277 toolset arch compile Link Execute msvc-8.0 32 FAIL X X msvc-8.0 64 FAIL X X msvc-9.0 32 FAIL X X msvc-9.0 64 FAIL X X msvc-10.0 32 FAIL X X msvc-10.0 64 FAIL 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 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
Hi,
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 library built all right (VC++2013), but there was a bunch of warnings when compiling Boost.Spirit (roughly 3000 lines in the log) and Boost.Python (roughly 200 lines); see below. I didn't run the Tests. Question here: Is there an automated way of running the tests with the RC-version, best resulting in a file that can be uploaded manually (I'm behind a Firewall)? If so, what are the requirements and how do you use that tool? (Sorry for the question; I didn't find the Docs on the Website very clarifying.) Regards, Alexander Appendix: Here are some specimen of the warnings: * Boost.Python:
import.cpp d:\programme\python 3.2.2 64bit\include\pymath.h(22) : warning C4273: 'round' : inconsistent dll linkage C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\math.h(516) : see previous definition of 'round' C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xtgmath.h(206) : warning C4273: 'round' : inconsistent dll linkage C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\math.h(516) : see previous definition of 'round' compile-c-c++ bin.v2\libs\python\build\msvc-12.0\release\link-static\threading-multi\exec.obj (The others were of similar kind.)
* Boost.Spirit:
named_scope_format_parser.cpp .\boost/spirit/home/support/terminal.hpp(264) : warning C4348: 'boost::spirit::terminal<boost::spirit::tag::lit>::result_helper' : redefinition of default parameter : parameter 3 .\boost/spirit/home/support/terminal.hpp(270) : see declaration of 'boost::spirit::terminal<boost::spirit::tag::lit>::result_helper' .\boost/spirit/home/support/common_terminals.hpp(142) : see reference to class template instantiation 'boost::spirit::terminal<boost::spirit::tag::lit>' being compiled (The others were of similar kind.)
* Here's the configuration prefix of the log:
Performing configuration checks
- 32-bit : yes - arm : no - mips1 : no - power : no - sparc : no - x86 : yes
Building the Boost C++ Libraries.
- symlinks supported : no - junctions supported : yes - hardlinks supported : yes - has_icu builds : no warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - zlib : no - iconv (libc) : no - iconv (separate) : no - icu : no - icu (lib64) : no - compiler-supports-visibility : no - message-compiler : yes - compiler-supports-ssse3 : yes - compiler-supports-avx2 : yes - gcc visibility : no - long double support : yes warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. - zlib : no (cached)
Component configuration:
- atomic : building - chrono : building - container : building - context : building - coroutine : building - coroutine2 : building - date_time : building - exception : building - filesystem : building - graph : building - graph_parallel : building - iostreams : building - locale : building - log : building - math : building - mpi : building - program_options : building - python : building - random : building - regex : building - serialization : building - signals : building - system : building - test : building - thread : building - timer : building - type_erasure : building - wave : building
participants (2)
-
Alain Miniussi -
Alexander Lauser -
Marshall Clow -
Tom Kent