https://svn.boost.org/trac10/ticket/2107 <p> A very obscure bug just cropped up in our code when we moved to Boost 1.35 from 1.34.1. We use VSPL++, which uses LAPACK, which is provided in our installation by Intel's Math Kernel Library (MKL). After including &lt;vsip/math.hpp&gt; which brings in the LAPACK and MKL stuff, we cannot compile code using Boost routines that uses stuff from &lt;boost/mpl&gt;. In particular, we get a compile failure in various files found in the &lt;boost/mpl/aux_/preprocessed&gt; directory that have templates with a parameter called P4. This is defined in an MKL header to have the value 2 on our machine, which makes the template useless. </p> <p> I doubt that I can get Intel to not pollute the token space with 'P4'. I will try and get the VSIPL++ coders to '#undef P4' in a key spot in their code, and might be able to convince them that it would be OK to do so. But I was wondering if general uglification is necessary in the Boost code to reduce this type of problem in the future. I'll understand if the answer is "No" and this is rejected. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/2107 Trac 1.4.3 anonymous Wed, 11 Mar 2009 20:31:43 GMT https://svn.boost.org/trac10/ticket/2107#comment:5 https://svn.boost.org/trac10/ticket/2107#comment:5 <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">invalid</span> </li> </ul> <p> Closed as it seems Intel has removed the P4 macro. </p> Ticket