Skip to content
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

vscode cpptools extensions not working #35088

Closed
juliendehos opened this issue Feb 18, 2018 · 4 comments
Closed

vscode cpptools extensions not working #35088

juliendehos opened this issue Feb 18, 2018 · 4 comments
Labels
2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md

Comments

@juliendehos
Copy link
Contributor

Issue description

The vscode cpptools extension is linked to /lib64/ld-linux-x86-64.so.2.

$ file ~/.vscode/extensions/ms-vscode.cpptools-0.15.0/bin/Microsoft.VSCode.CPP.Extension.linux 
/home/dehos/.vscode/extensions/ms-vscode.cpptools-0.15.0/bin/Microsoft.VSCode.CPP.Extension.linux: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=4ab2b1c13cd195245e581b35901048f97acd1dda, not stripped

So the extension fails when editing a C++ file with vscode:

[Error - 10:41:56 AM] Starting client failed Launching server using command /home/.../.vscode/extensions/ms-vscode.cpptools-0.15.0/bin/Microsoft.VSCode.CPP.Extension.linux failed.

This issue has been reported in the vscode repo (microsoft/vscode-cpptools#1345) but I think it is more a packaging problem.

@ftpman
Copy link

ftpman commented Apr 20, 2018

I had this problem on Raspbian Desktop and, I solved it by installing AMD64 version of libc (sudo apt-get install libc6-dev:amd64), because uname -r returned 4.9.0-4-amd64, but libc was i386, VS Code was i386 and cpptools extension is amd64.

Before I only had /lib/ld-linux.so.2 and now I have /lib64/ld-linux-x85-64.so.2

@jcrben
Copy link
Contributor

jcrben commented May 11, 2018

If you use vscode-with-extensions and https://github.com/NixOS/nixpkgs/blob/master/pkgs/misc/vscode-extensions/cpptools/default.nix then you can get it to work. Still haven't figured out if this means that I need to manage all my vscode extensions in nix tho.

I have this in my packageOverrides (pinnedPkgs is my thing):

      vscodeCpp = pinnedPkgs.vscode-with-extensions.override {
        vscodeExtensions = with vscode-extensions; [ ms-vscode.cpptools ];
      };

@danbst
Copy link
Contributor

danbst commented Jan 3, 2019

Alternative solution - https://discourse.nixos.org/t/vscode-extensions-setup/1801

This issue should be closed, as cpptools works in NixOS

@stale
Copy link

stale bot commented Jun 3, 2020

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

  1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
  2. Ask on the NixOS Discourse.
  3. Ask on the #nixos channel on irc.freenode.net.

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jun 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md
Projects
None yet
Development

No branches or pull requests

4 participants