2,652
edits
Installation: Difference between revisions
→WSL2
(→WSL2) |
(→WSL2) |
||
| Line 157: | Line 157: | ||
echo "[wsl2]" > .wslconfig | echo "[wsl2]" > .wslconfig | ||
echo "kernelCommandLine = vsyscall=emulate" >> .wslconfig | echo "kernelCommandLine = vsyscall=emulate" >> .wslconfig | ||
to make the shelx* programs happy (see https://github.com/microsoft/WSL/issues/4694 ). A few libraries also needed installation: | to make the shelx* programs happy (see https://github.com/microsoft/WSL/issues/4694 ), and "vsyscall=emulate" appear in /proc/cmdline. After creating the file, WSL must be restarted (or the machine booted). | ||
A few libraries also needed installation: | |||
sudo apt install tcsh libqt5opengl5 libqt5printsupport5 libqt5gui5 libxcb-render0 libxcb-shm0 libglu1-mesa | sudo apt install tcsh libqt5opengl5 libqt5printsupport5 libqt5gui5 libxcb-render0 libxcb-shm0 libglu1-mesa | ||
In addition, the Xming Xlaunch needed a box checked that prevents access control; and the Windows firewall needed a rule for port 6000 as shown in https://stackoverflow.com/questions/61110603/how-to-set-up-working-x11-forwarding-on-wsl2 . | In addition, the Xming Xlaunch needed a box checked that prevents access control; and the Windows firewall needed a rule for port 6000 as shown in https://stackoverflow.com/questions/61110603/how-to-set-up-working-x11-forwarding-on-wsl2 . | ||