1.56.0 beta release candidate 2 available for testing
The second release candidate files for 1.56.0 beta 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_b1_rc2.7z) = cd6267325a8dadbb82b384c4776ee450 MD5 (boost-1_56_0_b1_rc2.tar.bz2) = b74cd72043b6b2fa16c6690633acb422 MD5 (boost-1_56_0_b1_rc2.tar.gz) = b51810be6737e73a4deee70e84895ca7 MD5 (boost-1_56_0_b1_rc2.zip) = f4ceb73492ae7d9b1843d841498850e5 Since this is the first post-git release, we are expecting some teething pains with this release. Please test extensively. Besides bug fixes the TypeIndex library has been included, and I think that the problems that mjklaim@gmail.com was seeing have been fixed. I would like to post this to SourceForge Thursday night/Friday morning, if possible. Thank you. --The release managers
On Jul 15, 2014, at 9:58 AM, Marshall Clow <mclow.lists@gmail.com> wrote:
The second release candidate files for 1.56.0 beta 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_b1_rc2.7z) = cd6267325a8dadbb82b384c4776ee450 MD5 (boost-1_56_0_b1_rc2.tar.bz2) = b74cd72043b6b2fa16c6690633acb422 MD5 (boost-1_56_0_b1_rc2.tar.gz) = b51810be6737e73a4deee70e84895ca7 MD5 (boost-1_56_0_b1_rc2.zip) = f4ceb73492ae7d9b1843d841498850e5
Since this is the first post-git release, we are expecting some teething pains with this release. Please test extensively.
Builds successfully with clang-darwin. — Marshall
Le 15/07/14 18:58, Marshall Clow a écrit :
The second release candidate files for 1.56.0 beta 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.
Besides bug fixes the TypeIndex library has been included, and I think that the problems that mjklaim@gmail.com <mailto:mjklaim@gmail.com> was seeing have been fixed.
Hi review managers, please, could you replay to the different request to merge some issues from develop branche? Thanks in advance, Vicente
On Jul 15, 2014, at 10:58 AM, Marshall Clow <mclow.lists@gmail.com> wrote:
The second release candidate files for 1.56.0 beta 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.
Tested with gcc-4.8.2 and OpenMPI 1.6.4 on Linux. ...failed updating 29 targets... ...skipped 38 targets... ...updated 51452 targets… — Noel
Marshall Clow <mclow.lists <at> gmail.com> writes:
The second release candidate files for 1.56.0 beta 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.
Building Boost works with MSVC 2013 Update 3 RC as well as MSVC 2014 CTP 2. With MSVC 2013 Update 3 RC, building a real-world project works in release mode when using the Windows SDK 7.1A (Windows XP toolset). Using smart_ptr in debug mode still fails because of https://svn.boost.org/trac/boost/ticket/10183 Using asio with the updated Windows SDK 8.1 from Update 3 still fails because of https://github.com/chriskohlhoff/asio/pull/22
2014-07-15 20:58 GMT+04:00 Marshall Clow <mclow.lists@gmail.com>:
The second release candidate files for 1.56.0 beta 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_b1_rc2.7z) = cd6267325a8dadbb82b384c4776ee450 MD5 (boost-1_56_0_b1_rc2.tar.bz2) = b74cd72043b6b2fa16c6690633acb422 MD5 (boost-1_56_0_b1_rc2.tar.gz) = b51810be6737e73a4deee70e84895ca7 MD5 (boost-1_56_0_b1_rc2.zip) = f4ceb73492ae7d9b1843d841498850e5
Since this is the first post-git release, we are expecting some teething pains with this release. Please test extensively.
Besides bug fixes the TypeIndex library has been included, and I think that the problems that mjklaim@gmail.com was seeing have been fixed.
Builds OK on Ubintu 14.04 with GCC-4.8.2 (C++03 and C++11 modes) Some of the earlier reported issues remain, but they do not look like critical: Some problems with bzip2 headers detection during build: libs/iostreams/src/bzip2.cpp: 20:56: fatal error: bzlib.h: No such file or directory #include "bzlib.h" // Julian Seward's "bzip.h" header. ^ compilation terminated. "g++-4.8" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_IOSTREAMS_DYN_LINK=1 -DBOOST_IOSTREAMS_USE_DEPRECATED -DNDEBUG -I"." -c -o "bin.v2/libs/iostreams/build/gcc-4.8/release/threading-multi/bzip2.o" "libs/iostreams/src/bzip2.cpp" Warning in locale: ./boost/locale/boundary/segment.hpp:30:35: warning: typedef ‘right_iterator’ locally defined but not used [-Wunused-local-typedefs] typedef RightIterator right_iterator; Compilation of Python failed: In file included from ./boost/python/detail/prefix.hpp:13:0, from ./boost/python/numeric.hpp:8, from libs/python/src/numeric.cpp:6: ./boost/python/detail/wrap_python.hpp:75:24: fatal error: patchlevel.h: No such file or directory #include <patchlevel.h> ^ compilation terminated. "g++-4.8" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.7" -c -o "bin.v2/libs/python/build/gcc-4.8/release/threading-multi/numeric.o" "libs/python/src/numeric.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.8/release/threading-multi/numeric.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.8/release/threading-multi/list.o In file included from ./boost/python/detail/prefix.hpp:13:0, from ./boost/python/list.hpp:8, from libs/python/src/list.cpp:5: ./boost/python/detail/wrap_python.hpp:75:24: fatal error: patchlevel.h: No such file or directory #include <patchlevel.h> ^ compilation terminated. "g++-4.8" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -DNDEBUG -I"." -I"/usr/include/python2.7" -c -o "bin.v2/libs/python/build/gcc-4.8/release/threading-multi/list.o" "libs/python/src/list.cpp" ...failed gcc.compile.c++ bin.v2/libs/python/build/gcc-4.8/release/threading-multi/list.o... gcc.compile.c++ bin.v2/libs/python/build/gcc-4.8/release/threading-multi/long.o In file included from ./boost/python/detail/prefix.hpp:13:0, from ./boost/python/long.hpp:8, from libs/python/src/long.cpp:5: ./boost/python/detail/wrap_python.hpp:75:24: fatal error: patchlevel.h: No such file or directory #include <patchlevel.h> ^ compilation terminated. Warnings in Spirit: ./boost/spirit/home/classic/core/primitives/primitives.hpp:50:68: warning: typedef ‘result_t’ locally defined but not used [-Wunused-local-typedefs] typedef typename parser_result<self_t, ScannerT>::type result_t; ^ ./boost/spirit/home/classic/core/non_terminal/impl/grammar.ipp:285:68: warning: typedef ‘iterator_t’ locally defined but not used [-Wunused-local-typedefs] typedef typename helper_list_t::vector_t::reverse_iterator iterator_t; ^ ./boost/spirit/home/classic/ tree/parse_tree.hpp:79:42: warning: typedef ‘attr_t’ locally defined but not used [-Wunused-local-typedefs] typedef typename match_t::attr_t attr_t; ^ -- Best regards, Antony Polukhin
On Tue, Jul 15, 2014 at 11:58 AM, Marshall Clow <mclow.lists@gmail.com> wrote:
The second release candidate files for 1.56.0 beta 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_b1_rc2.7z) = cd6267325a8dadbb82b384c4776ee450 MD5 (boost-1_56_0_b1_rc2.tar.bz2) = b74cd72043b6b2fa16c6690633acb422 MD5 (boost-1_56_0_b1_rc2.tar.gz) = b51810be6737e73a4deee70e84895ca7 MD5 (boost-1_56_0_b1_rc2.zip) = f4ceb73492ae7d9b1843d841498850e5
Since this is the first post-git release, we are expecting some teething pains with this release. Please test extensively.
Besides bug fixes the TypeIndex library has been included, and I think that the problems that mjklaim@gmail.com was seeing have been fixed.
I would like to post this to SourceForge Thursday night/Friday morning, if possible.
Thank you.
--The release managers
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
This appears to have built successfully for me on Ubuntu 14.04 using GCC 4.8.2. It appears to also have been built successfully on OS X using clang-503.0.40. Both have tons of warnings. It appears most of the warnings are from empty macro arguments while expanding boost.pp and boost.mpl macros clang, "warning: empty macro arguments are a C99 feature [-Wc99-extensions]". There are of course other warnings, but the vast majority is that one. On GCC, the warnings aren't so bad... mostly -Wunused-local-typedefs in boost.python and boost.spirit. However, one of my projects now fails to build using boost 1.56, where before it would succeed on boost 1.55. Further, it appears to only fail when using OSX/clang: Ubuntu/GCC succeeds (well, after correcting for a deprecated header). It appears to only fail when using --std=c++11 (which my project does). If I omit --std=c++11, then the example compiles with one warning. I am not 100% certain if it's a fault in boost 1.56, as locally I am using boost 1.55 from macports. When trying to check boost 1.55 "fresh", I cannot seem to get boost.thread 1.55 to build on OSX/clang, which boost.log requires, so cannot be 100% certain if this is a regression. The issue I am seeing can be reproduced in a boost.log example: Commands: cd ~/Downloads wget http://boost.cowic.de/rc/boost-1_56_0_b1_rc2.tar.bz2 tar -xjf boost-1_56_0_b1_rc2.tar.bz2 cd boost-1_56_0_b1 ./bootstrap.sh ./b2 -j8 # see tons and tons of -Wc99-extensions warnings on OSX/clang cd libs/log/example/settings_file clang main.cpp -I /Users/kbennett/Downloads/boost-1_56_0_b1/ -L /Users/kbennett/Downloads/boost-1_56_0_b1/stage/lib -l boost_log -l boost_log_setup -l boost_date_time -l boost_filesystem -l boost_system -l boost_locale -l boost_thread -DBOOST_ALL_DYN_LINK=1 -l stdc++ --std=c++11 Error Output: In file included from main.cpp:25: In file included from /Users/kbennett/Downloads/boost-1_56_0_b1/boost/log/common.hpp:24: In file included from /Users/kbennett/Downloads/boost-1_56_0_b1/boost/log/sources/global_logger_storage.hpp:21: /Users/kbennett/Downloads/boost-1_56_0_b1/boost/smart_ptr/make_shared_object.hpp:254:20: error: no matching function for call to 'sp_forward' ::new( pv ) T( boost::detail::sp_forward<Args>( args )... ); -- Keith Bennett
On Tue, Jul 15, 2014 at 4:58 PM, Marshall Clow <mclow.lists@gmail.com> wrote:
The second release candidate files for 1.56.0 beta 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.
Looks good on Visual Studio. 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.
We use here VStudio 2010: D:\Develop\SDK and Libraries\boost-1_56_0_b1\boost/atomic/detail/ops_msvc_x86.hpp(250): warning C4100: 'failure_order' : unreferenced formal parameter D:\Develop\SDK and Libraries\boost-1_56_0_b1\boost/atomic/detail/ops_msvc_x86.hpp(250): warning C4100: 'success_order' : unreferenced formal parameter D:\Develop\SDK and Libraries\boost-1_56_0_b1\boost/circular_buffer/base.hpp(191): warning C4172: returning address of local variable or temporary
I compiled 3576ecffc00d97a48bb909e13988120f54b1d7c8 this morning (VS2013 Update 2 32 and 64 bit). I assume that this is equivalent to the beta 2 package? I found no error in the boost build log (using this script: https://www.dropbox.com/s/bggoap0sex4508r/build_boost_github_VS.bat) The full log can be found there: https://www.dropbox.com/s/12ep1cbt6v48us0/20140716-0831-build_boost_github_V... However the install part still have some problems: - signals2 headers where not installed (but are present in the repo working dir); - uuid headers where not installed (but are present in the repo working dir); - program_option.hpp root header was not installed (but is present in the repo working dir), but note that it still appear in the log and seem to compile with no error, the libs are generated in the right place, only the root header is missing in the install directory, not the headers in the program_option header directory; I installed manually these libraries (copy-paste) at this point, then: - function_output_iterator.hpp (in the root include dir) is missing too but is present in the repo working dir (maybe other iterator library headers are missing, I'm not sure). By the way: the full error report is 4>e:\sdk\boost\boost\include\boost-1_56\boost\signals2\detail\null_output_iterator.hpp(14): fatal error C1083: Cannot open include file: 'boost/function_output_iterator.hpp': No such file or directory Which suggest that either I have an unusual setup (but I don't think so?) OR there are no tests for this signals2 code. OR boost build is failing only for me. I re-installed iterator library manually at this point. Then I hit the same link error I reported previously, from optional code apparently: 3>typevaluemap.obj : error LNK2019: unresolved external symbol "class std::basic_ostream<char,struct std::char_traits<char> > & __cdecl boost::operator<<<char,struct std::char_traits<char>,int>(class std::basic_ostream<char,struct std::char_traits<char> > &,class boost::optional<int> const &)" (??$?6DU?$char_traits@D@std@@H@boost @@YAAAV?$basic_ostream@DU?$char_traits@D@std@@@std@@AAV12@ABV?$optional@H@0@@Z) referenced in function "void __cdecl testing_internal::DefaultPrintNonContainerTo<class boost::optional<int>
(class boost::optional<int> const &,class std::basic_ostream<char,struct std::char_traits<char> > *)" (??$DefaultPrintNonContainerTo@V?$optional@H @boost@@@testing_internal@@YAXABV?$optional@H@boost@@PAV?$basic_ostream@DU ?$char_traits@D@std@@@std@@@Z)
I investigated further and found that this error only occur in when this function have been compiled: template< class ValueType > inline boost::optional<ValueType> TypeValueMap::read() const { auto* slot = m_slot_index.find<ValueType>(); if( slot && slot->value ) { return slot->value.get(); } return {}; } With slot's type looking like this: template< class ValueType > struct SlotOf : public Slot { boost::optional<ValueType> value; //... Maybe I did something wrong here? However, the link error report suggest that some boost optional's testing function is called when it shouldn't (this appear when I'm compiling my own project). Note that I detected these errors by trying to compile my own project: there might be others. Joël Lamotte
Please ignore the following part of my previous email: On Wed, Jul 16, 2014 at 9:14 PM, Klaim - Joël Lamotte <mjklaim@gmail.com> wrote:
Then I hit the same link error I reported previously, from optional code apparently:
3>typevaluemap.obj : error LNK2019: unresolved external symbol "class std::basic_ostream<char,struct std::char_traits<char> > & __cdecl boost::operator<<<char,struct std::char_traits<char>,int>(class std::basic_ostream<char,struct std::char_traits<char> > &,class boost::optional<int> const &)" (??$?6DU?$char_traits@D@std@@H@boost @@YAAAV?$basic_ostream@DU?$char_traits@D@std@@@std@@AAV12@ABV?$optional@H @0@@Z) referenced in function "void __cdecl testing_internal::DefaultPrintNonContainerTo<class boost::optional<int>
(class boost::optional<int> const &,class std::basic_ostream<char,struct std::char_traits<char> > *)" (??$DefaultPrintNonContainerTo@V?$optional@H @boost@@@testing_internal@@YAXABV?$optional@H@boost@@PAV?$basic_ostream@DU ?$char_traits@D@std@@@std@@@Z)
I investigated further and found that this error only occur in when this function have been compiled:
template< class ValueType > inline boost::optional<ValueType> TypeValueMap::read() const { auto* slot = m_slot_index.find<ValueType>(); if( slot && slot->value ) { return slot->value.get(); } return {}; }
With slot's type looking like this:
template< class ValueType > struct SlotOf : public Slot { boost::optional<ValueType> value; //...
Maybe I did something wrong here? However, the link error report suggest that some boost optional's testing function is called when it shouldn't (this appear when I'm compiling my own project).
I found that it's a link issue related to GTest macros which apparently generate this error when I try to test the optional result implicitely: #include <gtest/gtest.h> #include <boost/optional.hpp> TEST( blah, blah ) { boost::optional<int> k = 42; EXPECT_EQ( 42, k ); // this will trigger the link error } Replacing the pointed line by EXPECT_EQ( 42, k.get() ); // OK seems to fix the issue. Sorry for the noise!
On Wed, Jul 16, 2014 at 9:59 PM, Klaim - Joël Lamotte <mjklaim@gmail.com> wrote:
I found that it's a link issue related to GTest macros which apparently generate this error when I try to test the optional result implicitely:
Note that this was not the case with Boost 1.55
On Tue, Jul 15, 2014 at 6:58 PM, Marshall Clow <mclow.lists@gmail.com> wrote:
The second release candidate files for 1.56.0 beta 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.
By the way, could you add tags to mark the revisions corresponding to betas?
participants (2)
-
Antony Polukhin -
Belcourt, Kenneth -
gast128 -
Keith Bennett -
Klaim - Joël Lamotte -
Marcel Raad -
Marshall Clow -
Tom Kent -
Vicente J. Botet Escriba