Changes

From XDSwiki
Jump to navigationJump to search
17 bytes removed ,  20:33, 21 April 2021
Line 158: Line 158:  
=== WSL2 ===
 
=== WSL2 ===
   −
CCP4 7.1 including coot-0.9.5 works on Ubuntu 20.04 LTS under WSL2.  
+
CCP4 7.1 including coot-0.9.5 works in a Ubuntu 20.04 LTS machine under WSL2.  
   −
After installation of WSL2 according to [https://docs.microsoft.com/de-de/windows/wsl/install-win10 https://docs.microsoft.com/windows/wsl/install-win10], I installed [https://mobaxterm.mobatek.net/ MobaXterm] as the Xserver. When the Windows firewall asked whether it should allow MobaXterm communciation, I answered "yes" for both private and public networks.
+
[https://docs.microsoft.com/windows/wsl/install-win10 After installation of WSL2], I installed [https://mobaxterm.mobatek.net/ MobaXterm] as the Xserver. When the Windows firewall asked whether it should allow MobaXterm communciation, I answered "yes" for both private and public networks.
   −
Before you start CCP4 installation,
+
If you want to install CCP4 as a regular user, you need (as this is Linux):
 
+
sudo mkdir /opt/xtal
sudo mkdir /opt/xtal
+
sudo chown MYWSLNAME /opt/xtal
 
  −
sudo chown MYWSLNAME /opt/xtal
      
A few libraries are needed before CCP4 installation (tcsh is needed by CCP4, the others are mostly graphics libraries):
 
A few libraries are needed before CCP4 installation (tcsh is needed by CCP4, the others are mostly graphics libraries):
 
  sudo apt install tcsh libqt5opengl5 libqt5printsupport5 libqt5gui5 libxcb-render0 libxcb-shm0 libglu1-mesa libgomp1
 
  sudo apt install tcsh libqt5opengl5 libqt5printsupport5 libqt5gui5 libxcb-render0 libxcb-shm0 libglu1-mesa libgomp1
Let the CCP4 installation "modify the environment" for you. My ~/.bashrc has the line (which the CCP4 installation created):
+
When installing CCP4, let it "modify the environment" for you. If you forgot this, insert a line into your ~/.bashrc :
 
  source /opt/xtal/ccp4-7.1/bin/ccp4.setup-sh  
 
  source /opt/xtal/ccp4-7.1/bin/ccp4.setup-sh  
I created a file in the Windows filesystem (replace MYUSERNAME with your Windows username):
+
afterwards. I created a file in the Windows filesystem (replace MYUSERNAME with your Windows username):
 
  cd /mnt/c/Users/MYUSERNAME/
 
  cd /mnt/c/Users/MYUSERNAME/
 
  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 ), and to make "vsyscall=emulate" appear in /proc/cmdline. After creating the file, WSL2 must be restarted with "wsl.exe --shutdown" (or the machine booted).
+
to make the shelx* programs work (see https://github.com/microsoft/WSL/issues/4694 ), and to make "vsyscall=emulate" appear in /proc/cmdline. After creating the file, WSL2 must be restarted with "wsl.exe --shutdown" (or the machine booted).
    
Performance of coot is good enough for occasional work. XDSGUI and multi-threaded XDS work as expected. For reading .h5 files, the NEGGIA plugin works correctly, but the DURIN plugin currently crashes (a [https://github.com/DiamondLightSource/durin/issues/22 bug] has been reported).
 
Performance of coot is good enough for occasional work. XDSGUI and multi-threaded XDS work as expected. For reading .h5 files, the NEGGIA plugin works correctly, but the DURIN plugin currently crashes (a [https://github.com/DiamondLightSource/durin/issues/22 bug] has been reported).
2,522

edits

Cookies help us deliver our services. By using our services, you agree to our use of cookies.

Navigation menu