-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
clang-tidy: /lib64/libm.so.6: version `GLIBC_2.27' not found #10019
Comments
Does clang-tidy support remote scenarios? |
Yes it works fine when clang-tidy can run on the remote machine (with a new enough glibc). This type of issue already appeared in the past on cpptools executable, see here: #8192 As a comparison, here is a working clang-tidy on a Debian Unstable remote, issues are detected and displayed: And here, using a Centos 7 remote, there is no issues detected and the error appear in the C/C++ output (requires "Information" log level): |
The workaround would be to set C_Cpp.codeAnalysis.clangTidy.path to a clang-tidy that works on your OS with a lower glibc requirement. |
FYI, this will be fixed in our pending 1.13.3 release next week (also with clang-tidy 15.0.3). |
The fix is available with 1.13.3 (pre-release) for Linux x64 or arm64 (or Alpine): https://github.com/microsoft/vscode-cpptools/releases/tag/v1.13.3 However, Linux arm 32-bit still builds with shared libraries because otherwise it was crashing. We could open another issue track that if someone is hitting an issue with that. |
Environment
Bug Summary and Steps to Reproduce
Bug Summary:
The cpptools extensions show errors about clang-tidy which can't be run on Red Hat 7 as it requires GLIBC_2.27 for the function
log2f
.This makes clang-tidy not usable.
The exact error is:
Steps to reproduce:
C_Cpp.codeAnalysis.clangTidy.enabled
Log (Remote Serer)
clang-tidy: /lib64/libm.so.6: version GLIBC_2.27 not found
Other Extensions
No response
Additional Information
Running objdump -T on clang-tidy shows which function is the issue:
The text was updated successfully, but these errors were encountered: