-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
build failure with clang 10 on Ubuntu 20.04 #2915
Comments
Yes, I believe this is will happen with any I fixed this for myself just by adding |
I can confirm that the problem goes away when using clang from the current HEAD. |
I've faced the same issue and fixed by switching llvm version |
You can use the "Automatic installation script" to easily upgrade the Clang and LLVM related tools on Ubuntu. |
I've face the same issue with clang-10 and Ubuntu 18.04. I tried to use @zrait 's method. The issue has been solved.
|
Could you explain it detailly and which files should modify! Thanks very much. |
Could you explain it detailly and which files should modify! Thanks very much. |
I still got this issue when to compile in ubuntu 20.04. |
Met the same issue with a similar setting. @zrait and @jnhu76's method worked, except it took me 10 mins to find the file (like @smehod) |
This fix worked. Is this considered a workaround or is there a reason this hasn't been pushed into the codebase? |
But when I used this fix, it caused more bugs. Do I just need to change the cmake when using this method? Or do I need to download Polly from LLVM? @dgtlrift |
list(APPEND clang_libs in my case i didn't include ${libclangbasic} since, it wasn't mentioned there and again running my system: $uname -r |
Doing
Leads to:
This is with
clang version 10.0.0-4ubuntu1
.This appears to be upstream clang issue https://bugs.llvm.org/show_bug.cgi?id=44870
A fix claims to have been merged upstream but apparently didn't make this clang release. I gather from other Google hits that there are workarounds to be done in the cmake files, but I don't know the details.
The text was updated successfully, but these errors were encountered: