Boost logo

Boost :

Subject: Re: [boost] [release] Boost 1.64.0 Beta 1
From: Deniz Bahadir (dbahadir_at_[hidden])
Date: 2017-03-27 10:44:48


Am 27.03.2017 um 12:39 schrieb Oliver Kowalke via Boost:
> 2017-03-27 11:03 GMT+02:00 Deniz Bahadir via Boost <boost_at_[hidden]>:
>
>> PS: The following is the error output when compiling with GCC 4.8:
>>
>>
>> common.mkdir /home/jenkins/workspace/TEST_Boost_Build/gcc48/build/boost/b
>> oost/bin.v2/libs/fiber
>> common.mkdir /home/jenkins/workspace/TEST_Boost_Build/gcc48/build/boost/b
>> oost/bin.v2/libs/fiber/build
>> common.mkdir /home/jenkins/workspace/TEST_Boost_Build/gcc48/build/boost/b
>> oost/bin.v2/libs/fiber/build/gcc-4.8
>> common.mkdir /home/jenkins/workspace/TEST_Boost_Build/gcc48/build/boost/b
>> oost/bin.v2/libs/fiber/build/gcc-4.8/release
>> common.mkdir /home/jenkins/workspace/TEST_Boost_Build/gcc48/build/boost/b
>> oost/bin.v2/libs/fiber/build/gcc-4.8/release/link-static
>> common.mkdir /home/jenkins/workspace/TEST_Boost_Build/gcc48/build/boost/b
>> oost/bin.v2/libs/fiber/build/gcc-4.8/release/link-static/threading-multi
>> common.mkdir /home/jenkins/workspace/TEST_Boost_Build/gcc48/build/boost/b
>> oost/bin.v2/libs/fiber/build/gcc-4.8/release/link-static/thr
>> eading-multi/algo
>> gcc.compile.c++ /home/jenkins/workspace/TEST_B
>> oost_Build/gcc48/build/boost/boost/bin.v2/libs/fiber/build/g
>> cc-4.8/release/link-static/threading-multi/algo/algorithm.o
>> gcc.compile.c++ /home/jenkins/workspace/TEST_B
>> oost_Build/gcc48/build/boost/boost/bin.v2/libs/fiber/build/g
>> cc-4.8/release/link-static/threading-multi/algo/round_robin.o
>> gcc.compile.c++ /home/jenkins/workspace/TEST_B
>> oost_Build/gcc48/build/boost/boost/bin.v2/libs/fiber/build/g
>> cc-4.8/release/link-static/threading-multi/algo/shared_work.o
>> gcc.compile.c++ /home/jenkins/workspace/TEST_B
>> oost_Build/gcc48/build/boost/boost/bin.v2/libs/fiber/build/g
>> cc-4.8/release/link-static/threading-multi/algo/work_stealing.o
>> gcc.compile.c++ /home/jenkins/workspace/TEST_B
>> oost_Build/gcc48/build/boost/boost/bin.v2/libs/fiber/build/g
>> cc-4.8/release/link-static/threading-multi/barrier.o
>> gcc.compile.c++ /home/jenkins/workspace/TEST_B
>> oost_Build/gcc48/build/boost/boost/bin.v2/libs/fiber/build/g
>> cc-4.8/release/link-static/threading-multi/condition_variable.o
>> gcc.compile.c++ /home/jenkins/workspace/TEST_B
>> oost_Build/gcc48/build/boost/boost/bin.v2/libs/fiber/build/g
>> cc-4.8/release/link-static/threading-multi/context.o
>> libs/fiber/src/context.cpp: In constructor ‘boost::fibers::context::conte
>> xt(boost::fibers::dispatcher_context_t, const
>> boost::context::preallocated&, const default_stack&,
>> boost::fibers::scheduler*)’:
>> libs/fiber/src/context.cpp:230:14: error: call of overloaded
>> ‘callcc(const std::allocator_arg_t&, const boost::context::preallocated&,
>> const default_stack&, boost::fibers::context::contex
>> t(boost::fibers::dispatcher_context_t, const
>> boost::context::preallocated&, const default_stack&,
>> boost::fibers::scheduler*)::__lambda5)’ is ambiguous
>> });
>> ^
>> libs/fiber/src/context.cpp:230:14: note: candidates are:
>> In file included from ./boost/fiber/context.hpp:27:0,
>> from libs/fiber/src/context.cpp:7:
>> ./boost/context/continuation.hpp:468:1: note:
>> boost::context::continuation boost::context::callcc(std::allocator_arg_t,
>> StackAlloc, Fn&&, Arg ...) [with StackAlloc = boost::context::preallocated;
>> Fn = const boost::context::basic_fixedsize_stack<boost::context::stack_traits>&;
>> Arg = {boost::fibers::context::context(boost::fibers::dispatcher_context_t,
>> const boost::context::preallocated&, const default_stack&,
>> boost::fibers::scheduler*)::__lambda5}]
>> callcc( std::allocator_arg_t, StackAlloc salloc, Fn && fn, Arg ... arg) {
>> ^
>> ./boost/context/continuation.hpp:482:1: note:
>> boost::context::continuation boost::context::callcc(std::allocator_arg_t,
>> boost::context::preallocated, StackAlloc, Fn&&, Arg ...) [with StackAlloc =
>> boost::context::basic_fixedsize_stack<boost::context::stack_traits>; Fn =
>> boost::fibers::context::context(boost::fibers::dispatcher_context_t,
>> const boost::context::preallocated&, const default_stack&,
>> boost::fibers::scheduler*)::__lambda5; Arg = {}]
>> callcc( std::allocator_arg_t, preallocated palloc, StackAlloc salloc, Fn
>> && fn, Arg ... arg) {
>> ^
>> ./boost/context/continuation.hpp:513:1: note:
>> boost::context::continuation boost::context::callcc(std::allocator_arg_t,
>> boost::context::preallocated, StackAlloc, Fn&&) [with StackAlloc =
>> boost::context::basic_fixedsize_stack<boost::context::stack_traits>; Fn =
>> boost::fibers::context::context(boost::fibers::dispatcher_context_t,
>> const boost::context::preallocated&, const default_stack&,
>> boost::fibers::scheduler*)::__lambda5]
>> callcc( std::allocator_arg_t, preallocated palloc, StackAlloc salloc, Fn
>> && fn) {
>> ^
>> ./boost/context/continuation.hpp:456:1: note:
>> boost::context::continuation boost::context::callcc(Fn&&, Arg ...) [with Fn
>> = const std::allocator_arg_t&; Arg = {boost::context::preallocated,
>> boost::context::basic_fixedsize_stack<boost::context::stack_traits>,
>> boost::fibers::context::context(boost::fibers::dispatcher_context_t,
>> const boost::context::preallocated&, const default_stack&,
>> boost::fibers::scheduler*)::__lambda5}; <template-parameter-1-3> = void]
>> callcc( Fn && fn, Arg ... arg) {
>> ^
>>
>> "g++-4.8" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline
>> -Wall -pthread -m64 -m64 -fpic -std=c++11 -m64 -fpic
>> -DBOOST_ALL_NO_LIB=1 -DBOOST_DISABLE_ASSERTS -DBOOST_FIBERS_SOURCE
>> -DNDEBUG -I"." -c -o "/home/jenkins/workspace/TEST_
>> Boost_Build/gcc48/build/boost/boost/bin.v2/libs/fiber/build/
>> gcc-4.8/release/link-static/threading-multi/context.o"
>> "libs/fiber/src/context.cpp"
>>
>> ...failed gcc.compile.c++ /home/jenkins/workspace/TEST_B
>> oost_Build/gcc48/build/boost/boost/bin.v2/libs/fiber/build/g
>> cc-4.8/release/link-static/threading-multi/context.o...
>> ...failed updating 1 target...
>> ...updated 13574 targets...
>>
>
> did you run b2 with option --reconfigure? otherwise you use the cached
> values of the feature check

No I did not.

However, I used an entirely new / empty working-directory for each
compiler, so I did not see any reason in useing an option like
"--reconfigure".
(Earlier version-releases of Boost compiled fine without this option.)


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk