We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It's kind of hard to see what version of wsl people are using. It seems like wsl2 works ok, but wsl1 won't run some of the 32bit dependencies.
there are a few options for how to tell which version it is, but I can't confirm that they will always work.
the environment variable WSL_INTEROP should only be set for wsl2 uname -r will show *-microsoft-standard* for wsl2 but wsl1 will have *-Microsoft *
WSL_INTEROP
uname -r
*-microsoft-standard*
*-Microsoft *
There may be a directory called /run/WSL in wsl2 but in wsl1 it might be /run/WSL1.
/run/WSL
/run/WSL1
AFAIK this is the best I can do, and i've only looked at it for ubuntu.
We should try to warn people using WSL1 this this is the reason they might get an issue with phobius/signalp3.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It's kind of hard to see what version of wsl people are using.
It seems like wsl2 works ok, but wsl1 won't run some of the 32bit dependencies.
there are a few options for how to tell which version it is, but I can't confirm that they will always work.
the environment variable
WSL_INTEROP
should only be set for wsl2uname -r
will show*-microsoft-standard*
for wsl2 but wsl1 will have*-Microsoft *
There may be a directory called
/run/WSL
in wsl2 but in wsl1 it might be/run/WSL1
.AFAIK this is the best I can do, and i've only looked at it for ubuntu.
We should try to warn people using WSL1 this this is the reason they might get an issue with phobius/signalp3.
The text was updated successfully, but these errors were encountered: