Replies: 1 comment 8 replies
-
|
As mentioned on Discord, we need clangd logs to investigate what is going wrong. Clangd writes its logs to stderr and clients should expose a way to access that. I'm not familiar with Emacs, but assuming you're using lsp-mode, some searching suggests (based on e.g. this FAQ entry) that the clangd logs are stored in a buffer called |
Beta Was this translation helpful? Give feedback.
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
[UPDATE]: Thanks for @HighCommander4
When I running, I got the message:
zsh: no such file or directory: /usr/lib/llvm/14/bin/g++, I notice this option exists but I didn't spec manually:
--driver-mode=g++So I guess this is triggered by my compile_command.json, so I add these
, I regenerate compile_command.json, and the errors are just gone!
[ORIGIN]
In my emacs, I use
lsp-emacs+clangd, there are so many clangd error outputs but it can compile success, there's also happened in other projects. And when I use clion with clangd these errors are just gone and the syntax check outputs are the same as compiler compilation output.These are my operations when I get starting with a project:
cmake -B build -DCMAKE_EXPORT_COMPILE_COMMAND=YES -DCMAKE_BUILD_TYPE=Debug && ln -s build/compile_command.json ..Are there any operations and configurations I missed?
Here are my clangd-related configurations, the error still produces whether these configurations exist or not.
Here's my collected info following the troubleshooting guide
Beta Was this translation helpful? Give feedback.
All reactions