[llvm-dev] building LLVM 11 with OpenMP on Windows (original) (raw)

Geoff Levner via llvm-dev llvm-dev at lists.llvm.org
Tue Aug 3 13:29:04 PDT 2021

I tried setting LLVM_ENABLE_RUNTIMES=openmp instead of LLVM_ENABLE_PROJECTS=openmp. The error messages are different, but the errors result all the same. So for now I will have to continue commenting out KMP_DEBUG and the faulty trace commands that result when compiling in debug. Unless somebody else has a suggestion?

Ninja is much faster than nmake, though.

On Tue, Aug 3, 2021 at 5:52 PM Geoff Levner <glevner at gmail.com> wrote:

Thanks for that, Michael.

The workaround I have found for now is to use nmake and to avoid trace statements in OpenMP, which cause the compilation errors in the debug configuration, by commenting out the line in the OpenMP source code that #defines KMPDEBUG to 1. But that is not a nice workaround. I will try setting LLVMENABLERUNTIMES, as you suggest, to see if that works without hacking the source code. (Also nmake is very, very slow. Presumably ninja will be faster.)

On Tue, Aug 3, 2021 at 5:22 PM Michael Kruse <llvmdev at meinersbur.de> wrote: Am Di., 3. Aug. 2021 um 05:05 Uhr schrieb Geoff Levner via llvm-dev <llvm-dev at lists.llvm.org>: > Perhaps a solution would be to compile LLVM/Clang and OpenMP with Visual Studio but separately? Only I don't know how to do that...

You could use ninja on Windows (-cmake GNinja) which only has a single configuration per builddir. If compilation with cl.exe fail, try LLVMENABLERUMTIMES=openmp (instead of LLVMENABLEPROJECTS=openmp) which will build libomp using just-built clang. Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210803/55b353e0/attachment.html>

More information about the llvm-dev mailing list