Skip to content
Permalink
Browse files

Include link to supported compiler

  • Loading branch information...
alazzaro committed Apr 10, 2019
1 parent 1b5a0fd commit ceb9b1a644c2f6fefc79a4808f4cdca95c811da3
Showing with 2 additions and 3 deletions.
  1. +2 −3 INSTALL.md
@@ -31,8 +31,7 @@ The basic steps are:
```

- Once the script has completed successfully, follow the instructions given at the end of its output.
Note that the pre-built arch files provided by the toolchain are for the GNU compiler, users have to adapt them for other compilers.
It is possible to use the provided [arch files](./arch) as guidance.
Note that the pre-built arch files provided by the toolchain are for the GNU compiler, users have to adapt them for other compilers. It is possible to use the provided [arch files](./arch) as guidance.

Sub-points here discuss prerequisites needed to build CP2K. Copies of the recommended versions of 3rd party software can be downloaded from https://www.cp2k.org/static/downloads/.

@@ -44,7 +43,7 @@ GNU make should be on your system (gmake or make on linux) and used for the buil
Python 2.x is needed to run the dependency generator. On most system Python is already installed. For more information visit: https://www.python.org/

### 2c. Fortran and C Compiler (required, build system)
A Fortran 2008 compiler and matching C compiler should be installed on your system. We have good experience with gcc/gfortran (gcc >=4.6 works, later version recommended). Be aware that some compilers have bugs that might cause them to fail (internal compiler errors, segfaults) or, worse, yield a mis-compiled CP2K. Report bugs to compiler vendors; they (and we) have an interest in fixing them. Always run a `make -j test` (See point 5.) after compilation to identify these problems.
A Fortran 2008 compiler and matching C compiler should be installed on your system. We have good experience with gcc/gfortran (gcc >=4.6 works, later version recommended). Be aware that some compilers have bugs that might cause them to fail (internal compiler errors, segfaults) or, worse, yield a mis-compiled CP2K. Report bugs to compiler vendors; they (and we) have an interest in fixing them. A list of tested compiler can be found [here](https://www.cp2k.org/dev:compiler_support). Always run a `make -j test` (See point 5.) after compilation to identify these problems.

### 2d. BLAS and LAPACK (required, base functionality)
BLAS and LAPACK should be installed. Using vendor-provided libraries can make a very significant difference (up to 100%, e.g., ACML, MKL, ESSL), not all optimized libraries are bug free. Use the latest versions available, use the interfaces matching your compiler, and download all patches!

0 comments on commit ceb9b1a

Please sign in to comment.
You can’t perform that action at this time.