1.57.0 beta 1 release candidates available for testing
Release candidate files for 1.57.0 beta 1 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_57_0_b1_rc1.7z) = 8633fbf5ebb7eaabcb0f309c14646ae3 MD5 (boost_1_57_0_b1_rc1.tar.bz2) = 8e76f98146793f0fbd2492a9151c405b MD5 (boost_1_57_0_b1_rc1.tar.gz) = d41ff3ffb36ac84ff5bf34f799308907 MD5 (boost_1_57_0_b1_rc1.zip) = 8a844dc36284247b2e936f2120e118b2 Thanks! -- The release managers
Marshall Clow
Release candidate files for 1.57.0 beta 1 are available [...] Please report both success and failure, and anything else that is noteworthy.
Everything tested in 32-bit and 64-bit, debug and release mode: Visual C++ 2013 Update 4 RC: all libraries built successfully Visual C++ 14 CTP 4 without BOOST_MSVC_ENABLE_2014_JUN_CTP: all libraries built successfully (but some are not usable, mostly because of missing noexcept) Visual C++ 14 CTP 4 with BOOST_MSVC_ENABLE_2014_JUN_CTP: compile errors in Graph and Log because of is_nothrow_move_assignable in TypeTraits All projects using Boost I tried (Debug 32-bit + 64-bit) compiled successfully with MSVC12. For MSVC14, TypeTraits 9de6a49 is missing in master.
Release candidate files for 1.57.0 beta 1 are available [...] Please report both success and failure, and anything else that is noteworthy.
Everything tested in 32-bit and 64-bit, debug and release mode:
Visual C++ 2013 Update 4 RC: all libraries built successfully
Visual C++ 14 CTP 4 without BOOST_MSVC_ENABLE_2014_JUN_CTP: all libraries built successfully (but some are not usable, mostly because of missing noexcept)
Is this a Config issue or what exactly?
Visual C++ 14 CTP 4 with BOOST_MSVC_ENABLE_2014_JUN_CTP: compile errors in Graph and Log because of is_nothrow_move_assignable in TypeTraits
All projects using Boost I tried (Debug 32-bit + 64-bit) compiled successfully with MSVC12. For MSVC14, TypeTraits 9de6a49 is missing in master.
Ah, my bad, I've just merged those missing fixes to master - do these fix the is_nothrow_move_assignable issue as well? John.
John Maddock
Visual C++ 14 CTP 4 without BOOST_MSVC_ENABLE_2014_JUN_CTP: all libraries built successfully (but some are not usable, mostly because of missing noexcept)
Is this a Config issue or what exactly?
One issue was that MSVC14's std::atomic<T> requires T to have a noexcept default constructor. Without BOOST_MSVC_ENABLE_2014_JUN_CTP, this breaks Boost.Lockfree, for example.
Visual C++ 14 CTP 4 with BOOST_MSVC_ENABLE_2014_JUN_CTP: compile errors in Graph and Log because of is_nothrow_move_assignable in TypeTraits
OK, I managed to get CTP4 installed and have 2 updates: For Boost.Config: https://github.com/boostorg/config/commit/d9026f1d45f28947024a3f2d393e138ff1... a mostly minor update. For TypeTraits: https://github.com/boostorg/type_traits/commit/5c0474dbc7d6ed28bacf643481398... I suspect you're not going to like the latter as it basically disables working versions of is_nothrow* for msvc-14. The reason is that is appears that Boost.Log ends up using noexcept(non_compiling_expression) which requires SFINAE expression support. I'm not sure about this though because the error messages from the Boost.Log failed build are pretty inscrutable - they refer to boost::spirit::info being undefined when it clearly is, and also the instantiation backtrace goes nowhere, so I suspect a compiler bug and/or noexcept being too immature on this compiler for serious use. I'll double check MSVC-14 noexcept support with the multiprecision tests as they make quite a bit of use of this. Any other libraries? One final question - to what extent should we try to support this compiler in 1.57 given that it's still in alpha? John.
John Maddock
OK, I managed to get CTP4 installed and have 2 updates:
For Boost.Config:
a mostly minor update.
Great, thanks! According to the feature table, auto return types (BOOST_NO_CXX14_RETURN_TYPE_DEDUCTION) are also supported.
For TypeTraits:
I suspect you're not going to like the latter as it basically disables working versions of is_nothrow* for msvc-14. The reason is that is appears that Boost.Log ends up using noexcept(non_compiling_expression) which requires SFINAE expression support.
I also think it's the best solution. You can also delete the "!::boost::is_const<T>::value" with it now.
For Boost.Config:
a mostly minor update.
Great, thanks! According to the feature table, auto return types (BOOST_NO_CXX14_RETURN_TYPE_DEDUCTION) are also supported.
Confirmed - it passes our test case anyway, feature enabled.
For TypeTraits:
I suspect you're not going to like the latter as it basically disables working versions of is_nothrow* for msvc-14. The reason is that is appears that Boost.Log ends up using noexcept(non_compiling_expression) which requires SFINAE expression support.
I also think it's the best solution. You can also delete the "!::boost::is_const<T>::value" with it now.
Done. Marshall - is it OK to merge these fixes after the beta is out? Thanks, John.
On Oct 20, 2014, at 3:52 AM, John Maddock
For Boost.Config:
a mostly minor update.
Great, thanks! According to the feature table, auto return types (BOOST_NO_CXX14_RETURN_TYPE_DEDUCTION) are also supported.
Confirmed - it passes our test case anyway, feature enabled.
For TypeTraits:
I suspect you're not going to like the latter as it basically disables working versions of is_nothrow* for msvc-14. The reason is that is appears that Boost.Log ends up using noexcept(non_compiling_expression) which requires SFINAE expression support.
I also think it's the best solution. You can also delete the "!::boost::is_const<T>::value" with it now.
Done.
Marshall - is it OK to merge these fixes after the beta is out?
Absolutely. — Marshall
On 18.10.2014 00:40, Marshall Clow wrote:
Release candidate files for 1.57.0 beta 1 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.
x86_64-linux-gnu-g++ (native): Builds successfully. arm-linux-androideabi-g++: Fails to link due to missing librt. mipsel-linux-android-g++: Fails to link due to missing librt. x86_64-w64-mingw32-g++: Chokes on libs/context/src/asm/make_x86_64_sysv_elf_gas.S. x86_64-w64-mingw32-g++: Chokes on libs/context/src/asm/make_x86_64_sysv_elf_gas.S. clang++ (native): Builds successfully. pnacl-clang++: Lots of errors, including: Unrecognized option: -shared ./boost/system/detail/error_code.ipp:120:16: error: assigning to 'int' from incompatible type 'char *' ./boost/system/detail/error_code.ipp:261:10: error: duplicate case value: '104' and '__elast1' both equal '104' ./boost/chrono/detail/inlined/posix/process_cpu_clocks.hpp:31:33: error: use of undeclared identifier '_SC_CLK_TCK' ./boost/thread/pthread/thread_data.hpp:62:23: error: no matching function for call to 'pthread_attr_getstacksize' The failures for Android look serious but fixable. The failures for mingw seem to only affect Boost.Context which is inherently non-portable, so I don't consider them serious. The failures for pnacl look serious, but their sheer number probably makes fixing them for this release impractical. -- Rainer Deyke (rainerd@eldwood.com)
On Oct 17, 2014, at 3:40 PM, Marshall Clow
Release candidate files for 1.57.0 beta 1 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.
I have successfully build the RC on Mac OS X with the following configurations: clang -std=c++03 clang -std=c++11 clang -std=c++14 gcc 4.9.0 -std=c++03 gcc 4.9.0 -std=c++11 — Marshall
Le 18/10/14 00:40, Marshall Clow a écrit :
Release candidate files for 1.57.0 beta 1 are available at http://boost.cowic.de/rc/
Hi, could I merge the following to the master branch? https://github.com/boostorg/thread/commit/3e28ea806c412c697f134fdaacbccc9b64... https://github.com/boostorg/thread/commit/1029fa9c5937269c9a65848972da7d8bbe... https://github.com/boostorg/thread/commit/63dd439992cbc6d62f0af442f4669121e0... This fixes "deferred/ready futures on variadic when_all/when_any." Best, Vicente
On Oct 19, 2014, at 2:22 PM, Vicente J. Botet Escriba
Le 18/10/14 00:40, Marshall Clow a écrit :
Release candidate files for 1.57.0 beta 1 are available at http://boost.cowic.de/rc/
Hi, could I merge the following to the master branch?
https://github.com/boostorg/thread/commit/3e28ea806c412c697f134fdaacbccc9b64... https://github.com/boostorg/thread/commit/1029fa9c5937269c9a65848972da7d8bbe... https://github.com/boostorg/thread/commit/63dd439992cbc6d62f0af442f4669121e0...
This fixes "deferred/ready futures on variadic when_all/when_any.”
Vicente — I’d appreciate if you would merge those *after* we release the beta. There will be about a week where the master branch will be open again. — Marshall (who would like to get the beta out to a wide audience sooner, rather than later)
Le 20/10/14 07:29, Marshall Clow a écrit :
On Oct 19, 2014, at 2:22 PM, Vicente J. Botet Escriba
mailto:vicente.botet@wanadoo.fr> wrote: Le 18/10/14 00:40, Marshall Clow a écrit :
Release candidate files for 1.57.0 beta 1 are available at http://boost.cowic.de/rc/
Hi, could I merge the following to the master branch?
https://github.com/boostorg/thread/commit/3e28ea806c412c697f134fdaacbccc9b64... https://github.com/boostorg/thread/commit/1029fa9c5937269c9a65848972da7d8bbe... https://github.com/boostorg/thread/commit/63dd439992cbc6d62f0af442f4669121e0...
This fixes "deferred/ready futures on variadic when_all/when_any."
Vicente ---
I'd appreciate if you would merge those *after* we release the beta. There will be about a week where the master branch will be open again.
I will do it then. Best, Vicente
I had failures in msvc-8.0 with the log library.
There were many, one was this:
.\boost/log/detail/light_function_pp.hpp(59) : error C2248:
'boost::rv<T>::rv' : cannot access private member declared in class
'boost::rv<T>'
with
[
T=boost::log::v2s_mt_nt5::aux::light_function
Release candidate files for 1.57.0 beta 1 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_57_0_b1_rc1.7z) = 8633fbf5ebb7eaabcb0f309c14646ae3 MD5 (boost_1_57_0_b1_rc1.tar.bz2) = 8e76f98146793f0fbd2492a9151c405b MD5 (boost_1_57_0_b1_rc1.tar.gz) = d41ff3ffb36ac84ff5bf34f799308907 MD5 (boost_1_57_0_b1_rc1.zip) = 8a844dc36284247b2e936f2120e118b2
Thanks!
-- The release managers
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
On Mon, Oct 20, 2014 at 6:04 AM, Tom Kent
wrote: I had failures in msvc-8.0 with the log library.
Full build results: 32 bit - http://pastebin.com/E3jkw44s 64 bit - http://pastebin.com/gASZ0nCn
The correct 64-bit log: http://pastebin.com/uAVJnPjY
Marshall Clow
Release candidate files for 1.57.0 beta 1 are available [...] 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.
range/detail/any_iterator.hpp is broken because it expects postfix_increment_proxy and writable_postfix_increment_proxy to be in namespace boost::detail, but they are in boost::iterators::detail now. Those errors are also visible in all of the type_erased_* regression tests of range.
On Oct 20, 2014, at 7:06 AM, Marcel Raad
Marshall Clow
writes: Release candidate files for 1.57.0 beta 1 are available [...] 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.
range/detail/any_iterator.hpp is broken because it expects postfix_increment_proxy and writable_postfix_increment_proxy to be in namespace boost::detail, but they are in boost::iterators::detail now.
Those errors are also visible in all of the type_erased_* regression tests of range.
I made an executive decision to push the beta out with this problem (and the MSVC 8.0 bugs, too), because I wanted to get a wider audience looking at the beta. Thanks for reporting this, and now let’s fix them. — Marshall
boost serialization is still broken(said so:
http://article.gmane.org/gmane.comp.lib.boost.user/82715 ) and to date i
do know no workaround to get my library to work on fx Arch Linux without
telling users to rebuild with boost 1.55 (or sending them a saved
package from my system...)
Error message:
In file included from
/home/ulfi/Shark/include/shark/Data/Impl/Dataset.inl:39:0,
from /home/ulfi/Shark/include/shark/Data/Dataset.h:56,
from
/home/ulfi/Shark/include/shark/Models/Clustering/Centroids.h:39,
from /home/ulfi/Shark/src/Models/Centroids.cpp:35:
/home/ulfi/include/boost/serialization/shared_ptr.hpp: In instantiation
of 'void boost::serialization::load(Archive&, boost::shared_ptr<U>&,
unsigned int) [with Archive = boost::archive::polymorphic_iarchive; T =
shark::blas::matrix
On Oct 20, 2014, at 7:06 AM, Marcel Raad
wrote: Marshall Clow
writes: Release candidate files for 1.57.0 beta 1 are available [...] 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. range/detail/any_iterator.hpp is broken because it expects postfix_increment_proxy and writable_postfix_increment_proxy to be in namespace boost::detail, but they are in boost::iterators::detail now.
Those errors are also visible in all of the type_erased_* regression tests of range. I made an executive decision to push the beta out with this problem (and the MSVC 8.0 bugs, too), because I wanted to get a wider audience looking at the beta.
Thanks for reporting this, and now let’s fix them.
— Marshall
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
participants (7)
-
John Maddock
-
Marcel Raad
-
Marshall Clow
-
oswin krause
-
Rainer Deyke
-
Tom Kent
-
Vicente J. Botet Escriba