-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
unable to build v6-26-00 with clang 13.0.1 #10046
Comments
Compiling with Clang 13 on CentOS 8 works fine. If you write "gcc8.4 and gcc11.2 toolchains for clang", does this include Yes, build errors would certainly help to determine which parts cause problems. |
see attached log. this is after running ninja as far as it will go, then re-running it to just capture the errors. this is from building with clang 13.0.1 that was built with the gcc 8.4 toolchain. It was built with |
here is the cmake configuration log. system was setup with
CC and CXX env vars are set to the clang_wrapper that does |
What is happening here is that your build pulls in header files from Clang 13.0.1, instead of using those bundled with ROOT:
In root/interpreter/llvm/src/include/llvm/ADT/StringRef.h Lines 246 to 248 in c4175cb
explicit yet and the code works.
Do your compiler wrappers maybe also add arguments or set environment variables that change the include path? |
this is the compiler wrapper:
should I set CXX to just |
You could try that, but I'm not sure this will change a lot. It could also be that your |
clang++ -v output is:
|
Ok, as expected |
indeed, the modulefile does:
I'll try again with it unset. |
removing the CPATH env var did the trick. thanks! |
Describe the bug
building root v6-26-00 with clang 13.0.1 fails with many errors. I have tried with both gcc8.4 and gcc11.2 toolchains for clang. This is on a centos7 system. The cmake (3.22.2) configuration step was:
Is this expected behavior? If so, what version of clang is supported for building root?
If desired, I will attach the build errors.
The text was updated successfully, but these errors were encountered: