Open Chaz6 opened 2 years ago
I found this: https://github.com/clangd/clangd/issues/722#issuecomment-795295250. This doesn't seem like anything that can be fixed here - maybe there could be a check for which glibc version is installed to make sure it's >= 2.18
.
If clangd is already available on the system, the installer should use that instead of downloading a fresh copy that is broken on the system.
I'd recommend simply not managing clangd via nvim-lsp-installer instead. You :LspUninstall clangd
and then make sure you set up clangd directly via lspconfig somewhere in your config:
lspconfig.clangd.setup {}
Problem description
When installing support for clangd, instead of using the system clangd, a new clangd installation is downloaded which requires a newer libc than is available on the system, so attempting to use it will fail. I was able to workaround this by deleting the folder
~/.local/share/nvim/lsp_servers/clangd/clangd
then restarting neovim. Please note the contents of LspInfo are shown after implementing the workaround.Neovim version (>= 0.6)
NVIM v0.7.0-dev+1192-g8ed9c8448 Build type: RelWithDebInfo LuaJIT 2.1.0-beta3
Operating system/version
Centos 7.9.2009 (Core)
I've recently downloaded the latest plugin version of both nvim-lsp-installer and nvim-lspconfig
Affected language servers
clangd
Steps to reproduce
Actual behavior
[ERROR][2022-03-06 15:57:57] .../vim/lsp/rpc.lua:420 "rpc" "clangd" "stderr" "clangd: /lib64/libc.so.6: version
GLIBC_2.18' not found (required by clangd)\n"`Expected behavior
If clangd is already available on the system, the installer should use that instead of downloading a fresh copy that is broken on the system.
LspInfo
Healthcheck
Screenshots or recordings
No response