Explicitly converting optional to bool in those two cases (there are two test_all calls) fixes the issue, is it possible to get this patched before the 1.56.0 release?
This might be a c++11/14 specific bug (I compile with clang-trunk using c++1y). On Thu, Jul 31, 2014 at 10:52 AM, Gonzalo BG <gonzalob...@gmail.com> wrote: > I'm getting the following compilation error on the git master branch mpi > py_nonblocking.cpp > > libs/mpi/src/python/py_nonblocking.cpp:166:14: error: no viable conversion > from 'optional<(anonymous > namespace)::py_call_output_iterator<boost::mpi::status, > std::__1::__wrap_iter<boost::mpi::python::request_with_value *> > >' to > 'bool' > > return test_all(requests.begin(), requests.end(), > > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > 1 error generated. > > > when compiling with clang: > > "clang++" -x c++ -Wl,-flat_namespace -stdlib=libc++ -nostdinc++ -std=c++1y > -I/Users/gnzlbg/src/env/include/libcxx -O3 -O3 -finline-functions > -Wno-inline -Wall -DBOOST_ALL_NO_LIB=1 -DBOOST_MPI_DYN_LINK=1 > -DBOOST_MPI_PYTHON_DYN_LINK=1 -DBOOST_PYTHON_DYN_LINK=1 -DNDEBUG -I"." > -I"/Users/gnzlbg/src/env/include" > -I"/usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Versions/2.7/include/python2.7" > -c -o > "/Users/gnzlbg/src/env/boost_build/boost/bin.v2/libs/mpi/build/clang-darwin-4.2.1/release/threading-multi/python/py_nonblocking.o" > "libs/mpi/src/python/py_nonblocking.cpp" > > > Any ideas? >
_______________________________________________ Boost-mpi mailing list Boost-mpi@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-mpi
