aaron.ballman added a comment. In D130689#3706200 <https://reviews.llvm.org/D130689#3706200>, @thieta wrote:
> In D130689#3706199 <https://reviews.llvm.org/D130689#3706199>, @cor3ntin > wrote: > >> Trying to read the logs,, notably >> `C:\PROGRA~2\MIB055~1\2019\PROFES~1\VC\Tools\MSVC\1429~1.301\bin\Hostx64\x64\cl.exe >> `, it would seem that this particular bot is running a version much older >> than the current requirements (Visual Studio 2019 16.7) >> Either I'm reading that wrong or the CMake script does not check the msvc >> version? > > The compilers are definitely version checked here: > https://github.com/llvm/llvm-project/blob/main/llvm/cmake/modules/CheckCompilerVersion.cmake#L50 > > But reading the cmake log it seems like it's using a cache already and it's > hard to say if it's using the same version of MSVC. Something odd is going on here and we might want to consider a revert of this patch until we resolve it. When I do a git pull and cmake files change, Visual Studio's built-in CMake support automatically re-runs the configure step. This should be all that's necessary to switch the toolchain, but it isn't for some reason (today's build is also failing for me with C++17 related issues after I did another pulldown this morning). I deleted my cache explicitly and regenerated CMake from scratch and am still getting the same build errors. The failures I am getting are the same as what's shown by the sanitizer bot for Windows: https://lab.llvm.org/buildbot/#/builders/127/builds/33980/steps/4/logs/stdio (I'm using VS 2019 16.11.17 FWIW). I hope we can resolve this quickly as basically no MSVC builds are green right now in the build lab. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D130689/new/ https://reviews.llvm.org/D130689 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
