-
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
Failed to query compiler (1.2.0) #6898
Comments
Hi @nonprenom . With #6314 , we now avoid invoking executables that do not appear to be valid compilers, based on whether we detect certain defines that are required by the C or C++ standard. It looks like the compiler you are using diverges from what we are expecting, so we can't confirm it's valid. Could you point me to how I can get this particular compiler installed, or provide the output of passing the following args to it? -x c -E -dM /dev/null |
Actually, I think I have a fix for this. I'll see if we can release a 1.2.1 with this fix. |
Hi @Colengms, thanks for your answer. with arm-oe-linux-gnueabi-gcc
|
Should be fixed with https://github.com/microsoft/vscode-cpptools/releases/tag/1.2.1 |
Type: LanguageService
C/C++
Describe the bug
With the new version 1.2.0, the extension fails to query the compiler for default standard version and then disable it.
VsCode then starts to shows many errors in the code whereas the previous version 1.1.3 everything was fine.
I started to see this in the insider also few weeks ago so I went back to the standard version.
The debug log on 1.2.0 says:
Failed to query compiler at path "/opt/toolchain/usr/bin/arm-oe-linux-gnueabi/arm-oe-linux-gnueabi-gcc" for default standard versions. Compiler querying is disabled for this compiler.
With the previous version 1.1.3 - There was no errors in the logs
Steps to reproduce
Expected behavior
1.2.0 behave like 1.1.3
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: