https://svn.boost.org/trac10/ticket/12057 <p> Extracted from issue <a class="ext-link" href="https://svn.boost.org/trac/boost/ticket/11516"><span class="icon">​</span>https://svn.boost.org/trac/boost/ticket/11516</a>: </p> <p> Many Boost headers use double-quoted include directives with paths that are not relative to the current header file. For example, this is an excerpt from boost/aligned_storage.hpp: </p> <p> #include "boost/config.hpp" #include "boost/detail/workaround.hpp" </p> <p> This will cause the full search path to be searched for the given files, even the directories supposedly local to the application (set via -iquote option on GCC/Clang), which can make local files interfere with Boost, especially if there's some part in the local project that is also called "boost"... </p> <p> See a full list of offending directives via: </p> <p> find /usr/include/boost -type f -exec grep '#.*"boost/' {} + </p> <p> As can be seen in boost/any.hpp, this might even be intentional for boost/config.hpp, but this is surely not intended for any other file. Handling of boost/config.hpp is not uniform, however; see for example boost/limits.h, which includes config.hpp via angle-quotes. </p> <p> This bug report does not address double-quoted include directives with header-relative paths, as used copiously by Boost Spirit, for example. These work fine on GCC/Clang and do not interact with local code (but see <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/3762" title="#3762: Patches: Thread can't be compiled with winscw (Codewarrior by Nokia) (closed: fixed)">#3762</a>). </p> <p> I suggest to change all include directives to a uniform style in order to eliminate interference of local files. The easiest and least-invasive solution would be to change double quotes to angle brackets, something along the lines of </p> <p> find /usr/include/boost -type f -exec sed -i~ -e 's/\(#.* \)"\(boost\/.*\)"/\1&lt;\2&gt;/' {} + </p> <p> (warning: search-and-destroy capability; this also updates #defines that are used later in #include directives) </p> <p> After applying this command, my code still compiles and passes all unit tests, but strace confirms that project-local include directories are no longer searched, except for boost/mpl/aux_/preprocessed/gcc/*.hpp, which is due to some stringification macro magic in boost/mpl/aux_/include_preprocessed.hpp. That's probably obscure enough to not matter in practice. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/12057 Trac 1.4.3 Antony Polukhin Thu, 02 Jun 2016 19:17:41 GMT https://svn.boost.org/trac10/ticket/12057#comment:1 https://svn.boost.org/trac10/ticket/12057#comment:1 <ul> <li><strong>owner</strong> changed from <span class="trac-author">ebf</span> to <span class="trac-author">Antony Polukhin</span> </li> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">assigned</span> </li> <li><strong>milestone</strong> <span class="trac-field-old">To Be Determined</span> → <span class="trac-field-new">Boost 1.62.0</span> </li> </ul> <p> Fixed in <a class="ext-link" href="https://github.com/boostorg/variant/commit/f4b7d2e50c6433bc9e981ee8d44531a7ba928926"><span class="icon">​</span>f4b7d2e5 develop</a>, will merge to master as soon as all the regression tests will cycle. </p> Ticket Antony Polukhin Sat, 29 Oct 2016 18:10:39 GMT https://svn.boost.org/trac10/ticket/12057#comment:2 https://svn.boost.org/trac10/ticket/12057#comment:2 <ul> <li><strong>status</strong> <span class="trac-field-old">assigned</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> Ticket