-
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
Clang 9.0.1 on OSX and CMake failure #531
Comments
Sorry, I don't know Conda and am not sure how you want me to debug this. Do you just want me to try and build locally with CMake 3.17 and Clang 9.0.1? |
Can you pick the compiler version that Conda uses? If you could just set it to an earlier version, this problem would go away, right? |
This is an existing problem that just happens to be thrown up on the conda tests. It doesn't have anything to do with conda really. Also, forcing older compilers with conda is going to get us into trouble at some point (you don't want to conda install STIR and get a lot of old compiler stuff...). Anyway, test is: modify STIR's top-level |
when I run
So it seems I'm using 11.0.3, not 9.0.1. |
From this link, perhaps the Conda build is running Sierra (10.12) or High Sierra (10.13)? Can you choose a newer OSX image? |
Also the link in your first post (http://cmake.3232098.n2.nabble.com/No-known-features-for-CXX-compiler-warning-with-custom-Clang-td7594752.html) says that he's using a |
Thanks Richard. I don't really want to get into conda stuff too much. I know conda installs its own compilers and is independent of brew, and even most system files these days. The way I understand the nabble post is that the CMP0025 policy is recommended, as otherwise a new CMake will/might fall back to outdated behaviour (as our minimum requirements are very old). So, I suggest we just try that, commit it, and hope it resolves the conda problem. If not, we'll wait a while until conda's CMake has caught up with their clang. So, if you don't mind creating a PR on top if |
Works fine for me and all tests pass. |
great. phew! Just waiting for Travis then, and then I'll tag 4.0.2. Then merge that onto release_4. I'll then create a new PR to merge release_4 onto master. There's likely some changes needed in the scatter code for the Time to merge Palak's PR onto release_4 then! |
Sure, let me know when you've created the PR and i'll check it. |
Unfortunately, conda's build still says the same, so c287e70 didn't help. Oh well. |
Also observed by @robbietuk with |
Had a working version of STIR. Installed ITK with brew, this updated a lot of dependancies (including python 3.7 -> 3.8) requiring a reinstall of STIR. |
sure, updating "system" files generally means wiping existing CMake configurations. You can try to get round this by deleting cached settings So, are you saying this worked then on a new install? |
It seems the issue was with the cached settings. Creating a fresh install allowed for generate to work.
|
Quite unlikely this is a STIR problem. Seems something wrong with your XCode. maybe need a reinstall after |
Agreed, I will clean up the caches and I am updating xcode. |
Similar issue reported here and is related to the Xcode toolchain being corrupted: Reinstalling Xcode and Comand Line Tools leads to the same error. Similar issues were found here but many of the solutions didnt work for me. PointCloudLibrary/pcl#2601 Uninstalling Xcode but keeping CLT allowed for compilation... e: For me the issue was fixed when ITK is also causing some issues but that is seperate. |
Others struggle with the above errors as well. Homebrew/homebrew-core#59146 (comment) thinks it might be a VTK-bug. |
as I have no clue how to address this, I'll postpone it for later |
Not sure if this is related but in order to get STIR 4.0.1 to build on Mac OSX 11.6 I had to explicitly set the C++ compiler version in the top-level CMakeLists.txt file as follows:
According to conan-io/conan-center-index#3977 the default mode of apple-clang 12 (and 10) is C++03. Features in STIR seem to require C++11 or later. |
I'm going to close this, as it seems very outdated. By the way, we do require c++-11 now. |
The conda build for OSX now fails with
I suspect that this is because 9.0.1 is brand-new, and the installed CMake 3.17.0 doesn't know it yet, although I'm not sure.
However, I found a similar post http://cmake.3232098.n2.nabble.com/No-known-features-for-CXX-compiler-warning-with-custom-Clang-td7594752.html which says we should set CMP0025.
But then I'm not sure what we need at
STIR/CMakeLists.txt
Lines 44 to 46 in a005fd7
The text was updated successfully, but these errors were encountered: