CASINO manual - Theory of Condensed Matter

if no C++ compiler is available)
- FFLAGS_opt : flags for the Fortran compiler with full optimization
- FFLAGS_debug : flags for the Fortran compiler with full debugging
- CFLAGS_opt : flags for the C compiler with full optimization
- CXXFLAGS_opt : flags for the C++ compiler with full optimization
* Optional variables controlling features:
- HAVE_BLAS : omit HAVE_BLAS/HAVE_LAPACK or set them to ’no’ if you
HAVE_LAPACK would like to use the BLAS/LAPACK libraries provided with
LDBLAS_yes the CASINO distribution. Otherwise, set the HAVE_
LDLAPACK_yes variables to ’yes’ and the LDBLAS_yes/LDLAPACK_yes
variables to the ’-l’ flags required to link the
optimized BLAS/LAPACK libraries in your system.
- SUPPORT_OPENMP : omit SUPPORT_OPENMP or set it to ’no’ if your compiler
FFLAGS_OPENMP_yes does not support OpenMP or you wish to disable the
ability to compile it, else set SUPPORT_OPENMP to ’yes’
and set FFLAGS_OPENMP_yes to the flags required by your
compiler to enable OpenMP extensions, e.g., ’-openmp’
- SUPPORT_SHM : omit SUPPORT_SHM or set it to ’yes’ if your machine
CFLAGS_SHM supports either SysV or POSIX SHM. Set CFLAGS_SHM to
the C compiler flags to compile SHM support - these are
expected to be either -DSHM_SYSV or -DSHM_POSIX, which
select which version of SHM to use.
* Optional variables controlling the compile/run environment:
- ENVIRONMENT_COMMAND: single-line command to run before compiling and
running. This is useful where environment variables
need to be set (e.g., ’export MPI=OpenMPI’) or in
clusters where the ’module’ environment
handling system is used (e.g., ’module load
default-infinipath’). Multiple commands separated
by semicolons can be given. The only variables
that may be referenced are pre-existing environment
variables, and should be referenced using the syntax
’${variable}’ rather than ’$variable’; e.g.:
export PATH=${PATH}:/path/to/f90
is valid, while
export PATH=$PATH:/path/to/f90
and
export PATH1=/path/to/f90 ;\
export PATH=${PATH}:${PATH1}
are not valid. (The reason for this restriction is
the peculiarities of how ’make’ and ’sh’ interact.)
* Variables controlling Fortran and MPI libraries:
- MPI_VERSION : major version of the MPI library. Allowed values are 1
and 2 (default).
- ISOVAR_VERSION : version of iso_varying_string[1-2].f90. Allowed values
are 1 (default) and 2. The option 2 should only be used with
compilers which refused to compile iso_varying_string1.f90
(such as the Hitachi ofort90 compiler).
- LIB_PATH : ’-L’ options to add library search paths, e.g.,
’-L/usr/opt/mpi/lib’ (add one ’-L’ option for each path to
be added)
- INCLUDE_DIR : ’-I’ options to add include search paths, e.g.,
’-I/usr/opt/mpi/include’ (add one ’-I’ option for each path
to be added)
- LDLIBS_all : ’-l’ options to link libraries, e.g., ’-lmpi’ (add one ’-l’
option for each library to be linked)
* Variables defining a different compilation parameters for the utilities.
This is useful when one needs to cross-compile the sources to run on the
compute nodes of a cluster, but still requires a native compiler to be
able to build the utilities. The main keyword is:
- UTILS_MODE : set to ’native’ if the utilities require a compiler
different from the one used for main binary, leave empty
228