https://svn.boost.org/trac10/ticket/13641 <p> Platform: Windows </p> <p> How to reproduce: </p> <ol><li>Extract Boost sources to some directory, say D:\boost </li><li>Bootstrap Boost as usual </li><li>Build Boost like this: <code>b2 --build-dir=D:\boost-build stage</code> </li></ol><p> Build process will not produce configuration log in D:\boost-build\boost\bin.v2\config.log, but will spew all configuration messages and errors to console. </p> <p> What I've found: </p> <ul><li>in tools\build\src\build-system.jam, line 678: <code>$(first-project-root).build-dir</code> yields "/D:/boost-build/boost/bin.v2". With a slash at the beginning it's not a valid Windows path. </li><li>in tools\build\src\build-system.jam, line 679: <code>set-log-file</code> rule silently fails </li><li>in tools\build\src\build\configure.jam, line 280: <code>FILE_OPEN</code> is unable to create "/D:/boost-build/boost/bin.v2/config.log" </li></ul><p> I don't have enough Boost.Build knowledge to provide a reasonable patch, but the problem seems to stem from <code>build-dir</code> project attribute prepending a slash to its value on Windows. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/13641 Trac 1.4.3 alexsharoff@… Mon, 23 Jul 2018 12:22:16 GMT https://svn.boost.org/trac10/ticket/13641 https://svn.boost.org/trac10/ticket/13641 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">007-fix-build-dir-argument-on-windows.diff</span> </li> </ul> <p> A hacky patch that I made to fix the problem on my end </p> Ticket