Boost C++ Libraries: Ticket #636: strange compiling problem for transitive_closure https://svn.boost.org/trac10/ticket/636 <pre class="wiki">Dears, I've found a strange compilation problem. By adding the following line to the file boost_1_33_1/libs/graph/example/transitive_closure.cpp #include &lt;boost/graph/depth_first_search.hpp&gt; before the inclusion of transitive_closure.hpp, the compilation broke. Please check the attached example. Best Regards, Fabrizio Ferrandi </pre> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/636 Trac 1.4.3 nobody Tue, 16 May 2006 13:26:51 GMT <link>https://svn.boost.org/trac10/ticket/636#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/636#comment:1</guid> <description> <pre class="wiki">Logged In: NO Note that I've this problem compiling with gcc 4.1 on a Fedora Core 5. Best Regards, Fabrizio Ferrandi </pre> </description> <category>Ticket</category> </item> <item> <dc:creator>anonymous</dc:creator> <pubDate>Fri, 05 Oct 2007 22:45:31 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/636#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/636#comment:2</guid> <description> <p> The same compilation error can be reproduced by using both the -Wall and -Wextra flags in gcc </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Andrew Sutton</dc:creator> <pubDate>Tue, 30 Sep 2008 12:47:00 GMT</pubDate> <title>status, resolution changed; severity set https://svn.boost.org/trac10/ticket/636#comment:3 https://svn.boost.org/trac10/ticket/636#comment:3 <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-old">None</span> → <span class="trac-field-new">worksforme</span> </li> <li><strong>severity</strong> → <span class="trac-field-new">Problem</span> </li> </ul> <p> Tried to verify on Ubuntu+gcc-4.2.3 on trunk and again on CentOS+gcc-4.1.2 and cannot reproduce the error. Perhaps this was fixed and the ticket not closed. </p> Ticket