|
Boost : |
Subject: Re: [boost] [move] Build failures in develop
From: Ion Gaztañaga (igaztanaga_at_[hidden])
Date: 2014-09-30 14:10:41
El 30/09/2014 9:33, Andrey Semashev escribió:
> Hi,
>
> I'm seeing lots of build errors that originate from Boost.Move, such as:
>
> In file included from ../libs/log/src/text_file_backend.cpp:41:
> In file included from ../boost/filesystem/path.hpp:28:
> In file included from ../boost/iterator/iterator_facade.hpp:12:
> In file included from ../boost/iterator/interoperable.hpp:11:
> In file included from ../boost/mpl/or.hpp:23:
> ../boost/mpl/aux_/nested_type_wknd.hpp:27:10: error: no type named
> 'type' in 'boost::move_detail::is_rv<boost::rv<boost::log::v2_mt_posix::aux::light_function<void
> ()> > >'
> : T::type
move_detail::is_rv is an implementation detail, and it previously
inherited from integral_constant (inheriting with a "type" member) to
just holding static const bool = xxx to minimize dependencies.
I will add a workaround, but if you really need that trait, let's move
it to the top namespace so that everyone knows it's an interface trait.
Best,
Ion
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk