diff options
| author | Alexandre Ganea <alexandre.ganea@ubisoft.com> | 2020-01-28 14:48:12 -0500 |
|---|---|---|
| committer | Alexandre Ganea <alexandre.ganea@ubisoft.com> | 2020-01-28 14:57:57 -0500 |
| commit | b8c39e94626597912783d2077244158a4d5f27b8 (patch) | |
| tree | 5a84fec533c4b978c6c36826b976a8c8b40a0388 /llvm/lib/Support/LockFileManager.cpp | |
| parent | 7a717d82ff718271a4b5fcfd50d03eb9177066db (diff) | |
| download | llvm-b8c39e94626597912783d2077244158a4d5f27b8.zip llvm-b8c39e94626597912783d2077244158a4d5f27b8.tar.gz llvm-b8c39e94626597912783d2077244158a4d5f27b8.tar.bz2 | |
Fix compiling with clang-cl inside a Visual Studio 2019 16.4 command prompt.
This was introduced by 0d17410e919124b3a9194b9bdbe2ce39dd779941 and was preventing from compiling with clang-cl on Windows.
The problem was that clang-cl detects the triple from the current env vars (was x86_64-pc-windows-msvc19.24.28315 for me, as I happen to always run inside a VS2019 cmd prompt).
Diffstat (limited to 'llvm/lib/Support/LockFileManager.cpp')
0 files changed, 0 insertions, 0 deletions