On 8/7/2015 9:26 PM, Tom Kent wrote:
On Fri, Aug 7, 2015 at 5:21 PM, Andrey Semashev
wrote: On 07.08.2015 21:21, John Maddock wrote:
On 07/08/2015 17:24, Andrey Semashev wrote:
On 07.08.2015 19:09, John Maddock wrote:
What are the steps to reproduce this? 64-bit msvc-14 builds seem to be OK for me,
I described my steps at the beginning of the thread:
http://boost.2283326.n4.nabble.com/build-Problems-with-VC14-and-MSPDB140-DLL...
Did you remove the b2_msvc_14.0_vcvarsall* files in your temp directory?
Got it, can confirm it's an issue when building with 32-bit bjam (which uses the cross compiler), if you build with 64-bit bjam then it uses the native 64-bit compiler, and everything is OK.
I thought there's only one way to build bjam - by running tools/build/src/engine/build.bat. That's how I've always been building it anyway, and it always produced a 32-bit binary. How do you build a 64-bit bjam?
This problem will occur (with msvc-14.0) when using the bootstrap.bat file specified in the getting started directions.
Do you mean that it is a problem if bootstrap.bat picks msvc-14.0 as the "default" to use to bootstrap Boost build on Windows ? Actually I have never really understand how bootstrap.bat picks a default compiler in order to bootstrap Boost build. Do you know ?