https://svn.boost.org/trac10/ticket/10790 <p> There are some failures caused by Boost.Container using long long: <a href="http://www.boost.org/development/tests/develop/developer/output/FBSD-64%20jc-bell-boost-bin-v2-libs-regex-test-regex_regress_threaded-test-gcc-4-2-1-debug-threading-multi.html">http://www.boost.org/development/tests/develop/developer/output/FBSD-64%20jc-bell-boost-bin-v2-libs-regex-test-regex_regress_threaded-test-gcc-4-2-1-debug-threading-multi.html</a> </p> <p> The issue is that the compiler does support use of long long, but only under strict circumstances, the workaround is to use boost::long_long_type and boost::ulong_long_type defined in boost/config.hpp as these typedefs suppress the warnings which later lead to errors. Hope this makes sense! </p> <p> Thanks, John. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/10790 Trac 1.4.3 Michel Morin Thu, 13 Nov 2014 22:20:37 GMT https://svn.boost.org/trac10/ticket/10790#comment:1 https://svn.boost.org/trac10/ticket/10790#comment:1 <ul> <li><strong>owner</strong> set to <span class="trac-author">Ion Gaztañaga</span> </li> <li><strong>component</strong> <span class="trac-field-old">None</span> → <span class="trac-field-new">container</span> </li> </ul> Ticket Ion Gaztañaga Sat, 22 Nov 2014 12:26:44 GMT https://svn.boost.org/trac10/ticket/10790#comment:2 https://svn.boost.org/trac10/ticket/10790#comment:2 <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">fixed</span> </li> </ul> <p> Thanks, I didn't know about long_long_type. </p> <p> Commit in trunk SHA-1: 1d38ecfd1025ef1e4f1312a0300630580aeb5fd7 </p> <ul><li>Fixed <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/10790" title="#10790: Bugs: long long errors from container (closed: fixed)">#10790</a> (Trac): long long errors from container </li></ul> Ticket