There's a problem with noncopyable and boost::unit_test::singleton in Intel 13 for Linux in C++11 compatibility mode that's rippling through many Boost libs. To list a few:
This is already being solved: https://github.com/boostorg/config/pull/34
Sort of... this fix depends on setting an undocumented and untested config macro that was added while I wasn't paying attention. It raises a whole host of questions frankly: 1) Why on earth is: BOOST_CONSTEXPR noncopyable() = default; Better than noncopyable() {} The latter with or without a BOOST_CONSTEXPR? 2) Are any of the new features of noncopyable tested - if there are testable new features that is? 3) Should the undocumented/tested macro BOOST_NO_CXX11_NON_PUBLIC_DEFAULTED_FUNCTIONS exist at all, or should we disable the feature altogether (ie set BOOST_NO_CXX11_DEFAULTED_FUNCTIONS) for these problem cases/compilers? Finally, I note that comments on Github are all very well, but many interested parties may miss the discussion altogether - we're all guilty of this I realise - but it's important not to forget the mailing list - so many thanks to Joaquin for raising this to wider awareness! Cheers, John.