We have tested BerkeleyGW extensively with various configurations, and support the following compilers and libraries:
- Operating systems: Linux, AIX, MacOS
- Fortran compilers (required, and must support Fortran 2003):
- C compilers (required):
- C++ compilers (required):
- MPI implementation (optional): OpenMPI, MPICH1, MPICH2, MVAPICH2, Intel MPI
- OpenMP threading (optional)
- LAPACK/BLAS implementation (required): NetLib, ATLAS, Intel MKL, ACML, Cray LibSci
- ScaLAPACK/BLACS implementation (required if MPI is used): NetLib, Cray LibSci, Intel MKL, AMD
- FFTW (required): versions 3.3.x (preferred) or 2.x.
The instructions below represent a typical case for compiling BerkeleyGW:
Architecture-specific Makefile-include files appropriate for various supercomputers as well as for using standard Ubuntu or Macports packages are provided in the
config/directory. Copy the configuration file that most resembles your architecture and name it
cp config/stampede.tacc.utexas.edu_threaded_hdf5.mk arch.mk
arch.mkfile to fit your needs. Refer to the compilation flags documentation for details.
maketo see the available compilation targets. If the
arch.mkis properly configured, you only need to type:where
make all-flavors -j 16
16can be substituted by the number of concurrent build processes.
If there is any error in the make processes, it may be beneficial to first build the real version of the code. You can repeatedly type
make realand fix any issues in the
arch.mk. Once the code builds successfully, clean the code and make the complex version of the code:
make clean-flavored make cplx -j 16
Note that the complex version may always be used. Real may be used for systems that have both inversion (about the origin) and time-reversal symmetry, and will be faster and use less memory.
- Test your build. See testsuite/README for more info.