Re: [boost] Clang 4.0.0 MPL error in Boost next.hpp and prior.hpp

Subject: Re: [boost] Clang 4.0.0 MPL error in Boost next.hpp and prior.hpp
From: Peter Dimov (lists_at_[hidden])
Date: 2017-03-26 01:43:58

> So, Clang/C2 can't link for some reason.

It occurred to me that the PP tests don't need to link. So,

...failed updating 25 targets...
...skipped 26 targets...
...updated 118 targets...

...failed clang-linux.compile.c++.without-pth 
..\..\bin.v2\libs\preprocessor\test\array.test\clang-linux-14.1\debug\array.obj...
...failed clang-linux.compile.c++.without-pth 
..\..\bin.v2\libs\preprocessor\test\list.test\clang-linux-14.1\debug\list.obj...
...failed clang-linux.compile.c++.without-pth 
..\..\bin.v2\libs\preprocessor\test\arithmetic_nvm.test\clang-linux-14.1\debug\arithmetic_nvm.obj...
...failed clang-linux.compile.c++.without-pth 
..\..\bin.v2\libs\preprocessor\test\array_nvm.test\clang-linux-14.1\debug\array_nvm.obj...
...failed clang-linux.compile.c++.without-pth 
..\..\bin.v2\libs\preprocessor\test\comparison_nvm.test\clang-linux-14.1\debug\comparison_nvm.obj...
...failed clang-linux.compile.c++.without-pth 
..\..\bin.v2\libs\preprocessor\test\control_nvm.test\clang-linux-14.1\debug\control_nvm.obj...
...failed clang-linux.compile.c++.without-pth 
..\..\bin.v2\libs\preprocessor\test\iteration_nvm.test\clang-linux-14.1\debug\iteration_nvm.obj...
...failed clang-linux.compile.c++.without-pth 
..\..\bin.v2\libs\preprocessor\test\list_nvm.test\clang-linux-14.1\debug\list_nvm.obj...
...failed clang-linux.compile.c++.without-pth 
..\..\bin.v2\libs\preprocessor\test\repetition_nvm.test\clang-linux-14.1\debug\repetition_nvm.obj...
...failed clang-linux.compile.c++.without-pth 
..\..\bin.v2\libs\preprocessor\test\selection_nvm.test\clang-linux-14.1\debug\selection_nvm.obj...
...failed clang-linux.compile.c++.without-pth 
..\..\bin.v2\libs\preprocessor\test\seq_nvm.test\clang-linux-14.1\debug\seq_nvm.obj...
...failed clang-linux.compile.c++.without-pth 
..\..\bin.v2\libs\preprocessor\test\tuple_nvm.test\clang-linux-14.1\debug\tuple_nvm.obj...
...failed clang-linux.compile.c.without-pth 
..\..\bin.v2\libs\preprocessor\test\array_c.test\clang-linux-14.1\debug\array_c.obj...
...failed clang-linux.compile.c.without-pth 
..\..\bin.v2\libs\preprocessor\test\list_c.test\clang-linux-14.1\debug\list_c.obj...
...failed clang-linux.compile.c.without-pth 
..\..\bin.v2\libs\preprocessor\test\arithmetic_c_nvm.test\clang-linux-14.1\debug\arithmetic_c_nvm.obj...
...failed clang-linux.compile.c.without-pth 
..\..\bin.v2\libs\preprocessor\test\array_c_nvm.test\clang-linux-14.1\debug\array_c_nvm.obj...
...failed clang-linux.compile.c.without-pth 
..\..\bin.v2\libs\preprocessor\test\comparison_c_nvm.test\clang-linux-14.1\debug\comparison_c_nvm.obj...
...failed clang-linux.compile.c.without-pth 
..\..\bin.v2\libs\preprocessor\test\control_c_nvm.test\clang-linux-14.1\debug\control_c_nvm.obj...
...failed clang-linux.compile.c.without-pth 
..\..\bin.v2\libs\preprocessor\test\list_c_nvm.test\clang-linux-14.1\debug\list_c_nvm.obj...
...failed clang-linux.compile.c.without-pth 
..\..\bin.v2\libs\preprocessor\test\selection_c_nvm.test\clang-linux-14.1\debug\selection_c_nvm.obj...
...failed clang-linux.compile.c.without-pth 
..\..\bin.v2\libs\preprocessor\test\seq_c_nvm.test\clang-linux-14.1\debug\seq_c_nvm.obj...
...failed clang-linux.compile.c.without-pth 
..\..\bin.v2\libs\preprocessor\test\tuple_c_nvm.test\clang-linux-14.1\debug\tuple_c_nvm.obj...
...failed clang-linux.compile.c++.without-pth 
..\..\bin.v2\libs\preprocessor\test\isempty_nvm.test\clang-linux-14.1\debug\isempty_nvm.obj...
...failed clang-linux.compile.c.without-pth 
..\..\bin.v2\libs\preprocessor\test\isempty_c_nvm.test\clang-linux-14.1\debug\isempty_c_nvm.obj...
clang.exe: error: linker command failed with exit code 1 (use -v to see 
invocation)
...failed clang-linux.link 
..\..\bin.v2\libs\preprocessor\test\config_info.test\clang-linux-14.1\debug\config_info.exe...

All the _nvm failures are an invalid token paste, which shouldn't in 
principle happen in a strict configuration, and are probably not something 
users will encounter because they disable BOOST_PP_VARIADICS by hand.

Full failure log attached.