-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenMP linking errors on Windows using Ninja and clang #1129
Comments
8eaa7dc removed any trace of https://ci.appveyor.com/project/KrisThielemans/stir/builds/45873849#L31028 shows that no openmp flag nor library is added for linking. Cutting some stuff it reads
other bits from the log
Relevant CMake lines Line 158 in f75bd04
STIR/src/buildblock/CMakeLists.txt Line 145 in f027d10
STIR/src/recon_buildblock/CMakeLists.txt Line 133 in f75bd04
|
Appveyor for VS 2015 is running with cmake version 3.16.2, that'll explain a lot as CLang support has improved in CMake. I guess best to try with VS 2019 or 2022 where it will use 3.24.2. |
This still occurs with cmake version 3.24.2 and Clang 14.0.6 (on AppVeyor with the VS 2022 VM, so therefore Ninja 1.11.1). Build is https://ci.appveyor.com/project/KrisThielemans/stir/builds/45938757. Log file copied here. |
#1127 attempts to use Ninja on Appveyor (among trying to use
sccache
). It fails due to (unrelated) linking errors with OpenMP. Apparently the linker doesn't get passed the correct flag. This is likely caused by switching to Ninja, which I had to do as the VS Generator ignores the*COMPILER_LAUNCHER
(I guess I could trynmake
). But this is using theclang
compiler as opposed tocl
. so lots of things change.errors like
and
I don't think this is our problem, but CMake's FindOpenMP.
Originally posted by @KrisThielemans in #1127 (comment)
The text was updated successfully, but these errors were encountered: