Boost C++ Libraries: Ticket #13026: Boost is not correctly configured on modern Mac with Intel C++ Compiler https://svn.boost.org/trac10/ticket/13026 <p> Boost does not work properly on modern macOS, for example 10.11, with Intel C++ Compiler. </p> <p> When compiling with default language/standard/compatibility flags, <code>select_compiler_config.hpp</code> picks up <code>intel.hpp</code> which does not define <code>BOOST_NO_RTTI</code> and <code>BOOST_NO_RTTI</code> due to <code>__INTEL_RTTI__</code>. This is wrong, since Intel C++ 2016 builds upon LLVM/Clang which does not have RTTI. As a result, if your application uses RTTI-dependent operators (like <code>typeid()</code>), it breaks. </p> <p> When you compile with the following flags: </p> <p> <code>-no-use-intel-optimized-headers -no-intel-extensions -no-icc -no-gcc</code> </p> <p> ...then Boost picks up <code>clang.hpp</code>. But the Clang version handling in this header file is broken since Apple has different versioning scheme for Clang. </p> <p> However, if you use the flag <code>-clangxx-name=&lt;clang&gt;</code> with a custom Clang version, then the Clang versioning scheme is back to normal. </p> <p> When building with Intel C++ on macOS, both Clang and Intel compiler specific settings need to be considered. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/13026 Trac 1.4.3 John Maddock Tue, 31 Jul 2018 18:45:09 GMT status changed; resolution set https://svn.boost.org/trac10/ticket/13026#comment:1 https://svn.boost.org/trac10/ticket/13026#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">obsolete</span> </li> </ul> <p> Moved to <a class="ext-link" href="https://github.com/boostorg/config/issues/235"><span class="icon">​</span>https://github.com/boostorg/config/issues/235</a>. </p> <p> Please consider filing some PR's against current develop as your configuration isn't one we can easily test here. </p> Ticket