curtnichols
commented
4 years ago 64-bit builds appear compromised from recent tool chain updates, as well. For example, while building vc-using-framestream.sln:
[16:42:53][Step 3/26] x64\Release\UdpListener.obj
[16:42:54][Step 3/26] libprotobuf.lib(descriptor_database.cc.obj) : error LNK2001: unresolved external symbol __GSHandlerCheck_EH4 [C:\BuildAgent\work\89818f767e729ed7\sample-code\vc-using-framestream\vc-using-framestream\vc-using-framestream.vcxproj]
[16:42:54][Step 3/26] libprotobuf.lib(substitute.cc.obj) : error LNK2001: unresolved external symbol __GSHandlerCheck_EH4 [C:\BuildAgent\work\89818f767e729ed7\sample-code\vc-using-framestream\vc-using-framestream\vc-using-framestream.vcxproj]
[16:42:54][Step 3/26] libprotobuf.lib(io_win32.cc.obj) : error LNK2001: unresolved external symbol __GSHandlerCheck_EH4 [C:\BuildAgent\work\89818f767e729ed7\sample-code\vc-using-framestream\vc-using-framestream\vc-using-framestream.vcxproj]
[16:42:54][Step 3/26] libprotobuf.lib(map_field.cc.obj) : error LNK2001: unresolved external symbol __GSHandlerCheck_EH4 [C:\BuildAgent\work\89818f767e729ed7\sample-code\vc-using-framestream\vc-using-framestream\vc-using-framestream.vcxproj]
[16:42:54][Step 3/26] libprotobuf.lib(zero_copy_stream_impl.cc.obj) : error LNK2001: unresolved external symbol __GSHandlerCheck_EH4 [C:\BuildAgent\work\89818f767e729ed7\sample-code\vc-using-framestream\vc-using-framestream\vc-using-framestream.vcxproj]
[16:42:54][Step 3/26] libprotobuf.lib(extension_set_heavy.cc.obj) : error LNK2001: unresolved external symbol __GSHandlerCheck_EH4 [C:\BuildAgent\work\89818f767e729ed7\sample-code\vc-using-framestream\vc-using-framestream\vc-using-framestream.vcxproj]
[16:42:54][Step 3/26] libprotobuf.lib(descriptor.pb.cc.obj) : error LNK2001: unresolved external symbol __GSHandlerCheck_EH4 [C:\BuildAgent\work\89818f767e729ed7\sample-code\vc-using-framestream\vc-using-framestream\vc-using-framestream.vcxproj]
[16:42:54][Step 3/26] libprotobuf.lib(strtod.cc.obj) : error LNK2001: unresolved external symbol __GSHandlerCheck_EH4 [C:\BuildAgent\work\89818f767e729ed7\sample-code\vc-using-framestream\vc-using-framestream\vc-using-framestream.vcxproj]
[16:42:54][Step 3/26] libprotobuf.lib(tokenizer.cc.obj) : error LNK2001: unresolved external symbol __GSHandlerCheck_EH4 [C:\BuildAgent\work\89818f767e729ed7\sample-code\vc-using-framestream\vc-using-framestream\vc-using-framestream.vcxproj]This is acknowledged (?) by this post, which suggests the following flags for compile and link:
Yeah the cl.exe command line is as you described. For the linker it’s the same thing but under linker. To summarize:
VS2019->Properties->C/C++->Command Line add ‘-d2FH4-‘ VS2019->Properties->Linker->Command Line add ‘-d2:-FH4-‘
Afterthought: this is using the v141 (VS 2017) tools, so how would this have broken?
We're seeing some disturbing things in the various builds.
- The build server sees
[10:03:50][Step 3/26] C:\BuildAgent\work\89818f767e729ed7\tools\arislog\arislog\generated\availability.pb.cc(354,65): error C2220: the following warning is treated as an error [C:\BuildAgent\work\89818f767e729ed7\tools\arislog\arislog\arislog.vcxproj] [10:03:50][Step 3/26] C:\BuildAgent\work\89818f767e729ed7\tools\arislog\arislog\generated\availability.pb.cc(354,65): warning C4244: '=': conversion from 'google::protobuf::uint64' to 'google::protobuf::uint32', possible loss of data [C:\BuildAgent\work\89818f767e729ed7\tools\arislog\arislog\arislog.vcxproj] - Locally on the command line,
build-vc-programs.cmd(in "Developer Command Prompt for VS 2019") is seeingS:\git\aris-integration-sdk\common\code\ArisBasics.h(3): fatal error C1083: Cannot open include file: 'cstdint': No such file or directory [S:\git \aris-integration-sdk\sample-code\vc-using-framestream\vc-using-framestream\vc-using-framestream.vcxproj] - building directly in VS2019 16.3.7 succeeds.
All three builds above are Release|x86.
PR for automated build. Fixes #131.