[build] recent issues w. VS 2017
Dear all, 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. Is this problem known? Thanks, Raffi build 01-May-2018 11:43:49 D:\bamboo_build_dir\SW-BCB161-VC2017WIN\library\libs\test\test>..\..\..\b2 --abbreviate-paths toolset=msvc-14.1 cxxflags="/std:c++latest" build 01-May-2018 11:43:50 Performing configuration checks build 01-May-2018 11:43:50 build 01-May-2018 11:43:50 - default address-model : 32-bit (cached) build 01-May-2018 11:43:50 - default architecture : x86 (cached) build 01-May-2018 11:43:50 - symlinks supported : no (cached) build 01-May-2018 11:43:50 - junctions supported : yes (cached) build 01-May-2018 11:43:50 - hardlinks supported : yes (cached) build 01-May-2018 11:43:51 - BOOST_COMP_GNUC >= 4.3.0 : no build 01-May-2018 11:43:54 - Boost.Config Feature Check: cxx11_auto_declarations : no build 01-May-2018 11:43:54 - Boost.Config Feature Check: cxx11_function_template_default_args : no build 01-May-2018 11:43:54 - Boost.Config Feature Check: cxx11_lambdas : no build 01-May-2018 11:43:55 - Boost.Config Feature Check: cxx11_hdr_initializer_list : no build 01-May-2018 11:43:55 - Boost.Config Feature Check: cxx11_template_aliases : no build 01-May-2018 11:43:55 - Boost.Config Feature Check: cxx11_decltype : no build 01-May-2018 11:43:55 - Boost.Config Feature Check: cxx11_hdr_random : no build 01-May-2018 11:43:55 - Boost.Config Feature Check: cxx11_hdr_tuple : no build 01-May-2018 11:43:55 - Boost.Config Feature Check: cxx11_variadic_macros : no build 01-May-2018 11:43:55 - Boost.Config Feature Check: cxx11_trailing_result_types : no build 01-May-2018 11:43:56 - Boost.Config Feature Check: cxx11_nullptr : no build 01-May-2018 11:43:56 - Boost.Config Feature Check: cxx11_unified_initialization_syntax : no build 01-May-2018 11:43:56 - Boost.Config Feature Check: cxx11_variadic_templates : no build 01-May-2018 11:43:57 - Boost.Config Feature Check: cxx11_decltype : no build 01-May-2018 11:43:57 - Boost.Config Feature Check: cxx11_hdr_random : no build 01-May-2018 11:43:57 - Boost.Config Feature Check: cxx11_hdr_tuple : no build 01-May-2018 11:43:57 - Boost.Config Feature Check: cxx11_hdr_initializer_list : no build 01-May-2018 11:43:57 - Boost.Config Feature Check: cxx11_variadic_macros : no build 01-May-2018 11:43:57 - Boost.Config Feature Check: cxx11_trailing_result_types : no build 01-May-2018 11:43:57 - Boost.Config Feature Check: cxx11_template_aliases : no build 01-May-2018 11:43:57 ...patience... build 01-May-2018 11:43:57 ...found 3946 targets... build 01-May-2018 11:43:57 ...updating 553 targets... build 01-May-2018 11:43:58 compile-c-c++ ..\..\..\bin.v2\libs\test\test\string_cast-test.test\msvc-14.1\dbg\thrd-mlt\utils-ts\string_cast-test.obj build 01-May-2018 11:43:58 string_cast-test.cpp build 01-May-2018 11:43:58 D:\bamboo_build_dir\SW-BCB161-VC2017WIN\library\boost/config/detail/select_stdlib_config.hpp(18): fatal error C1083: Cannot open include file: 'cstddef': No such file or directory 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 @"..\..\..\bin.v2\libs\test\test\string_cast-test.test\msvc-14.1\dbg\thrd-mlt\utils-ts\string_cast-test.obj.rsp" build 01-May-2018 11:43:58 build 01-May-2018 11:43:58 ...failed compile-c-c++ ..\..\..\bin.v2\libs\test\test\string_cast-test.test\msvc-14.1\dbg\thrd-mlt\utils-ts\string_cast-test.obj... build 01-May-2018 11:43:58 compile-c-c++ ..\..\..\bin.v2\libs\test\build\msvc-14.1\dbg\lnk-sttc\thrd-mlt\compiler_log_formatter.obj
Raffi Enficiaud wrote:
D:\bamboo_build_dir\SW-BCB161-VC2017WIN\library\boost/config/detail/select_stdlib_config.hpp(18): fatal error C1083: Cannot open include file: 'cstddef': No such file or directory
This happens when you update Visual Studio but the .bat files that b2 creates remain unchanged. These were formerly being created in %TEMP%, but now they should be in bin.v2. If you retain this directory between runs, try deleting the .bat files.
AMDG 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.
<snip> 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 @"..\..\..\bin.v2\libs\test\test\string_cast-test.test\msvc-14.1\dbg\thrd-mlt\utils-ts\string_cast-test.obj.rsp" <snip>
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. In Christ, Steven Watanabe
Le 01/05/2018 à 23:23, Steven Watanabe via Boost a écrit :
AMDG
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.
<snip> 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 @"..\..\..\bin.v2\libs\test\test\string_cast-test.test\msvc-14.1\dbg\thrd-mlt\utils-ts\string_cast-test.obj.rsp" <snip>
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 Studio\2017\Community\Common7\Tools\VsDevCmd.bat" The msvc-setup.bat looks ok, as far as I understand it. However, the platform is set to x86 from the "b2 headers" part. I do b2 headers b2 toolset=msvc-14.1 (from libs/test/tests) It used to work so far. Thanks for the help, Raffi
AMDG 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.
<snip> 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 @"..\..\..\bin.v2\libs\test\test\string_cast-test.test\msvc-14.1\dbg\thrd-mlt\utils-ts\string_cast-test.obj.rsp"
<snip>
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 Studio\2017\Community\Common7\Tools\VsDevCmd.bat"
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.
In Christ, Steven Watanabe
Le 02/05/2018 à 14:55, Steven Watanabe via Boost a écrit :
AMDG
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.
<snip> 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 @"..\..\..\bin.v2\libs\test\test\string_cast-test.test\msvc-14.1\dbg\thrd-mlt\utils-ts\string_cast-test.obj.rsp"
<snip>
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 Studio\2017\Community\Common7\Tools\VsDevCmd.bat"
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.
Thanks for all your feedback, Somehow adding address-model=64 at the header and build steps fixed everything. I do not know what I was compiling so far then :) Best, Raffi
participants (3)
-
Peter Dimov -
Raffi Enficiaud -
Steven Watanabe