On 6/21/2011 5:28 PM, KTC wrote:

On 21/06/2011 20:47, Jürgen Hunold wrote:

...

...

bjam --without-python --stagedir=x86 --build-type=complete -j2 stage

Both result in: "...failed updating 2 targets..." See<http://pastebin.com/s7Cvw2Tm> for failure.

Boost.Exceptions is a library on Win32. It builds "libs/exception/src/clone_current_exception_msvc.cpp"

which states at the top:

#if defined(_MSC_VER)&& defined(_M_IX86)&& !defined(_M_X64)

so this is for x86 only. On x64, no code gets compiled.

The msvc linker then "helpfully" silently omits the creation of an empty dll and the corresponding copy step(s) fail(s).

The correct fix would be to build this file only on for the<address-model>32 case but I don't know if this can be specified with the current Boost.Build.

There's the problem that this is also occurring when building for x86 while on a x64 system.

Does "<address-model>32:<build>no" as a requirement work? -Matt