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

integrated-terminal (x86_64-unknown-linux-gnu) #62

Open
ArtHome12 opened this issue Nov 20, 2018 · 10 comments
Open

integrated-terminal (x86_64-unknown-linux-gnu) #62

ArtHome12 opened this issue Nov 20, 2018 · 10 comments

Comments

@ArtHome12
Copy link

ArtHome12 commented Nov 20, 2018

Came from microsoft/vscode#62532

VS Code under flatpack is not workable for complex projects, while with a separate installation everything is fine.

In the OS terminal:

art@artPC:/$ ls /usr/bin/../lib/gcc/
avr  i686-linux-gnu  x86_64-linux-gnu

In the VSCode integrated under flatpack:


sh-4.4$ ls /usr/bin/../lib/gcc/
x86_64-unknown-linux-gnu

There is only one object (really 3) and it has different name - x86_64-unknown-linux-gnu instead correct x86_64-linux-gnu. As result - cannot to build library.

@TingPing
Copy link
Member

It will never match the host as it isn't the host.

@ronesp86
Copy link

+1

@jeffshee
Copy link

+1
make under integrated terminal gives error, while under OS terminal it works fine. My error was something like below, which showing the integrated one couldn't find the file.

/usr/lib/gcc/x86_64-unknown-linux-gnu/8.2.0/../../../../x86_64-unknown-linux-gnu/bin/ld: cannot find -ll

@refi64
Copy link
Contributor

refi64 commented Feb 11, 2019

On a related note, should there be a warning on where to report issues when using the Flatpak? I imagine upstream VS Code might get a little tired of issues that don't exist on their end past a certain point...

@peteruithoven
Copy link

Isn't this a duplicate of #39 ?

@ArtHome12
Copy link
Author

I seem it's related, but not the same. In any case, VSCode have to not use flatpack until solving this global problem.

@ZeroAurora
Copy link

Maybe because Flatpak runs vscode in a container so that vscode isn't able to access commands in the host machine? I am new to Flatpak and I don't understand it very well.
Before someone fixes the bug, I have to use the binary file provided by Microsoft.
(And sorry for my bad English)

@ricvelozo
Copy link

Use flatpak-spawn --host bash in VS Code terminal, or edit the settings of shell, i.e:

"terminal.integrated.shell.linux": "flatpak-spawn",
"terminal.integrated.shellArgs.linux": ["--host", "bash"],

@Pheoxy
Copy link

Pheoxy commented Sep 10, 2019

Use flatpak-spawn --host bash in VS Code terminal, or edit the settings of shell, i.e:

"terminal.integrated.shell.linux": "flatpak-spawn",
"terminal.integrated.shellArgs.linux": ["--host", "bash"],

This works, however it prints:
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
On Ubuntu 19.04.

@ricvelozo
Copy link

You can ignore the messages or use faltpak-spawn for just the external tools, instead of full terminal. The $TERM can be passed by --env=TERM=xterm-256color (before --host).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants