https://svn.boost.org/trac10/ticket/5155 <p> I have been building boost successfully on Windows since 1.33. I usually extract boost do a directory such as: </p> <p> d:\boost_1_44_0 </p> <p> With 1.44, for the first time I noticed that some binaries were (silently) failing to appear in the build directory. Viewing the build directories, I suspected we were exceeding the windows path limit (256?). </p> <p> When I renamed to root folder to d:\b, the build suceeded. </p> <p> I'm afraid I didn't keep the build log, but kept the build command: </p> <p> bjam toolset=msvc-10.0 link=static runtime-link=static,shared variant="debug,release" threading="multi" define="_SECURE_SCL=0" debug-symbols="on" debug-store=database address-model=64 pch=off </p> <p> I suspect its the long list of options that have extended the path length. </p> <p> Platform: Windows 7 x64 Enterprise. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/5155 Trac 1.4.3 Steven Watanabe Fri, 11 Feb 2011 03:20:19 GMT