Toolchains: Difference between revisions

From VASP Wiki
No edit summary
No edit summary
Line 54: Line 54:
** [https://www.mpich.org/ MPICH 3.2.1]
** [https://www.mpich.org/ MPICH 3.2.1]
** [https://developer.nvidia.com/cuda-downloads CUDA 10.0]
** [https://developer.nvidia.com/cuda-downloads CUDA 10.0]
== Selected Makefiles ==
*[[A Debian based installation of VASP]]
*[[A Ubuntu based installation of VASP]]
*[[A Fedora based installation of VASP]]
*[[A CentOS based installation of VASP]]
*[[Linking gfortran with Intel MKL]]


== Related Sections ==
== Related Sections ==

Revision as of 12:47, 6 April 2022

VASP depends on several software libraries that have to be installed on the system and compatible with each other. This can sometimes be challenging, so that we provide a list of four compatible toolchains that have been used successfully for building and validating VASP 6.1.0 on Ubuntu Server 18.04.

Apart from a C and FORTRAN compiler, the parallel versions "vasp_std, vasp_gam, vasp_ncl" depend on four libraries:

The CUDA port of VASP does not depend on ScaLAPACK, however, a compatible CUDA toolkit is required.

The following toolchains have been tested successfully on Ubuntu Server 18.04.

The CUDA ports "vasp_gpu, vasp_gpu_ncl" have been successfully build and validated with following toolchains:

Related Sections

Installing VASP.6.X.X, Precompiler flags, CUDA-C GPU port of VASP, Validation tests


Contents