degski wrote:
I'm also just using (a.o.) the clang that ships with 2017. I don't get it...
I checked the master branch, works. Then checked a downloaded 1_64_0, fails: 1>------ Build started: Project: testbed2017, Configuration: Debug Win32 ------ 1>testbed2017.cpp 1>In file included from testbed2017.cpp:1: 1>In file included from D:/boost_1_64_0\boost/filesystem.hpp:16: 1>In file included from D:/boost_1_64_0\boost/filesystem/path.hpp:28: 1>In file included from D:/boost_1_64_0\boost/iterator/iterator_facade.hpp:12: 1>In file included from D:/boost_1_64_0\boost/iterator/interoperable.hpp:11: 1>In file included from D:/boost_1_64_0\boost/mpl/or.hpp:43: 1>In file included from D:/boost_1_64_0\boost/mpl/aux_/include_preprocessed.hpp:37: 1>D:/boost_1_64_0\boost/mpl/aux_/preprocessed/gcc/or.hpp(63,1): error : pasting formed 'BOOST_PP_TUPLE_ELEM_O_3(', an invalid preprocessing token [-Winvalid-token-paste] 1>BOOST_MPL_AUX_NA_SPEC2( 1>^ This is exactly how clang used to fail before the changes, if I recall. I'm now checking out the boost-1.64.0 tag to see how it would fare.