-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Wont find libclang automatically on Debian Testing #770
Comments
This sound strange. Did you remove the |
I did experience this on 2 systems without touching the configuration, I tried removing If you look at the log, the plugin searches for 'libclang-15..so', 'libclang-15..so.1' and similar. Seems the bug is in the generated library names (additional |
Hmm, you're right. That's very strange. It seems that for some reason the version of clang is not parsed correctly. What I don't understand is why it is not trimmed to two digits in here: EasyClangComplete/plugin/utils/clang_utils.py Lines 207 to 209 in c2e8913
So what I'm wondering now is what is the output of this command on your system: clang -v |
aint that the first 3 characters (including
|
As far as I know the stopping index of a slice is non-inclusive. But you could have a look into the code and try to help me out by checking which version it reports 🤔 |
Yes, and that means 3 characters {0, 1, 2}. Inclusive would be 4.
Not sure what you mean with "it", the content of |
digged around a bit. I guess the code you linked expects single-digit versions like 3.8.2 trying to extract 3.8.
One one of my systems, even with the code above not working, the "second pass" does, and is quite likely the clang -print-file-name=libclang.so.1
/usr/lib/llvm-15/bin/../lib/libclang.so.1 (Need to have a look at the broken systems later) I believe |
Yep, you're totally right. I hope I will be able to fix this over the weekend. Thanks for reporting and digging! |
Turns out clang will modify the searchpath to include Messy stuff, not sure what's the best way to solve this. I think taking the # clang -print-search-dirs
programs: =/usr/bin:/usr/lib/llvm-15/bin:/usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../x86_64-linux-gnu/bin
libraries: =/usr/lib/llvm-15/lib/clang/15.0.6:/usr/bin/../lib/gcc/x86_64-linux-gnu/12:/usr/bin/../lib/gcc/x86_64-linux-gnu/12/../../../../lib64:/lib/x86_64-linux-gnu:/lib/../lib64:/usr/lib/x86_64-linux-gnu:/usr/lib/../lib64:/usr/lib/llvm-15/bin/../lib:/lib:/usr/lib |
I'm able to confirm this issue on Debian Stable (Bullseye) using clang-14. Even using |
System info:
14 Build 4143
15.0.6
What happens:
The plugin is unable to find the libclang library, unless I provide the full path with
The library is available under the following paths:
Output from
clang --version
PS. I commented out the line in the settings shipped with the plugin,
doesnt make a difference for me, but it seems odd to have this as default:
Log that illustrates the issue:
The text was updated successfully, but these errors were encountered: