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

Installation guide: On WSL, clear /mnt/c stuff from PATH #34889

Closed
mkoeppe opened this issue Jan 3, 2023 · 10 comments
Closed

Installation guide: On WSL, clear /mnt/c stuff from PATH #34889

mkoeppe opened this issue Jan 3, 2023 · 10 comments

Comments

@mkoeppe
Copy link
Contributor

mkoeppe commented Jan 3, 2023

As seen in https://groups.google.com/g/sage-devel/c/1nYw7-6QSkQ, our configure script fails to notice that some stuff in finds in PATH is not suitable:

configure:7510: found /mnt/c/Strawberry/perl/bin/pkg-config
configure:7522: result: /mnt/c/Strawberry/perl/bin/pkg-config
configure:7547: checking pkg-config is at least version 0.29
...
configure:33252: checking for xml2-config
configure:33275: found /mnt/c/Strawberry/c/bin/xml2-config
configure:33288: result: /mnt/c/Strawberry/c/bin/xml2-config
configure:33305: will use system package and not install SPKG libxml2
...
configure:42387: checking for PRIMESIEVE
configure:42394: $PKG_CONFIG --exists --print-errors "primesieve >= 8.0"
./configure: /mnt/c/Strawberry/perl/bin/pkg-config: perl: bad interpreter: No such file or directory

CC: @dimpase @tobiasdiez

Component: documentation

Author: Matthias Koeppe

Branch/Commit: 80a84d4

Reviewer: Dima Pasechnik

Issue created by migration from https://trac.sagemath.org/ticket/34889

@mkoeppe mkoeppe added this to the sage-9.8 milestone Jan 3, 2023
@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jan 4, 2023

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jan 4, 2023

Commit: 80a84d4

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jan 4, 2023

New commits:

80a84d4README.md: Add step to sanitize the environment

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jan 4, 2023

Author: Matthias Koeppe

@dimpase
Copy link
Member

dimpase commented Jan 5, 2023

Reviewer: Dima Pasechnik

@dimpase
Copy link
Member

dimpase commented Jan 5, 2023

comment:3

lgtm

@tobiasdiez
Copy link
Contributor

comment:4

Note that this workaround disables that one could run windows command line tools from within linux: https://learn.microsoft.com/en-us/windows/wsl/filesystems#run-windows-tools-from-linux

For example, without this workaround, one can run code from within the linux command line to open Windows' vscode in wsl mode in the correct folder.

@tobiasdiez
Copy link
Contributor

comment:5

There is also a windows config option that controls whether the windows path is appended: https://learn.microsoft.com/en-us/windows/wsl/wsl-config#interop-settings

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jan 5, 2023

comment:6

Maybe we can add something like "It's safe to keep /mnt/c/.../Programs/Microsoft VS Code/bin/ in the PATH"?

@vbraun
Copy link
Member

vbraun commented Jan 12, 2023

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

No branches or pull requests

4 participants