Boost 1.63.0 Release Candidate 1
The release candidates for the 1.63.0 release are now available at: https://sourceforge.net/projects/boost/files/boost/1.63.0/ The SHA256 checksums are as follows: 010699561c6011e6d97dc453d55bc5e54cdc192622434eff7b8ac559efac846c boost_1_63_0_rc1.7z d8ebf8d90b2f823f04119445ac339d704395d655907333ec0fab863040119d24 boost_1_63_0_rc1.tar.bz2 dabe29b8a60369ae7c15c20681a32717f3c37d97e5dc6d39c5b2fd0494b8e995 boost_1_63_0_rc1.tar.gz 1683942022fd63c205c48fb2155af6094c67ef67aa13ffb3e1db78fecf817efe boost_1_63_0_rc1.zip 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. -- The release managers
On Sat, Dec 10, 2016 at 11:50 AM, Marshall Clow <mclow.lists@gmail.com> wrote:
The release candidates for the 1.63.0 release are now available at:
https://sourceforge.net/projects/boost/files/boost/1.63.0/
The SHA256 checksums are as follows:
010699561c6011e6d97dc453d55bc5e54cdc192622434eff7b8ac559efac846c boost_1_63_0_rc1.7z d8ebf8d90b2f823f04119445ac339d704395d655907333ec0fab863040119d24 boost_1_63_0_rc1.tar.bz2 dabe29b8a60369ae7c15c20681a32717f3c37d97e5dc6d39c5b2fd0494b8e995 boost_1_63_0_rc1.tar.gz 1683942022fd63c205c48fb2155af6094c67ef67aa13ffb3e1db78fecf817efe boost_1_63_0_rc1.zip
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 have built the RC using clang (both Apple's release clang, and a fairly recent built from source version) on Mac OS X 10.11 using libc++ and C++03/11/14 and 1z. $ clang --version Apple LLVM version 8.0.0 (clang-800.0.42.1) $ totclang --version clang version 4.0.0 (trunk 289079) At all language variants, with Apple's clang, Boost.Context fails to build: It also fails to build with ToT clang at all language variants. libs/context/src/asm/make_x86_64_sysv_macho_gas.S:70:5: error: unknown use
of instruction mnemonic without a size suffix jmp %rbx ^ "/Sources/LLVM/bin/bin/clang++" -x assembler-with-cpp -O3 -O3 -Wno-inline -Wall -m64 -DBOOST_ALL_NO_LIB=1 -DBOOST_CHRONO_STATIC_LINK=1 -DBOOST_CONTEXT_SOURCE -DBOOST_DISABLE_ASSERTS -DBOOST_SYSTEM_NO_DEPRECATED -DBOOST_SYSTEM_STATIC_LINK=1 -DBOOST_THREAD_BUILD_LIB=1 -DBOOST_THREAD_POSIX -DBOOST_THREAD_USE_LIB=1 -DNDEBUG -I"." -c -o "bin.v2/libs/context/build/clang-darwin-tot03/release/link-static/threading-multi/asm/make_x86_64_sysv_macho_gas.o" "libs/context/src/asm/make_x86_64_sysv_macho_gas.S" ...failed clang-darwin.compile.asm bin.v2/libs/context/build/clang-darwin-tot03/release/link-static/threading-multi/asm/make_x86_64_sysv_macho_gas.o...
Also, with ToT clang and C++1z, three additional failures occur:
clang-darwin.compile.c++ bin.v2/libs/fiber/build/clang-darwin-tot1z/release/link-static/threading-multi/context.o In file included from libs/fiber/src/context.cpp:7: In file included from ./boost/fiber/context.hpp:21: In file included from ./boost/context/execution_context.hpp:17: ./boost/context/execution_context_v2.hpp:110:18: error: call to 'apply' is ambiguous Ctx cc = apply( std::move( fn_), std::move( tpl) ); ^~~~~ ./boost/context/execution_context_v2.hpp:377:18: note: in instantiation of member function 'boost::context::detail::record<boost::context::execution_context<boost::fibers::detail::data_t *>, boost::context::basic_fixedsize_stack<boost::context::stack_traits>, (lambda at libs/fiber/src/context.cpp:216:11)>::run' requested here t = rec->run( t); ^ ./boost/context/execution_context_v2.hpp:455:56: note: in instantiation of function template specialization 'boost::context::detail::context_entry<boost::context::detail::record<boost::context::execution_context<boost::fibers::detail::data_t *>, boost::context::basic_fixedsize_stack<boost::context::stack_traits>, (lambda at libs/fiber/src/context.cpp:216:11)> >' requested here const fcontext_t fctx = make_fcontext( sp, size, & context_entry< record_t >); ^ ./boost/context/execution_context_v2.hpp:191:24: note: in instantiation of function template specialization 'boost::context::detail::context_create<boost::context::execution_context<boost::fibers::detail::data_t *>, boost::context::basic_fixedsize_stack<boost::context::stack_traits>, (lambda at libs/fiber/src/context.cpp:216:11)>' requested here fctx_( detail::context_create< execution_context >( ^ libs/fiber/src/context.cpp:215:5: note: in instantiation of function template specialization 'boost::context::execution_context<boost::fibers::detail::data_t *>::execution_context<boost::context::basic_fixedsize_stack<boost::context::stack_traits>, (lambda at libs/fiber/src/context.cpp:216:11)>' requested here ctx_{ std::allocator_arg, palloc, salloc, ^ /Sources/LLVM/bin/bin/../include/c++/v1/tuple:1362:26: note: candidate function [with _Fn = (lambda at libs/fiber/src/context.cpp:216:11), _Tuple = std::__1::tuple<boost::context::execution_context<boost::fibers::detail::data_t *> &&, boost::fibers::detail::data_t *>] constexpr decltype(auto) apply(_Fn && __f, _Tuple && __t) ^ ./boost/context/detail/apply.hpp:54:1: note: candidate function [with Fn = (lambda at libs/fiber/src/context.cpp:216:11), Tpl = std::__1::tuple<boost::context::execution_context<boost::fibers::detail::data_t *> &&, boost::fibers::detail::data_t *>] apply( Fn && fn, Tpl && tpl) ^ In file included from libs/fiber/src/context.cpp:7: In file included from ./boost/fiber/context.hpp:29: In file included from ./boost/fiber/detail/data.hpp:13: In file included from ./boost/fiber/detail/spinlock.hpp:16: ./boost/fiber/detail/spinlock_ttas.hpp:36:62: warning: private field 'pad' is not used [-Wunused-private-field] char pad[cacheline_length]; ^ In file included from libs/fiber/src/context.cpp:7: In file included from ./boost/fiber/context.hpp:29: In file included from ./boost/fiber/detail/data.hpp:13: In file included from ./boost/fiber/detail/spinlock.hpp:17: ./boost/fiber/detail/spinlock_ttas_adaptive.hpp:38:61: warning: private field 'pad' is not used [-Wunused-private-field] char pad[cacheline_length]; ^ In file included from libs/fiber/src/context.cpp:14: In file included from ./boost/fiber/scheduler.hpp:24: ./boost/fiber/detail/context_mpsc_queue.hpp:42:57: warning: private field 'pad_' is not used [-Wunused-private-field] char pad_[cacheline_length]; ^ 3 warnings and 1 error generated.
"/Sources/LLVM/bin/bin/clang++" -x c++ -std=c++1z -stdlib=libc++ -I /Sources/LLVM/llvm/projects/libcxx -O3 -O3 -Wno-inline -Wall -DBOOST_ALL_NO_LIB=1 -DBOOST_DISABLE_ASSERTS -DBOOST_FIBERS_SOURCE -DNDEBUG -I"." -c -o "bin.v2/libs/fiber/build/clang-darwin-tot1z/release/link-static/threading-multi/context.o" "libs/fiber/src/context.cpp"
...failed clang-darwin.compile.c++ bin.v2/libs/fiber/build/clang-darwin-tot1z/release/link-static/threading-multi/context.o...
======
clang-darwin.compile.c++ bin.v2/libs/test/build/clang-darwin-tot1z/release/link-static/threading-multi/compiler_log_formatter.o In file included from libs/test/src/compiler_log_formatter.cpp:16: ./boost/test/impl/compiler_log_formatter.ipp:151:70: error: incompatible operand types ('basic_cstring<...>' and 'const basic_cstring<...>') output << "fatal error: in \"" << (loc.m_function.is_empty() ? test_phase_identifier() : loc.m_function ) << "\": " ^
> 1 error generated.
>
> "/Sources/LLVM/bin/bin/clang++" -x c++ -Wno-c99-extensions
-Wno-variadic-macros -std=c++1z -stdlib=libc++ -I
/Sources/LLVM/llvm/projects/libcxx -O3 -O3 -Wno-inline -Wall -pedantic
-DBOOST_ALL_NO_LIB=1 -DBOOST_CHRONO_STATIC_LINK=1
-DBOOST_SYSTEM_NO_DEPRECATED -DBOOST_SYSTEM_STATIC_LINK=1
-DBOOST_TIMER_STATIC_LINK=1 -DNDEBUG -I"." -c -o
"bin.v2/libs/test/build/clang-darwin-tot1z/release/link-static/threading-multi/compiler_log_formatter.o"
"libs/test/src/compiler_log_formatter.cpp"
>
> ...failed clang-darwin.compile.c++
bin.v2/libs/test/build/clang-darwin-tot1z/release/link-static/threading-multi/compiler_log_formatter.o...
>
> ======
>
> clang-darwin.compile.c++
bin.v2/libs/program_options/build/clang-darwin-tot1z/release/threading-multi/variables_map.o
> libs/program_options/src/variables_map.cpp:71:83: error: incompatible
operand types ('const basic_string<...>' and 'basic_string<...>')
> string original_token =
options.options[i].original_tokens.size() ?
>
^
> 1 error generated.
>
> "/Sources/LLVM/bin/bin/clang++" -x c++ -std=c++1z -stdlib=libc++ -I
/Sources/LLVM/llvm/projects/libcxx -O3 -O3 -Wno-inline -Wall
-DBOOST_ALL_NO_LIB=1 -DBOOST_PROGRAM_OPTIONS_DYN_LINK=1 -DNDEBUG -I"." -c
-o
"bin.v2/libs/program_options/build/clang-darwin-tot1z/release/threading-multi/variables_map.o"
"libs/program_options/src/variables_map.cpp"
>
> ...failed clang-darwin.compile.c++
bin.v2/libs/program_options/build/clang-darwin-tot1z/release/threading-multi/variables_map.o...
>
> ======
-- Marshall
On 10 December 2016 at 19:50, Marshall Clow <mclow.lists@gmail.com> wrote:
The release candidates for the 1.63.0 release are now available at:
Documentation: http://beta.boost.org/doc/libs/1_63_0/ Release notes: http://beta.boost.org/users/history/in_progress.html Sorry that those links are on the beta site, I'm making some changes to how the release process is handled, and it isn't quite ready yet.
On Sat, Dec 10, 2016 at 1:50 PM, Marshall Clow <mclow.lists@gmail.com> wrote:
The release candidates for the 1.63.0 release are now available at:
https://sourceforge.net/projects/boost/files/boost/1.63.0/
The SHA256 checksums are as follows:
010699561c6011e6d97dc453d55bc5e54cdc192622434eff7b8ac559efac846c boost_1_63_0_rc1.7z d8ebf8d90b2f823f04119445ac339d704395d655907333ec0fab863040119d24 boost_1_63_0_rc1.tar.bz2 dabe29b8a60369ae7c15c20681a32717f3c37d97e5dc6d39c5b2fd0494b8e995 boost_1_63_0_rc1.tar.gz 1683942022fd63c205c48fb2155af6094c67ef67aa13ffb3e1db78fecf817efe boost_1_63_0_rc1.zip
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.
Windows builds look good. toolset arch compile Link Execute msvc-8.0 32 X X X msvc-8.0 64 X X X msvc-9.0 32 X X X msvc-9.0 64 X X X msvc-10.0 32 X X X msvc-10.0 64 X X X msvc-11.0 32 X X X msvc-11.0 64 X X X msvc-12.0 32 X X X msvc-12.0 64 X X X msvc-14.0 32 X X X msvc-14.0 64 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. Full output is at: https://gist.github.com/teeks99/ccf20ea258050354d883b1acd93f16fc Tom
On 10 December 2016 at 19:50, Marshall Clow <mclow.lists@gmail.com> wrote:
The release candidates for the 1.63.0 release are now available at:
https://sourceforge.net/projects/boost/files/boost/1.63.0/
The SHA256 checksums are as follows:
010699561c6011e6d97dc453d55bc5e54cdc192622434eff7b8ac559efac846c boost_1_63_0_rc1.7z d8ebf8d90b2f823f04119445ac339d704395d655907333ec0fab863040119d24 boost_1_63_0_rc1.tar.bz2 dabe29b8a60369ae7c15c20681a32717f3c37d97e5dc6d39c5b2fd0494b8e995 boost_1_63_0_rc1.tar.gz 1683942022fd63c205c48fb2155af6094c67ef67aa13ffb3e1db78fecf817efe boost_1_63_0_rc1.zip
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.
The algorithm documentation is in the wrong place. It looks like it was accidentally moved into the combined documentation in the changes to automate documentation building.
pull request https://github.com/boostorg/config/pull/106 has to be merged first - than I can merge bugfixes to master
* Marshall Clow wrote:
The release candidates for the 1.63.0 release are now available at:
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.
One thing I mentioned [1] about 1.62 and several older versions, a few days ago, is also present in this RC: In the "toolset=msvc-14.0 link=shared runtime-link=shared" build, several static libraries are built for no discernible reason. As far as I can tell by watching file system operations (using Sysinternals procmon), these libraries are not accessed again after creation. There is nothing documented about this behavior, and I suspect a bug in the build process. The unexpected files are: libboost_chrono-vc140-mt-1_63.lib libboost_system-vc140-mt-1_63.lib libboost_timer-vc140-mt-1_63.lib libboost_unit_test_framework-vc140-mt-1_63.lib These two are probably expected, because there are no DLLs built for them at all: libboost_test_exec_monitor-vc140-mt-1_63.lib libboost_exception-vc140-mt-1_63.lib Sorry for harping on this, but I still don't understand what's happening here, and would really like to. [1] http://lists.boost.org/boost-users/2016/12/86959.php -- Christian
On 12/10/2016 08:50 PM, Marshall Clow wrote:
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 did not build the Beta yet (buildserver is currently running) but I found two new *.o files in libs/config/checks/architecture/bin/gcc-4.9.2/debug/. Are they in the archive for a purpose or just an oversight that slipped into the beta? Norbert
On Mon, Dec 12, 2016 at 3:34 PM, Norbert Wenzel < norbert.wenzel.lists@gmail.com> wrote:
On 12/10/2016 08:50 PM, Marshall Clow wrote:
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 did not build the Beta yet (buildserver is currently running) but I found two new *.o files in libs/config/checks/architecture/bin/gcc-4.9.2/debug/. Are they in the archive for a purpose or just an oversight that slipped into the beta?
You mean that they are in the archive itself straight from the download? If yes, they should not be there. And are strays from the doc building process. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
Yes, I found these *.o files in the archive from the download page. I downloaded the *.7z version. (Sorry for my bad mail formatting, I'm in webmail right now.)
please add two patches in order to fix two bugs: e71b38c1d2cc8ab6d896eeeff012ba9a934e583b bb8b7f5dbf0015232e08906378c49d0af57eb6e1 (boost.context, branch master)
please add commit fffb7e7f320162775382d73ea0ac5434d7d55f0e (boost.fiber) to boost-1.63.0 - the patches fixes the mingw issue
On Sat, Dec 10, 2016 at 11:50 AM, Marshall Clow <mclow.lists@gmail.com> wrote:
The release candidates for the 1.63.0 release are now available at:
https://sourceforge.net/projects/boost/files/boost/1.63.0/
The SHA256 checksums are as follows:
010699561c6011e6d97dc453d55bc5e54cdc192622434eff7b8ac559efac846c boost_1_63_0_rc1.7z d8ebf8d90b2f823f04119445ac339d704395d655907333ec0fab863040119d24 boost_1_63_0_rc1.tar.bz2 dabe29b8a60369ae7c15c20681a32717f3c37d97e5dc6d39c5b2fd0494b8e995 boost_1_63_0_rc1.tar.gz 1683942022fd63c205c48fb2155af6094c67ef67aa13ffb3e1db78fecf817efe boost_1_63_0_rc1.zip
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.
Just a heads-up -- We're waiting for the bots to cycle for a Boost.Config change, and then we'll pick a couple bug fixes and turn an RC2. -- Marshall
participants (7)
-
Christian Ullrich -
Daniel James -
Marshall Clow -
Norbert Wenzel -
Oliver Kowalke -
Rene Rivera -
Tom Kent