Keyword arguments invalid because explicit interface is lacking

[pascal_boulet1]

Dear all,

I have problems to compile vasp 6.5.0 and 6.5.1 with either GNU or intel compilers because of
the hdf5 routine vhdf5_base.F

Is it a problem of my makefile.include (see below)?

Here is the error message:
vhdf5_base.F(378): error #6632: Keyword arguments are invalid without an explicit interface. [USE_FILE_LOCKING]
call h5pset_file_locking_f(plist_id, use_file_locking=.false., &
-------------------------------------------^
vhdf5_base.F(379): error #6632: Keyword arguments are invalid without an explicit interface. [IGNORE_DISABLED_LOCKS]
ignore_disabled_locks=.true., hdferr=ierr); call vh5_error(ierr,"vhdf5_base.F",379)
----------^
vhdf5_base.F(379): error #6632: Keyword arguments are invalid without an explicit interface. [HDFERR]
ignore_disabled_locks=.true., hdferr=ierr); call vh5_error(ierr,"vhdf5_base.F",379)

The makefile.include is:

# Default precompiler options
CPP_OPTIONS = -DHOST=\"LinuxIFC\" \
-DMPI -DMPI_BLOCK=8000 -Duse_collective \
-DscaLAPACK \
-DCACHE_SIZE=4000 \
-Davoidalloc \
-Dvasp6 \
-Dtbdyn \
-Dfock_dblbuf \
-D_OPENMP

CPP = fpp -f_com=no -free -w0 $*$(FUFFIX) $*$(SUFFIX) $(CPP_OPTIONS)

FC = mpiifort -qopenmp
FCL = mpiifort

FREE = -free -names lowercase

FFLAGS = -assume byterecl -w

OFLAG = -O2
OFLAG_IN = $(OFLAG)
DEBUG = -O0

# For what used to be vasp.5.lib
CPP_LIB = $(CPP)
FC_LIB = $(FC)
CC_LIB = icc
CFLAGS_LIB = -O
FFLAGS_LIB = -O1
FREE_LIB = $(FREE)

OBJECTS_LIB = linpack_double.o

# For the parser library
CXX_PARS = icpc
LLIBS = -lstdc++

##
## Customize as of this point! Of course you may change the preceding
## part of this file as well if you like, but it should rarely be
## necessary ...
##

# When compiling on the target machine itself, change this to the
# relevant target when cross-compiling for another architecture
VASP_TARGET_CPU = -march=core-avx2
FFLAGS += $(VASP_TARGET_CPU)

# Intel MKL (FFTW, BLAS, LAPACK, and scaLAPACK)
# (Note: for Intel Parallel Studio's MKL use -mkl instead of -qmkl)
FCL += -mkl
MKLROOT = /trinity/shared/apps/custom/x86_64/intel-2018.3.222/compilers_and_libraries_2018.3.222/linux/mkl
LLIBS += -L$(MKLROOT)/lib/intel64 -lmkl_scalapack_lp64 -lmkl_blacs_intelmpi_lp64
INCS =-I$(MKLROOT)/include/fftw

# HDF5-support (optional but strongly recommended, and mandatory for some features)
CPP_OPTIONS += -DVASP_HDF5
HDF5_ROOT = /trinity/shared/apps/tr17.10/x86_64/hdf5-icc18-impi-1.10.1
LLIBS += -L$(HDF5_ROOT)/lib -lhdf5_fortran
INCS += -I$(HDF5_ROOT)/include

# For the VASP-2-Wannier90 interface (optional)
CPP_OPTIONS += -DVASP2WANNIER90
WANNIER90_ROOT = /scratch/pboulet/packages/wannier90-3.1.0
LLIBS += -L$(WANNIER90_ROOT)/lib/intelmpi -lwannier

I am loading the following modules:
intel-mpi/64/2018.3.222
intel-compiler/64/2018.3.222
intel-mkl/64/2018.3.222
hdf5/icc18/impi/1.10.1

Any hint to solve this problem would be welcome.

Thank you

Pascal

[marie-therese.huebsch]

Hello,

I have never seen the error, but let's try to figure it out. It may be that our interface uses part of hdf5 that is not present in your installation. (Namely h5pset_file_locking_f) Could it be that the version is rather old? I see 2018 for the other modules. Can you try a more recent version?

Cheers,
Marie-Therese

[pascal_boulet1]

Hello,

Thank you for your reply.

Well, as I am using a mesocentre, I am limited to the compilers installed there. For intel compilers the latest module is intel-suite/2020.4.0, so version 19.1.2.254.
But then, I cannot use Intel-MPI, I have to use openMPI. That's ok for me, but there are several flavors:
openmpi/icc20/psm2/4.0.5
openmpi/icc20-4.1.6

Another restriction: mkl was not compiled with this 19.1.2.254 version of intel but the older one (18)...

Hence, I think I should rather use gfortran + openblas + scalapack + openmpi/gcc132-5.0.2 or openmpi/gcc72/psm2/3.1.3. Among these two, which one should I use? What is psm2?

Thank you
Pascal

[martin.schlipf]

It looks like the issue is the hdf5 library. Can you try compiling the code without hdf5 support and try to determine which version of hdf5 you are using? If the hdf5 version is very old it is possible that it does not support all features needed by VASP.