Re: [boost] Boost.TypeTraits build failures

Le 06/02/2016 15:26, Niall Douglas a écrit :

On 6 Feb 2016 at 13:02, Vicente J. Botet Escriba wrote:

...

...

...

...

I appreciate it isn't your fault, it's Boost.TypeTraits causing an internal compiler error. Interesting folk may view https://ci.nedprod.com/view/Boost%20Thread-Expected-Permit/job/Boost.T hread%20Build/ (look for the red dots!).

I don't reach to see where the error is reported :( Can you see https://ci.nedprod.com? yes. and I was able to see the previous link. The problem is that I don't know where the error is reported. Following the red dots didn't helped me.

E.g. this link https://ci.nedprod.com/job/Boost.AFIO%20Build/CPPSTD=c++11,CXX=clang++-3.3,L...

doesn't gives any information about where the error is. Boost.Thread on FreeBSD clang 3.3 is all good, that is why there is no error.

Try this instead:

https://ci.nedprod.com/view/Boost%20Thread-Expected-Permit/job/Boost.Thread%...

Error is:

compile-c-c++ bin.v2\libs\thread\build\msvc-12.0\release\link-static\threading-multi \win32\thread.obj thread.cpp .\boost/type_traits/detail/mp_defer.hpp(50) : fatal error C1001: An internal error has occurred in the compiler. (compiler file 'f:\dd\vctools\compiler\cxxfe\sl\p1\c\p1types.cpp', line 192) To work around this problem, try simplifying or changing the program near the locations listed above. Please choose the Technical Support command on the Visual C++ Help menu, or open the Technical Support help file for more information .\boost/type_traits/common_type.hpp(49) : see reference to class template instantiation 'boost::common_type' being compiled

The same cause is failing the Windows Phone builds - an internal compiler error. Have you reported the error to MS? Could you create a Trac ticket for type_traits? Do you have an idea on how to fix it?

Only VS2013 is affected. VS2015, VS2012 and VS2010 are okay.

...

Please, could you gibe me the exact pointer where the errors are reported. BTW, the Boost develop regression tests don't show any significant failure since the 15th December. They may not be testing VS2013 in the configuration I am.

Right. Vicente