[1.53.0] Beta release candidates 2 now available for testing
Updated release candidate files for 1.53.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: 579b680bf55f53cd6d50adc391cb6c23 *boost_1_53_0_beta1_rc2.tar.gz 02098bb6da0e9c10712ae63c16e6aeea *boost_1_53_0_beta1_rc2.tar.bz2 998e2616a66c50e5693f563afb899002 *boost_1_53_0_beta1_rc2.zip e4fde6a869a3e21f8751ba8b7fd471a8 *boost_1_53_0_beta1_rc2.7z There were three changes between rc1 and rc2: * Fixes for compilation errors in Boost.Serialization * Documentation updates for Boost.SmartPtr * Updates to Boost.Threads Thanks, --The release managers
On Jan 4, 2013, at 11:25 AM, Marshall Clow <mclow.lists@gmail.com> wrote:
Updated release candidate files for 1.53.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.
I built the RC on Mac OS X with both clang and gcc w/o errors. However, when I built using clang and libc++ in C++11 mode, I found two problems: ./b2 toolset=clang cxxflags="-std=c++11 -stdlib=libc++ -Wno-unused-variable" linkflags="-stdlib=libc++" Issue #1:
clang-darwin.compile.c++ bin.v2/libs/chrono/build/clang-darwin-11/release/threading-multi/chrono.o In file included from libs/chrono/src/chrono.cpp:14: In file included from ./boost/chrono/detail/inlined/chrono.hpp:13: In file included from ./boost/chrono/chrono.hpp:11: ./boost/chrono/duration.hpp:353:49: error: constexpr function never produces a constant expression static BOOST_CHRONO_LIB_CONSTEXPR float lowest() BOOST_CHRONO_LIB_NOEXCEPT_OR_THROW ^ ./boost/chrono/duration.hpp:355:21: note: non-constexpr function 'max' cannot be used in a constant expression return -(std::numeric_limits<float>::max) (); ^ /usr/bin/../lib/c++/v1/limits:443:43: note: declared here _LIBCPP_INLINE_VISIBILITY static type max() _NOEXCEPT {return __base::max();} ^
This is a bug in libc++; std::numeric_limits<>::max() is not marked as constexpr. This has been fixed in the libc++ trunk, and should appear in the next clang/libc++ release. Issue #2:
clang-darwin.compile.c++ bin.v2/libs/filesystem/build/clang-darwin-11/release/threading-multi/path.o In file included from libs/filesystem/src/path.cpp:39: In file included from ./boost/filesystem/detail/utf8_codecvt_facet.hpp:18: ./boost/detail/utf8_codecvt_facet.hpp:171:17: warning: 'boost::filesystem::detail::utf8_codecvt_facet::do_length' hides overloaded virtual function [-Woverloaded-virtual] virtual int do_length( ^ /usr/bin/../lib/c++/v1/__locale:920:17: note: hidden overloaded virtual function 'std::__1::codecvt<wchar_t, char, __mbstate_t>::do_length' declared here virtual int do_length(state_type&, const extern_type* __frm, const extern_type* __end, size_t __mx) const; ^
This is my fault - there's a change that I failed to merge. I will fix this before the release. -- Marshall
Marshall Clow wrote:
This is my fault - there's a change that I failed to merge. I will fix this before the release.
Marshall You might want to think about this some more. I know that this fix creates a failure in a test case in the serialization library. It turns out that isn't exactly obvious what the correct fix is and, in my view, needs some more more investigation. I also believe that other users of codecvt facet (e.g. file system) have some issues with this. I would suggest that we try get a fix into the next release rather than this one. I don't believe this is a new issue nor an urgent one and that letting this slide one more release is the best option. Robert Ramey
-- Marshall
On Jan 5, 2013, at 9:37 AM, Marshall Clow <mclow.lists@gmail.com> wrote:
On Jan 4, 2013, at 11:25 AM, Marshall Clow <mclow.lists@gmail.com> wrote:
Updated release candidate files for 1.53.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.
I built the RC on Mac OS X with both clang and gcc w/o errors. However, when I built using clang and libc++ in C++11 mode, I found two problems:
./b2 toolset=clang cxxflags="-std=c++11 -stdlib=libc++ -Wno-unused-variable" linkflags="-stdlib=libc++"
Issue #1:
clang-darwin.compile.c++ bin.v2/libs/chrono/build/clang-darwin-11/release/threading-multi/chrono.o In file included from libs/chrono/src/chrono.cpp:14: In file included from ./boost/chrono/detail/inlined/chrono.hpp:13: In file included from ./boost/chrono/chrono.hpp:11: ./boost/chrono/duration.hpp:353:49: error: constexpr function never produces a constant expression static BOOST_CHRONO_LIB_CONSTEXPR float lowest() BOOST_CHRONO_LIB_NOEXCEPT_OR_THROW ^ ./boost/chrono/duration.hpp:355:21: note: non-constexpr function 'max' cannot be used in a constant expression return -(std::numeric_limits<float>::max) (); ^ /usr/bin/../lib/c++/v1/limits:443:43: note: declared here _LIBCPP_INLINE_VISIBILITY static type max() _NOEXCEPT {return __base::max();} ^
This is a bug in libc++; std::numeric_limits<>::max() is not marked as constexpr. This has been fixed in the libc++ trunk, and should appear in the next clang/libc++ release.
And it has been fixed in Xcode 4.6, released today. -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki
participants (1)
-
Marshall Clow -
Robert Ramey