https://svn.boost.org/trac10/ticket/13001 <p> In the regex documentation there are multiple files with &gt;150 character path lengths. </p> <p> This isn't a problem in many installs. However on windows where there is a maximum path length limit of 256 characters, this doesn't leave a lot of breathing room for environments that don't put their boost install very near to the root of their drive. </p> <p> All the files with issues in regex are in the docs in the background_information\performance directory, the longest being 184 chars at: .\libs\regex\doc\html\boost_regex\background_information\performance\section_Testing_simple_leftmost_longest_matches_platform_Windows_x64_compiler_Microsoft_Visual_C_version_14_0_.html </p> <p> All these long (&gt;150 char) paths could be fixed by: 1) Rename the "background_information" directory to "background" 2) Rename the "performance" directory to "perf" 3) Remove the "section_Testing_" prefix to all the files in the perf directory. </p> <p> Regex isn't the library with the longest (limiting) path length in boost, but if Geometry fixes its github issue <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/396" title="#396: Support Requests: Download boost_1_32_0.tar.bz2 (closed: Invalid)">#396</a>, then regex would be the long-pole. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/13001 Trac 1.4.3 lists@… Mon, 01 May 2017 18:14:14 GMT https://svn.boost.org/trac10/ticket/13001#comment:2 https://svn.boost.org/trac10/ticket/13001#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> Fixed in develop. </p> Ticket