Update FAQ entry about outdated libclang

This commit is contained in:
micbou 2018-12-11 20:10:53 +01:00
parent 51b6335b24
commit ee6756bdf4
No known key found for this signature in database
GPG Key ID: C7E8FD1F3BDA1E05
2 changed files with 13 additions and 27 deletions

View File

@ -3029,21 +3029,13 @@ version of libpython on your machine (for instance,
`-DPYTHON_LIBRARY=/usr/lib/libpython2.7.so`). Naturally, this means you'll have `-DPYTHON_LIBRARY=/usr/lib/libpython2.7.so`). Naturally, this means you'll have
to go through the full installation guide by hand. to go through the full installation guide by hand.
### I get `Vim: Caught deadly signal SEGV` on Vim startup ### I see `undefined symbol: clang_getCompletionFixIt` in the server logs.
This can happen on some Linux distros. If you encounter this situation, run Vim
under `gdb`. You'll probably see something like this in the output when Vim
crashes:
```
undefined symbol: clang_CompileCommands_dispose
```
This means that Vim is trying to load a `libclang.so` that is too old. You need
at least a 3.9 libclang. Just go through the installation guide and make sure
you are using a correct `libclang.so`. We recommend downloading prebuilt
binaries from llvm.org.
This means that the server is trying to load a version of libclang that is too
old. You need at least libclang 7.0.0. We recommend running the `install.py`
script without `--system-libclang` or downloading the [latest prebuilt binaries
from llvm.org][clang-download] when going through the [full installation
guide](#full-installation-guide).
### I get `Fatal Python error: PyThreadState_Get: no current thread` on startup ### I get `Fatal Python error: PyThreadState_Get: no current thread` on startup

View File

@ -155,7 +155,7 @@ Contents ~
11. I have a Homebrew Python and/or MacVim; can't compile/SIGABRT when starting |youcompleteme-i-have-homebrew-python-and-or-macvim-cant-compile-sigabrt-when-starting| 11. I have a Homebrew Python and/or MacVim; can't compile/SIGABRT when starting |youcompleteme-i-have-homebrew-python-and-or-macvim-cant-compile-sigabrt-when-starting|
12. I get 'LONG_BIT definition appears wrong for platform' when compiling |youcompleteme-i-get-long_bit-definition-appears-wrong-for-platform-when-compiling| 12. I get 'LONG_BIT definition appears wrong for platform' when compiling |youcompleteme-i-get-long_bit-definition-appears-wrong-for-platform-when-compiling|
13. I get 'libpython2.7.a [...] relocation R_X86_64_32' when compiling |youcompleteme-i-get-libpython2.7.a-...-relocation-r_x86_64_32-when-compiling| 13. I get 'libpython2.7.a [...] relocation R_X86_64_32' when compiling |youcompleteme-i-get-libpython2.7.a-...-relocation-r_x86_64_32-when-compiling|
14. I get 'Vim: Caught deadly signal SEGV' on Vim startup |youcompleteme-i-get-vim-caught-deadly-signal-segv-on-vim-startup| 14. I see 'undefined symbol: clang_getCompletionFixIt' in the server logs. |youcompleteme-i-see-undefined-symbol-clang_getcompletionfixit-in-server-logs.|
15. I get 'Fatal Python error: PyThreadState_Get: no current thread' on startup |youcompleteme-i-get-fatal-python-error-pythreadstate_get-no-current-thread-on-startup| 15. I get 'Fatal Python error: PyThreadState_Get: no current thread' on startup |youcompleteme-i-get-fatal-python-error-pythreadstate_get-no-current-thread-on-startup|
16. 'install.py' says python must be compiled with '--enable-framework'. Wat? |youcompleteme-install.py-says-python-must-be-compiled-with-enable-framework-.-wat| 16. 'install.py' says python must be compiled with '--enable-framework'. Wat? |youcompleteme-install.py-says-python-must-be-compiled-with-enable-framework-.-wat|
17. YCM does not read identifiers from my tags files |youcompleteme-ycm-does-not-read-identifiers-from-my-tags-files| 17. YCM does not read identifiers from my tags files |youcompleteme-ycm-does-not-read-identifiers-from-my-tags-files|
@ -3257,19 +3257,13 @@ version of libpython on your machine (for instance,
to go through the full installation guide by hand. to go through the full installation guide by hand.
------------------------------------------------------------------------------- -------------------------------------------------------------------------------
*youcompleteme-i-get-vim-caught-deadly-signal-segv-on-vim-startup* *youcompleteme-i-see-undefined-symbol-clang_getcompletionfixit-in-server-logs.*
I get 'Vim: Caught deadly signal SEGV' on Vim startup ~ I see 'undefined symbol: clang_getCompletionFixIt' in the server logs. ~
This can happen on some Linux distros. If you encounter this situation, run Vim This means that the server is trying to load a version of libclang that is too
under 'gdb'. You'll probably see something like this in the output when Vim old. You need at least libclang 7.0.0. We recommend running the 'install.py'
crashes: script without '--system-libclang' or downloading the latest prebuilt binaries
> from llvm.org [40] when going through the full installation guide.
undefined symbol: clang_CompileCommands_dispose
<
This means that Vim is trying to load a 'libclang.so' that is too old. You need
at least a 3.9 libclang. Just go through the installation guide and make sure
you are using a correct 'libclang.so'. We recommend downloading prebuilt
binaries from llvm.org.
------------------------------------------------------------------------------- -------------------------------------------------------------------------------
*youcompleteme-i-get-fatal-python-error-pythreadstate_get-no-current-thread-on-startup* *youcompleteme-i-get-fatal-python-error-pythreadstate_get-no-current-thread-on-startup*