[1.56.0] Release candidates available
Release candidate files for 1.65.0 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. The files (and associated md5s) are: MD5 (boost_1_56_0_rc1.7z) = 0ac22b92b24209286d48e4c41925cd9f MD5 (boost_1_56_0_rc1.tar.bz2) = 5b5bfa99244b1ac5737323decceb19c2 MD5 (boost_1_56_0_rc1.tar.gz) = 2047cdd4e09cda34e7f10fec0f821175 MD5 (boost_1_56_0_rc1.zip) = 0c544f6acc85550b15cdc9221f2ac0c9 Thanks! -- The release managers
On Jul 29, 2014, at 10:06 AM, Marshall Clow
Release candidate files for 1.65.0 are available at http://boost.cowic.de/rc/
Ok, ok - fine. 1.56.0
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.
The files (and associated md5s) are: MD5 (boost_1_56_0_rc1.7z) = 0ac22b92b24209286d48e4c41925cd9f MD5 (boost_1_56_0_rc1.tar.bz2) = 5b5bfa99244b1ac5737323decceb19c2 MD5 (boost_1_56_0_rc1.tar.gz) = 2047cdd4e09cda34e7f10fec0f821175 MD5 (boost_1_56_0_rc1.zip) = 0c544f6acc85550b15cdc9221f2ac0c9
I have successfully built using gcc 4.9.0 and clang 3.4 on Mac OS X 9.4. — Marshall
On Jul 29, 2014, at 11:40 AM, Marshall Clow
On Jul 29, 2014, at 10:06 AM, Marshall Clow
wrote: Release candidate files for 1.65.0 are available at http://boost.cowic.de/rc/
Ok, ok - fine. 1.56.0
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.
The files (and associated md5s) are: MD5 (boost_1_56_0_rc1.7z) = 0ac22b92b24209286d48e4c41925cd9f MD5 (boost_1_56_0_rc1.tar.bz2) = 5b5bfa99244b1ac5737323decceb19c2 MD5 (boost_1_56_0_rc1.tar.gz) = 2047cdd4e09cda34e7f10fec0f821175 MD5 (boost_1_56_0_rc1.zip) = 0c544f6acc85550b15cdc9221f2ac0c9
I have successfully built using gcc 4.9.0 and clang 3.4 on Mac OS X 9.4.
Also successfully built with clang in C++11 mode and tip-of-tree clang in c++14 mode. — Marshall
I have successfully built using gcc 4.9.0 and clang 3.4 on Mac OS X 9.4. Also successfully built with clang in C++11 mode and tip-of-tree clang in c++14 mode. Also successfully built with MinGW-W64 32 and 64-bit posix_threading, based on the GCC-4.9.1.
http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Wi... http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Wi... -- Regards, niXman ___________________________________________________ Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows: http://sourceforge.net/projects/mingw-w64/ ___________________________________________________ Another online IDE: http://liveworkspace.org/
On 07/29/2014 08:40 PM, Marshall Clow wrote:
On Jul 29, 2014, at 10:06 AM, Marshall Clow
wrote: Release candidate files for 1.65.0 are available at http://boost.cowic.de/rc/ Ok, ok - fine. 1.56.0
The following doesn't compile with gcc 4.3.2 on Linux x86:
#include <iostream>
#include
On 07/29/2014 08:40 PM, Marshall Clow wrote:
On Jul 29, 2014, at 10:06 AM, Marshall Clow
wrote: Release candidate files for 1.65.0 are available at http://boost.cowic.de/rc/ Ok, ok - fine. 1.56.0
In my previous post I tested against Beta-1 and not RC1. I tested RC1 and the problem persists. See my previous post for details: http://lists.boost.org/boost-users/2014/07/82589.php
On Tue, 29 Jul 2014 19:06:43 +0200, Marshall Clow
Release candidate files for 1.56.0 are available at http://boost.cowic.de/rc/
Successfully built with Clang 3.3 on Ubuntu 12.04 (32-bit) - although tons of warnings as reported by others. Boris
[...]
On Tue, 29 Jul 2014 19:06:43 +0200, Marshall Clow
Release candidate files for 1.56.0 are available at http://boost.cowic.de/rc/
I get a compiler error with g++ 4.8.3 on Cygwin (64-bit): In file included from libs\system\src\error_code.cpp:19:0: ./boost/system/detail/error_code.ipp: In member function ‘virtual std::string boost::system::{anonymous}::system_error_category::message(int) const’: ./boost/system/detail/error_code.ipp:413:5: error: ‘local_free_on_destruction’ is not a member of ‘boost::detail’ detail::local_free_on_destruction lfod(lpMsgBuf); ^ This looks like the bug Eric had reported at https://svn.boost.org/trac/boost/ticket/10137. Boris
[...]
Boris Schäling
On Tue, 29 Jul 2014 19:06:43 +0200, Marshall Clow
gmail.com>
wrote:
Release candidate files for 1.56.0 are available at http://boost.cowic.de/rc/
I get a compiler error with g++ 4.8.3 on Cygwin (64-bit):
In file included from libs\system\src\error_code.cpp:19:0: ./boost/system/detail/error_code.ipp: In member function ‘virtual std::string boost::system::{anonymous}::system_error_category::message(int) const’: ./boost/system/detail/error_code.ipp:413:5: error: ‘local_free_on_destruction’ is not a member of ‘boost::detail’ detail::local_free_on_destruction lfod(lpMsgBuf);
Hi Boris, I'd like to expand my local testing to g++ 4.8.3 on Cygwin (64-bit) to catch errors like the above much earlier. Thus I'd like to know what your setup looks like. * Do you test from the Windows command prompt or with bash? * What does the b2 command you use look like? * What does your user-config.jam file specify for the cygwin tests? * Anything else you can think of to help me duplicate you cygwin test environment. Thanks, --Beman
On Thu, 31 Jul 2014 17:24:45 +0200, Beman Dawes
[...]I'd like to expand my local testing to g++ 4.8.3 on Cygwin (64-bit) to catch errors like the above much earlier. Thus I'd like to know what your setup looks like.
* Do you test from the Windows command prompt or with bash?
I use bash.
* What does the b2 command you use look like?
For this test I just entered "./bjam".
* What does your user-config.jam file specify for the cygwin tests?
I have no user-config.jam on Cygwin.
* Anything else you can think of to help me duplicate you cygwin test environment.
I did a very simple test as I just downloaded the release candidate, unpacked it, built bjam and then the libraries. :) Boris
Marshall Clow
Release candidate files for 1.65.0 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 tested about a dozen projects with MSVC 12 Update 3 RC and they all compile fine now, except for the compiler crashes because of the Boost.Range free-standing operators. Compiling Boost with MSVC 14 works too (in MSVC 12 mode - there is a compile error in Boost.TypeTraits with noexcept enabled).
On Tue, Jul 29, 2014 at 5:06 PM, Marshall Clow
Release candidate files for 1.65.0 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.
The files (and associated md5s) are: MD5 (boost_1_56_0_rc1.7z) = 0ac22b92b24209286d48e4c41925cd9f MD5 (boost_1_56_0_rc1.tar.bz2) = 5b5bfa99244b1ac5737323decceb19c2 MD5 (boost_1_56_0_rc1.tar.gz) = 2047cdd4e09cda34e7f10fec0f821175 MD5 (boost_1_56_0_rc1.zip) = 0c544f6acc85550b15cdc9221f2ac0c9
Thanks!
-- The release managers
Windows builds look good: Tom toolset arch compile install Link Execute msvc-8.0 32 X X X X msvc-8.0 64 X X X X msvc-9.0 32 X X X X msvc-9.0 64 X X X X msvc-10.0 32 X X X X msvc-10.0 64 X X X X msvc-11.0 32 X X X X msvc-11.0 64 X X X X msvc-12.0 32 X X X X msvc-12.0 64 X 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.
participants (7)
-
Andreas Wehrmann
-
Beman Dawes
-
Boris Schäling
-
Marcel Raad
-
Marshall Clow
-
niXman
-
Tom Kent