Hi Phillip, I've run into this myself outside of boost compilation. 

The issue stems from the default options for the new MS-compile not supporting synchronous writes to PDB files.
I believe this issue only arises during the compilation stage, in Visual studio I pass it the /FS option it desires.

I believe you might be able to use CXXFLAGS to pass the FS command to the compiler.


b2 -j2 release cxxflags=/FS

That said, I haven't tested this method myself (yet). (if this occurs during the linking stage you may need to pass linkflags=/FS also)

If I may ask, are you attempting to compile the static libraries? using multi-compilation to accelerate the process? If so you may wish to consider using --with-LIBNAME for just the libraries in question.
b2 --with-aiso --with-thread --with-filesystem
This will make the process much faster if you do not need the entire collection.



On 25 February 2015 at 21:11, Phillip Seaver <phil@apago.com> wrote:
I'm building several projects with VS2013, and the debug build ("b2
-j2") works fine, but when I do the release build ("b2 -j2 release"), I
get errors like this:  "fatal error C1041: cannot open program database
'x.pdb'; if multiple CL.EXE write to the same .PDB file, please use /FS"

Has anyone else run into this?

Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build