Boost C++ Libraries: Ticket #8934: b2 : failed to write output file https://svn.boost.org/trac10/ticket/8934 <p> Hello, </p> <p> Executing b2.exe within cmd.exe or powershell : </p> <p> and </p> <p> Building boost_1_54_0 with : </p> <p> b2 --debug-building --prefix=%USERPROFILE%\pkg\indie\boost address-model=64 --exec-prefix=%USERPROFILE%\programs\boost --libdir=%USERPROFILE%\pkg\lib --includedir=%USERPROFILE%\pkg\include --build-type=complete --build-dir=..\tmp pch=off debug-symbols=on debug-store=database install 2&gt;&amp;1 &gt;&gt; ..\boostbuild.txt </p> <p> results in an error : </p> <p> failed to write output file '..\tmp\boost\bin.v2\libs\program_options\build\msvc-11.0\release\address-model-64\debug-store-database\debug-symbols-on\link-static\pch-off\runtime-link-static\threading-multi\libboost_program_options-vc110-mt-s-1_54.lib.rsp'! </p> <p> My initial thoughts path name is it approaching the MAX_PATH, so I tried redirecting echo to the name file within cmd.exe; it resulted in The system cannot find the path specified. </p> <p> In powershell, echo redirection was successful but the build still failed at the same point. </p> <p> The full path length is 246 : python -c "print(len(r'C:\Users\Arkhe_2\pkg\src\tmp\boost\bin.v2\libs\program_options\build\msvc-11.0\release\address-model-64\debug-store-database\debug-symbols-on\link-static\pch-off\runtime-link-static\threading-multi\libboost_program_options-vc110-mt-s-1_54.lib.rsp'))" </p> <p> File system is NTFS located on a usb interconnected hard drive. </p> <p> Thanks for the great work. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/8934 Trac 1.4.3 jeffrey.beu.uz8yz6yl@… Mon, 29 Jul 2013 07:19:02 GMT attachment set https://svn.boost.org/trac10/ticket/8934 https://svn.boost.org/trac10/ticket/8934 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">openfile.c</span> </li> </ul> <p> fopen substitute </p> Ticket jeffrey.beu.uz8yz6yl@… Mon, 29 Jul 2013 07:30:45 GMT <link>https://svn.boost.org/trac10/ticket/8934#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/8934#comment:1</guid> <description> <p> Substituted occurrences of fopen in bjam/b2 source file with openfile.c which simply converts the arguments to wchar_t; prefixes the path with the voodoo of \ \ ? \ which allows very long path names in windows; then calls the _wfopen. </p> <p> Boost is now building fine. </p> <p> openfile is not meant to be a patch, just a quick fix that demonstrates a primitive resolution. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>viboes</dc:creator> <pubDate>Sat, 03 Aug 2013 16:35:25 GMT</pubDate> <title>component changed; owner set https://svn.boost.org/trac10/ticket/8934#comment:2 https://svn.boost.org/trac10/ticket/8934#comment:2 <ul> <li><strong>owner</strong> set to <span class="trac-author">Vladimir Prus</span> </li> <li><strong>component</strong> <span class="trac-field-old">None</span> → <span class="trac-field-new">build</span> </li> </ul> Ticket Steven Watanabe Tue, 11 Mar 2014 21:01:01 GMT <link>https://svn.boost.org/trac10/ticket/8934#comment:3 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/8934#comment:3</guid> <description> <p> You can use --abbreviate-paths or --hash to limit the path lengths. While it would be better for b2 to handle these paths safely, it's better to avoid them, as other tools can also have problems with them. </p> </description> <category>Ticket</category> </item> <item> <author>jeffrey.beu.uz8yz6yl@…</author> <pubDate>Thu, 13 Mar 2014 00:50:17 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/8934#comment:4 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/8934#comment:4</guid> <description> <p> Replying to <a class="ticket" href="https://svn.boost.org/trac10/ticket/8934#comment:3" title="Comment 3">steven_watanabe</a>: </p> <blockquote class="citation"> <p> You can use --abbreviate-paths or --hash to limit the path lengths. While it would be better for b2 to handle these paths safely, it's better to avoid them, as other tools can also have problems with them. </p> </blockquote> <p> Thanks Steve! </p> </description> <category>Ticket</category> </item> </channel> </rss>