[boost] [1.56.0] Release candidates available
Marshall Clow
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
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Marshall Clow
On Jul 29, 2014, at 10:06 AM, Marshall Clow <mclow...@gmail.com> wrote:
> 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
— Marshall
Menelaos Karavelas
On 29/07/2014 09:40 μμ, Marshall Clow wrote:
> On Jul 29, 2014, at 10:06 AM, Marshall Clow <mclow...@gmail.com> 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.
Same here on ubuntu 13.10 with gcc 4.8 and clang 3.2.
A lot of unused local typedef warnings on gcc 4.8 and A LOT of warnings
with clang (almost 46 MB build log file).
- m.
Marshall Clow
On Jul 29, 2014, at 11:40 AM, Marshall Clow <mclow...@gmail.com> wrote:
>
> On Jul 29, 2014, at 10:06 AM, Marshall Clow <mclow...@gmail.com> 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.
Agustín K-ballo Bergé
> 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.
snippet results in an ICE:
#include <boost/range/iterator_range_core.hpp>
#include <boost/lambda/lambda.hpp>
int main()
{
using boost::lambda::_1;
_1 == 42;
}
This is caused by the `operator==` defined by Range.
Regards,
--
Agustín K-ballo Bergé.-
http://talesofcpp.fusionfenix.com
Stephan T. Lavavej
> snippet results in an ICE:
Thanks,
STL
Marcel Raad
>
> [Agustín K-ballo Bergé]
> > Builds successfully with msvc-12.0. However, the following trivial
> > snippet results in an ICE:
>
> Repros with both VC12 and VC14. Filed as DevDiv#996370 "ICE with Boost
> 1.56.0 RC1 - Assertion failed:
> is<T>(), trees.h 626".
Could that be the same bug as
https://connect.microsoft.com/VisualStudio/feedback/details/915061/vc12-
update-3-rc-boost-1-56-compiler-crash?
That ICE is also caused by the Boost.Range free-standing operators.
The mentioned workaround also applies to Boost.Lambda: replacing the
anonymous enum in lambda/detail/operator_return_type_traits.hpp with static
const ints makes the ICE go away.
Stephan T. Lavavej
> https://connect.microsoft.com/VisualStudio/feedback/details/915061/vc12-
> update-3-rc-boost-1-56-compiler-crash?
> That ICE is also caused by the Boost.Range free-standing operators.
STL
Eric Niebler
> On Tue, 29 Jul 2014 19:06:43 +0200, Marshall Clow
> <mclow...@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);
> ^
>
> This looks like the bug Eric had reported at
> <https://svn.boost.org/trac/boost/ticket/10137>.
Crud. Beman, did a merge get missed?
Eric
Andrey Semashev
> 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
I'm seeing compilation failures with gcc 4.4.7 in C++11 mode:
In file included from ./boost/graph/adjacency_list.hpp:246,
from ./boost/graph/graphviz.hpp:24,
from ./boost/graph/graphml.hpp:20,
from libs/graph/src/graphml.cpp:17:
./boost/graph/detail/adjacency_list.hpp:304: error:
‘boost::detail::stored_edge_property<Vertex,
Property>::stored_edge_property(boost::detail::stored_edge_property<Vertex,
Property>&&)’ cannot be defaulted
./boost/graph/detail/adjacency_list.hpp:305: error:
‘boost::detail::stored_edge_property<Vertex, Property>&
boost::detail::stored_edge_property<Vertex,
Property>::operator=(boost::detail::stored_edge_property<Vertex,
Property>&&)’ cannot be defaulted
"g++-4.4" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline
-Wall -pthread -fPIC -std=c++0x -DBOOST_ALL_NO_LIB=1
-DBOOST_GRAPH_DYN_LINK=1 -DBOOST_HAS_ICU=1 -DNDEBUG -I"."
-I"libs/graph/src" -c -o
"bin.v2/libs/graph/build/gcc-4.4/release/threading-multi/graphml.o"
"libs/graph/src/graphml.cpp"
...failed gcc.compile.c++
bin.v2/libs/graph/build/gcc-4.4/release/threading-multi/graphml.o...
I'll see if I can come up with a patch.
Andrey Semashev
> 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
I also see compilation failures with gcc 4.6 in C++11 mode:
In file included from ./boost/thread/once.hpp:20:0,
from ./boost/thread.hpp:17,
from libs/coroutine/src/posix/stack_traits.cpp:22:
./boost/thread/pthread/once_atomic.hpp: In function ‘void
boost::call_once(boost::once_flag&, Function&&, ArgTypes&& ...) [with
Function = void (&)(long unsigned int*), ArgTypes = {long unsigned
int*}]’:
libs/coroutine/src/posix/stack_traits.cpp:57:46: instantiated from here
./boost/thread/pthread/once_atomic.hpp:127:9: error: call of
overloaded ‘invoke(boost::decay<void (&)(long unsigned int*)>::type,
boost::decay<long unsigned int*>::type)’ is ambiguous
./boost/thread/pthread/once_atomic.hpp:127:9: note: candidates are:
./boost/thread/detail/invoke.hpp:538:5: note: typename
boost::enable_if_c<(! boost::is_member_function_pointer<Fp>::value),
Ret>::type boost::detail::invoke(Fp&&, Args&& ...) [with Ret = void,
Fp = void (*)(long unsigned int*), Args = {long unsigned int*},
typename boost::enable_if_c<(!
boost::is_member_function_pointer<Fp>::value), Ret>::type = void]
./boost/thread/detail/invoke.hpp:544:5: note: Ret
boost::detail::invoke(Ret (*)(Args ...), Args&& ...) [with Ret = void,
Args = {long unsigned int*}]
./boost/thread/pthread/once_atomic.hpp: In function ‘void
boost::call_once(boost::once_flag&, Function&&, ArgTypes&& ...) [with
Function = void (&)(rlimit*), ArgTypes = {rlimit*}]’:
libs/coroutine/src/posix/stack_traits.cpp:65:54: instantiated from here
./boost/thread/pthread/once_atomic.hpp:127:9: error: call of
overloaded ‘invoke(boost::decay<void (&)(rlimit*)>::type,
boost::decay<rlimit*>::type)’ is ambiguous
./boost/thread/pthread/once_atomic.hpp:127:9: note: candidates are:
./boost/thread/detail/invoke.hpp:538:5: note: typename
boost::enable_if_c<(! boost::is_member_function_pointer<Fp>::value),
Ret>::type boost::detail::invoke(Fp&&, Args&& ...) [with Ret = void,
Fp = void (*)(rlimit*), Args = {rlimit*}, typename
boost::enable_if_c<(! boost::is_member_function_pointer<Fp>::value),
Ret>::type = void]
./boost/thread/detail/invoke.hpp:544:5: note: Ret
boost::detail::invoke(Ret (*)(Args ...), Args&& ...) [with Ret = void,
Args = {rlimit*}]
"g++-4.6" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline
-Wall -pthread -fPIC -std=c++0x -DBOOST_ALL_NO_LIB=1
-DBOOST_CHRONO_DYN_LINK=1 -DBOOST_CONTEXT_DYN_LINK=1
-DBOOST_COROUTINES_DYN_LINK=1 -DBOOST_COROUTINES_SOURCE
-DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_SYSTEM_NO_DEPRECATED
-DBOOST_THREAD_BUILD_DLL=1 -DBOOST_THREAD_POSIX
-DBOOST_THREAD_USE_DLL=1 -DNDEBUG -I"." -c -o
"bin.v2/libs/coroutine/build/gcc-4.6/release/threading-multi/posix/stack_traits.o"
"libs/coroutine/src/posix/stack_traits.cpp"
...failed gcc.compile.c++
bin.v2/libs/coroutine/build/gcc-4.6/release/threading-multi/posix/stack_traits.o...
Andrey Semashev
<andrey....@gmail.com> wrote:
> On Tue, Jul 29, 2014 at 9:06 PM, Marshall Clow <mclow...@gmail.com> wrote:
>> Release candidate files for 1.65.0 are available at
>> http://boost.cowic.de/rc/
>
>
> In file included from ./boost/graph/adjacency_list.hpp:246,
> from ./boost/graph/graphviz.hpp:24,
> from ./boost/graph/graphml.hpp:20,
> from libs/graph/src/graphml.cpp:17:
> ./boost/graph/detail/adjacency_list.hpp:304: error:
> ‘boost::detail::stored_edge_property<Vertex,
> Property>::stored_edge_property(boost::detail::stored_edge_property<Vertex,
> Property>&&)’ cannot be defaulted
> ./boost/graph/detail/adjacency_list.hpp:305: error:
> ‘boost::detail::stored_edge_property<Vertex, Property>&
> boost::detail::stored_edge_property<Vertex,
> Property>::operator=(boost::detail::stored_edge_property<Vertex,
> Property>&&)’ cannot be defaulted
>
> "g++-4.4" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline
> -Wall -pthread -fPIC -std=c++0x -DBOOST_ALL_NO_LIB=1
> -DBOOST_GRAPH_DYN_LINK=1 -DBOOST_HAS_ICU=1 -DNDEBUG -I"."
> -I"libs/graph/src" -c -o
> "bin.v2/libs/graph/build/gcc-4.4/release/threading-multi/graphml.o"
> "libs/graph/src/graphml.cpp"
>
> ...failed gcc.compile.c++
> bin.v2/libs/graph/build/gcc-4.4/release/threading-multi/graphml.o...
>
> I'll see if I can come up with a patch.
https://github.com/boostorg/graph/pull/14
Alexander Lauser
gcc.compile.c++ bin.v2/libs/python/build/gcc-4.7/release/link-static/threading-multi/object/enum.o
libs/python/src/object/enum.cpp: In function ‘boost::python::api::object boost::python::objects::{anonymous}::new_enum_type(const char*, const char*)’:
libs/python/src/object/enum.cpp:150:11: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
gcc.compile.c++ bin.v2/libs/python/build/gcc-4.7/release/link-static/threading-multi/object/class.o
libs/python/src/object/class.cpp: In function ‘PyObject* boost::python::objects::static_data()’:
libs/python/src/object/class.cpp:211:11: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
libs/python/src/object/class.cpp: In function ‘boost::python::type_handle boost::python::objects::class_metatype()’:
libs/python/src/object/class.cpp:319:11: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
libs/python/src/object/class.cpp: In function ‘boost::python::type_handle boost::python::objects::class_type()’:
libs/python/src/object/class.cpp:473:11: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
gcc.compile.c++ bin.v2/libs/python/build/gcc-4.7/release/link-static/threading-multi/object/function.o
libs/python/src/object/function.cpp: In constructor ‘boost::python::objects::function::function(const boost::python::objects::py_function&, const boost::python::detail::keyword*, unsigned int)’:
libs/python/src/object/function.cpp:108:9: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
libs/python/src/object/function.cpp:110:9: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
gcc.compile.c++ bin.v2/libs/python/build/gcc-4.7/release/link-static/threading-multi/object/inheritance.o
gcc.compile.c++ bin.v2/libs/python/build/gcc-4.7/release/link-static/threading-multi/object/life_support.o
libs/python/src/object/life_support.cpp: In function ‘PyObject* boost::python::objects::make_nurse_and_patient(PyObject*, PyObject*)’:
libs/python/src/object/life_support.cpp:94:9: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
libs/python/src/object/life_support.cpp:96:9: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
- Alex
Tom Kent
wrote:
> 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
>
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.
Beman Dawes
> On 07/29/2014 02:44 PM, Boris Schäling wrote:
> > On Tue, 29 Jul 2014 19:06:43 +0200, Marshall Clow
> > <mclow...@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);
> > ^
> >
> > This looks like the bug Eric had reported at
> > <https://svn.boost.org/trac/boost/ticket/10137>.
>
> Crud. Beman, did a merge get missed?
>
I'll look at this in a few hours.
--Beman
Beman Dawes
While we do not want to hold the release to clear warnings, once the
release ships we might want to have a sprint to clear warnings.
Thanks,
--Beman
Eric Niebler
> On Wed, Jul 30, 2014 at 10:49 AM, Andrey Semashev
> <andrey....@gmail.com> wrote:
>> On Tue, Jul 29, 2014 at 9:06 PM, Marshall Clow <mclow...@gmail.com> wrote:
>>> Release candidate files for 1.65.0 are available at
>>> http://boost.cowic.de/rc/
>>
>> I'm seeing compilation failures with gcc 4.4.7 in C++11 mode:
>>
>> "g++-4.4" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline
>> -Wall -pthread -fPIC -std=c++0x -DBOOST_ALL_NO_LIB=1
>> -DBOOST_GRAPH_DYN_LINK=1 -DBOOST_HAS_ICU=1 -DNDEBUG -I"."
>> -I"libs/graph/src" -c -o
>> "bin.v2/libs/graph/build/gcc-4.4/release/threading-multi/graphml.o"
>> "libs/graph/src/graphml.cpp"
>>
>> ...failed gcc.compile.c++
>> bin.v2/libs/graph/build/gcc-4.4/release/threading-multi/graphml.o...
>>
>> I'll see if I can come up with a patch.
>
> https://github.com/boostorg/graph/pull/14
and consider rolling it into a point release shortly after 1.56.0. My
reasoning is that the but doesn't have very broad scope for causing
problems (it only affects GCC 4.4, which is over 4 years old).
\e
Eric Niebler
Ouch. Can anybody else repro this? Oliver, thoughts?
Eric
Jason Roehm
On 07/30/2014 01:12 PM, Eric Niebler wrote:
> Thanks for the patch. My opinion is that we should hold on to this fix
> and consider rolling it into a point release shortly after 1.56.0. My
> reasoning is that the but doesn't have very broad scope for causing
> problems (it only affects GCC 4.4, which is over 4 years old).
mode? Note that gcc 4.4 is the version provided by the RHEL6-based Linux
distributions, which are still in pretty wide use. I doubt that many
users are attempting to use "-std=c++0x" with that old of a compiler though.
Jason
Eric Niebler
>
> On 07/30/2014 01:12 PM, Eric Niebler wrote:
>> Thanks for the patch. My opinion is that we should hold on to this fix
>> and consider rolling it into a point release shortly after 1.56.0. My
>> reasoning is that the but doesn't have very broad scope for causing
>> problems (it only affects GCC 4.4, which is over 4 years old).
>
> Just making sure: is the problem in question only triggered in C++11
> mode? Note that gcc 4.4 is the version provided by the RHEL6-based Linux
> distributions, which are still in pretty wide use. I doubt that many
> users are attempting to use "-std=c++0x" with that old of a compiler
> though.
this only affects people using -std=c++0x.
\e
Thomas Suckow
>
> Just making sure: is the problem in question only triggered in C++11 mode? Note that gcc 4.4 is the version provided by the RHEL6-based Linux distributions, which are still in pretty wide use. I doubt that many users are attempting to use "-std=c++0x" with that old of a compiler though.
>
-Thomas
Andrey Semashev
I think the problem is in Boost.Thread, boost/thread/detail/invoke.hpp. I
emailed Vicente, no response so far.
I'll try to come up with a patch.
Beman Dawes
> On 07/29/2014 02:44 PM, Boris Schäling wrote:
> > On Tue, 29 Jul 2014 19:06:43 +0200, Marshall Clow
> > <mclow...@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);
> > ^
> >
> > This looks like the bug Eric had reported at
> > <https://svn.boost.org/trac/boost/ticket/10137>.
>
> Crud. Beman, did a merge get missed?
>
It was a pull request. I've merged it to develop, although I only tested it
on VC++ and MinGW because I'm having trouble getting Cygwin tests to work
because of some flaw in my test setup. I'll take a break, then look at it
again.
But even if it is working for Cygwin, I'd want to see successful tests on
Linux and OS X at a minimum before merging to master.
--Beman
Andrey Semashev
Belcourt, Kenneth
On Jul 30, 2014, at 2:04 AM, Andrey Semashev <andrey....@gmail.com> wrote:
> On Wed, Jul 30, 2014 at 10:49 AM, Andrey Semashev
> <andrey....@gmail.com> wrote:
>> On Tue, Jul 29, 2014 at 9:06 PM, Marshall Clow <mclow...@gmail.com> wrote:
>>> Release candidate files for 1.65.0 are available at
>>> http://boost.cowic.de/rc/
>>
>> I'm seeing compilation failures with gcc 4.4.7 in C++11 mode:
— Noel
Beman Dawes
I've now tested Boost.System locally:
OS X / gcc
OS X / clang
Ubuntu / gcc
Ubuntu / clang
Win 7 / msvc-10.0
Win 7 / msvc-11.0
Win 7 / msvc-12.0
Win 7 / gcc - cygwin / cygwin installer / from bash (thanks to Eric for
help getting this running)
Win 7 / gcc - cygwin / cygwin installer / from Windows command line
Win 7 / gcc - mingw / mingw installer / from Windows command line
The last two turned up a different configuration issue which has also been
fixed.
I'd like permission to merge system develop to master Sunday morning (after
more regression testers have cycled)>
Tom Kent
> I'd like permission to merge system develop to master Sunday morning (after
> more regression testers have cycled)
>
testers to cycle before pushing another rc?
Tom
Kyle Ketterer
builds) :
b2 toolset=gcc --build-type=complete stage /* address-model=64 */
Kyle Ketterer
> I have successfully compiled this RC on Win76 using Mingw and Mingw64 (win
> builds) :
>
> b2 toolset=gcc --build-type=complete stage /* address-model=64 */
>
Niall Douglas
> I have successfully compiled this RC on Win76 using Mingw and Mingw64 (win
> builds) :
>
> b2 toolset=gcc --build-type=complete stage /* address-model=64 */
mine which entered rc1 broke mingw32.
I pushed a fix today to develop branch. I don't see it as a
showstopper as mingw-w64 still works, and besides ASIO hasn't
compiled with mingw32 without a bit of prodding for over a year and
no one complains, they just follow the stackoverflow guide.
Niall
--
ned Productions Limited Consulting
http://www.nedproductions.biz/
http://ie.linkedin.com/in/nialldouglas/
Kyle Ketterer
> I would be highly surprised if rc1 compiles with mingw32. A fix of
> mine which entered rc1 broke mingw32.
>
> I pushed a fix today to develop branch. I don't see it as a
> showstopper as mingw-w64 still works, and besides ASIO hasn't
> compiled with mingw32 without a bit of prodding for over a year and
> no one complains, they just follow the stackoverflow guide.
>
> Niall
>
>
I apologize for the confusion. The Win-Builds project has a 32 bit and 64
bit tool set. I mistakenly referred to this as THE Mingw. I was able to
compile this RC with the 32 and 64 bit toolset of that distro.
Keep up the excellent work !
Stephan T. Lavavej
> Builds successfully with msvc-12.0. However, the following trivial
> snippet results in an ICE:
> 1.56.0 RC1 - Assertion failed: is<T>(), trees.h 626".
This bug is still active.
STL
Stephan T. Lavavej
> Builds successfully with msvc-12.0. However, the following trivial
> snippet results in an ICE:
[STL]
> Repros with both VC12 and VC14. Filed as DevDiv#996370 "ICE with Boost
> 1.56.0 RC1 - Assertion failed: is<T>(), trees.h 626".
> The compiler team determined that this was a duplicate of
> DevDiv#980577/Connect#915061 "VC12 Update 3 RC: Boost 1.56 compiler crash":
> http://connect.microsoft.com/VisualStudio/feedbackdetail/view/915061/vc12-update-3-rc-boost-1-56-compiler-crash
> This bug is still active.