24小时热门版块排行榜    

查看: 984  |  回复: 1

granular258

金虫 (小有名气)

[求助] qe在redhat系统上安装出错,机子是服务器

qe在redhat上安装,configure成功,make时出错,提示如下
在文件 fox_m_fsys_varstr.F90:138

  character, dimension(, pointer, intent(inout) :: vs
                                 1
错误: POINTER 属性与 INTENT 属性在 (1) 处冲突
在文件 fox_m_fsys_varstr.F90:136

subroutine move_varstr_vs(vstr,vs)
                                1
错误: 符号‘vs’(位于 (1))没有 IMPLICIT 类型
在文件 fox_m_fsys_varstr.F90:140

  if (associated(vs)) deallocate(vs)
                1
错误: 实参‘pointer’(属于内建函数‘associated’,位于 (1))必须是一个 POINTER
make[3]: *** [fox_m_fsys_varstr.o] 错误 1
make[3]: Leaving directory `/home/pjianwang/q-e-qe-6.4.1/FoX/fox/fsys'
make[2]: *** [fsys_lib] 错误 2
make[2]: Leaving directory `/home/pjianwang/q-e-qe-6.4.1/FoX/fox'
make[1]: Leaving directory `/home/pjianwang/q-e-qe-6.4.1/install'
( cd UtilXlib ; make TLDEPS= all || exit 1 )
make[1]: Entering directory `/home/pjianwang/q-e-qe-6.4.1/UtilXlib'
mpif90 -O3 -g -x f95-cpp-input -D__FFTW -D__MPI   -I/home/pjianwang/q-e-qe-6.4.1//include -I/home/pjianwang/q-e-qe-6.4.1//FoX/finclude -I/home/pjianwang/q-e-qe-6.4.1//S3DE/iotk/include/ -I. -c parallel_include.f90
mpif90 -O3 -g -x f95-cpp-input -D__FFTW -D__MPI   -I/home/pjianwang/q-e-qe-6.4.1//include -I/home/pjianwang/q-e-qe-6.4.1//FoX/finclude -I/home/pjianwang/q-e-qe-6.4.1//S3DE/iotk/include/ -I. -c util_param.f90
mpif90 -O3 -g -x f95-cpp-input -D__FFTW -D__MPI   -I/home/pjianwang/q-e-qe-6.4.1//include -I/home/pjianwang/q-e-qe-6.4.1//FoX/finclude -I/home/pjianwang/q-e-qe-6.4.1//S3DE/iotk/include/ -I. -c clocks_handler.f90
在文件 clocks_handler.f90:60

     FUNCTION f_wall ( ) BIND(C,name="cclock" RESULT(t)
                       1
错误: (1) 处的函数声明后有非预期的垃圾字符
在文件 clocks_handler.f90:61

       USE ISO_C_BINDING
                       1
错误: 非预期的 USE 语句出现在 (1) 处的 INTERFACE 块中
在文件 clocks_handler.f90:62

       REAL(kind=c_double) :: t
                1
错误: Parameter 'c_double' at (1) has not been declared or is a variable, which does not reduce to a constant expression
在文件 clocks_handler.f90:63

     END FUNCTION f_wall
       1
错误: 需要 END INTERFACE 语句,于 (1)
在文件 clocks_handler.f90:64

     FUNCTION f_tcpu ( ) BIND(C,name="scnds" RESULT(t)
                       1
错误: (1) 处的函数声明后有非预期的垃圾字符
在文件 clocks_handler.f90:65

       USE ISO_C_BINDING
                       1
错误: 非预期的 USE 语句出现在 (1) 处的 INTERFACE 块中
在文件 clocks_handler.f90:66

       REAL(kind=c_double) :: t
                1
错误: Parameter 'c_double' at (1) has not been declared or is a variable, which does not reduce to a constant expression
在文件 clocks_handler.f90:67

     END FUNCTION f_tcpu
       1
错误: 需要 END INTERFACE 语句,于 (1)
在文件 clocks_handler.f90:85

       clock_label, walltime, t0wall, nclock, mpi_per_thread
                                                           1
致命错误: 无法打开模块文件‘mytime.mod’读取,在 (1) 处:没有那个文件或目录
make[1]: *** [clocks_handler.o] 错误 1
make[1]: Leaving directory `/home/pjianwang/q-e-qe-6.4.1/UtilXlib'
make: *** [libutil] 错误 1
回复此楼
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖

granular258

金虫 (小有名气)

make.inc文件内容
# make.inc.  Generated from make.inc.in by configure.

# compilation rules

.SUFFIXES :
.SUFFIXES : .o .c .f .f90

# most fortran compilers can directly preprocess c-like directives: use
#         $(MPIF90) $(F90FLAGS) -c $<
# if explicit preprocessing by the C preprocessor is needed, use:
#         $(CPP) $(CPPFLAGS) $< -o $*.F90
#        $(MPIF90) $(F90FLAGS) -c $*.F90 -o $*.o
# remember the tabulator in the first column !!!

.f90.o:
        $(MPIF90) $(F90FLAGS) -c $<

# .f.o and .c.o: do not modify

.f.o:
        $(F77) $(FFLAGS) -c $<

.c.o:
        $(CC) $(CFLAGS)  -c $<



# Top QE directory, useful for locating libraries,  linking QE with plugins
# The following syntax should always point to TOPDIR:
TOPDIR = $(dir $(abspath $(filter %make.inc,$(MAKEFILE_LIST))))
# if it doesn't work, uncomment the following line (edit if needed):

# TOPDIR = /home/pjianwang/q-e-qe-6.4.1

# DFLAGS  = precompilation options (possible arguments to -D and -U)
#           used by the C compiler and preprocessor
# To use libxc (v>=3.0.1), add -D__LIBXC to DFLAGS
# See include/defs.h.README for a list of options and their meaning
# With the exception of IBM xlf, FDFLAGS = $(DFLAGS)
# For IBM xlf, FDFLAGS is the same as DFLAGS with separating commas

# MANUAL_DFLAGS  = additional precompilation option(s), if desired
#                  BEWARE: it does not work for IBM xlf! Manually edit FDFLAGS
MANUAL_DFLAGS  =
DFLAGS         =  -D__FFTW -D__MPI
FDFLAGS        = $(DFLAGS) $(MANUAL_DFLAGS)

# IFLAGS = how to locate directories with *.h or *.f90 file to be included
#          typically -I$(TOPDIR)/include -I/some/other/directory/
#          the latter contains .e.g. files needed by FFT libraries
# for libxc add -I/path/to/libxc/include/

IFLAGS         = -I$(TOPDIR)/include -I$(TOPDIR)/FoX/finclude -I$(TOPDIR)/S3DE/iotk/include/

# MOD_FLAG = flag used by f90 compiler to locate modules

MOD_FLAG      = -I

# BASEMOD_FLAGS points to directories containing basic modules,
# while BASEMODS points to the corresponding module libraries
# Each Makefile can add directories to MODFLAGS and libraries to QEMODS

BASEMOD_FLAGS= $(MOD_FLAG)$(TOPDIR)/iotk/src \
               $(MOD_FLAG)$(TOPDIR)/Modules \
               $(MOD_FLAG)$(TOPDIR)/FFTXlib \
               $(MOD_FLAG)$(TOPDIR)/LAXlib \
               $(MOD_FLAG)$(TOPDIR)/UtilXlib \
               $(MOD_FLAG)$(TOPDIR)/FoX/finclude

# Compilers: fortran-90, fortran-77, C
# If a parallel compilation is desired, MPIF90 should be a fortran-90
# compiler that produces executables for parallel execution using MPI
# (such as for instance mpif90, mpf90, mpxlf90,...);
# otherwise, an ordinary fortran-90 compiler (f90, g95, xlf90, ifort,...)
# If you have a parallel machine but no suitable candidate for MPIF90,
# try to specify the directory containing "mpif.h" in IFLAGS
# and to specify the location of MPI libraries in MPI_LIBS

MPIF90         = mpif90
F90           = gfortran
CC             = gcc
F77            = gfortran

# GPU architecture (Kepler: 35, Pascal: 60, Volta: 70 )
GPU_ARCH=

# CUDA runtime (Pascal: 8.0, Volta: 9.0)
CUDA_RUNTIME=

# CUDA F90 Flags
CUDA_F90FLAGS=

# C preprocessor and preprocessing flags - for explicit preprocessing,
# if needed (see the compilation rules above)
# preprocessing flags must include DFLAGS and IFLAGS

CPP            = cpp
CPPFLAGS       = -P -traditional $(DFLAGS) $(IFLAGS)

# compiler flags: C, F90, F77
# C flags must include DFLAGS and IFLAGS
# F90 flags must include MODFLAGS, IFLAGS, and FDFLAGS with appropriate syntax

CFLAGS         = -O3 $(DFLAGS) $(IFLAGS)
F90FLAGS       = $(FFLAGS) -x f95-cpp-input $(FDFLAGS) $(CUDA_F90FLAGS) $(IFLAGS) $(MODFLAGS)
FFLAGS         = -O3 -g

# compiler flags without optimization for fortran-77
# the latter is NEEDED to properly compile dlamch.f, used by lapack

FFLAGS_NOOPT   = -O0 -g

# compiler flag needed by some compilers when the main program is not fortran
# Currently used for Yambo

FFLAGS_NOMAIN   =

# Linker, linker-specific flags (if any)
# Typically LD coincides with F90 or MPIF90, LD_LIBS is empty
# for libxc, set LD_LIBS=-L/path/to/libxc/lib/ -lxcf90 -lxc

LD             = mpif90
LDFLAGS        = -g
LD_LIBS        =

# External Libraries (if any) : blas, lapack, fft, MPI

# If you have nothing better, use the local copy via "--with-netlib" :
# BLAS_LIBS = /your/path/to/espresso/LAPACK/blas.a
# BLAS_LIBS_SWITCH = internal

BLAS_LIBS      =
BLAS_LIBS_SWITCH = external

# If you have nothing better, use the local copy via "--with-netlib" :
# LAPACK_LIBS = /your/path/to/espresso/LAPACK/lapack.a
# LAPACK_LIBS_SWITCH = internal
# For IBM machines with essl (-D__ESSL): load essl BEFORE lapack !
# remember that LAPACK_LIBS precedes BLAS_LIBS in loading order

LAPACK_LIBS    = $(TOPDIR)/LAPACK/liblapack.a $(TOPDIR)/LAPACK/libblas.a
LAPACK_LIBS_SWITCH = internal

SCALAPACK_LIBS =

# nothing needed here if the the internal copy of FFTW is compiled
# (needs -D__FFTW in DFLAGS)

FFT_LIBS       =

# HDF5
HDF5_LIB =
FOX_LIB  = -L$(TOPDIR)/FoX/lib  -lFoX_dom -lFoX_sax -lFoX_wxml -lFoX_common\
            -lFoX_utils -lFoX_fsys
FOX_FLAGS =
# For parallel execution, the correct path to MPI libraries must
# be specified in MPI_LIBS (except for IBM if you use mpxlf)

MPI_LIBS       =

# IBM-specific: MASS libraries, if available and if -D__MASS is defined in FDFLAGS

MASS_LIBS      =

# CUDA libraries
CUDA_LIBS=
CUDA_EXTLIBS =

# ar command and flags - for most architectures: AR = ar, ARFLAGS = ruv

AR             = ar
ARFLAGS        = ruv

# ranlib command. If ranlib is not needed (it isn't in most cases) use
# RANLIB = echo

RANLIB         = ranlib

# all internal and external libraries - do not modify

FLIB_TARGETS   = all

LIBOBJS        = $(TOPDIR)/clib/clib.a  $(TOPDIR)/iotk/src/libiotk.a
LIBXC_LIBS     =
QELIBS         = $(CUDA_LIBS) $(SCALAPACK_LIBS) $(LAPACK_LIBS) $(FOX_LIB) $(FFT_LIBS) $(BLAS_LIBS) $(MPI_LIBS) $(MASS_LIBS) $(HDF5_LIB) $(LIBXC_LIBS) $(LD_LIBS)

# wget or curl - useful to download from network
WGET = wget -O

# Install directory - "make install" copies *.x executables there
PREFIX = /usr/local
2楼2019-12-03 13:13:57
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖
相关版块跳转 我要订阅楼主 granular258 的主题更新
信息提示
请填处理意见