Subject: Re: [boost] [build] recent issues w. VS 2017
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2018-05-02 12:55:47
On 05/02/2018 05:53 AM, Raffi Enficiaud via Boost wrote:
> Le 01/05/2018 Ã 23:23, Steven Watanabe via Boost a Ã©critÂ :
>> On 05/01/2018 03:12 PM, Raffi Enficiaud via Boost wrote:
>>> I am experiencing an issue with VS 2017 (15.6.6) while compiling
>>> boost.test on my agent. Traces below.
>>> I do not recall having applied any change to this agent apart from
>>> installing C++/CLI support for CMake people.
>>> buildÂ Â Â 01-May-2018 11:43:58
>>> buildÂ Â Â 01-May-2018 11:43:58Â Â Â Â Â Â Â call
>>> "..\..\..\bin.v2\standalone\msvc\msvc-14.1\msvc-setup.bat"Â >nul
>>> buildÂ Â Â 01-May-2018 11:43:58Â Â Â Â cl /Zm800 -nologo
>> Check msvc-setup.bat and make sure that it looks sane.
>> If it's left over from a previous run, try deleting
>> it and letting it be recreated.
> Thanks Steven and Peter,
> However, this happens on clean builds as well.
> The only call that is done before the bootstrap.bat call is
> "call "C:\Program Files (x86)\Microsoft Visual
> The msvc-setup.bat looks ok, as far as I understand it. However, the
> platform is set to x86 from the "b2 headers" part.
That's expected. If you use address-model=64, it will
create another msvc-setup.bat.
a) Does it work if you tell Boost.Build to use the
original scripts from visual studio directly?
(using msvc : 14.1 : : <rewrite-setup-scripts>off ; )
b) Does the compiler work correctly if you run it manually?
> I do
> b2 headers
> b2 toolset=msvc-14.1 (from libs/test/tests)
> It used to work so far.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk