[Pw_forum] pwscf version 4.3 example 15 error
xu yuehua
njuxuyuehua at gmail.com
Sat Jun 18 11:29:38 CEST 2011
hi everyone:
i just update the pwscf version to 4.3. the install is finish, then i run
the example 14 to test the install is ok or not, but the error exits.
i run it ./run_exampel, not use mpirun....., but the error seems to be mpi.
i am wondering. i search the forum, someone has encountered the similaer
problem, but no answer here.
my install has problem? (there is only warning during install) i also paste
the make.sys here, someone would help me i will be aggreciated. thanks a lot
!!!
the error information :
/home/yxu/espresso-4.3/espresso-4.3/examples/example15 : starting
This example shows how to use pw.x and ph.x to calculate
the Raman tensor for AlAs.
executables directory: /home/yxu/espresso-4.3/bin
pseudo directory: /home/yxu/espresso-4.3/pseudo
temporary directory: /home/yxu/tmp
checking that needed directories and files exist... done
running pw.x as: /home/yxu/espresso-4.3/bin/pw.x
running ph.x as: /home/yxu/espresso-4.3/bin/ph.x
cleaning /home/yxu/tmp... done
running the scf calculation... done
running the response calculation...[unset]: aborting job:
application called MPI_Abort(MPI_COMM_WORLD, 0) - process 0
done
/home/yhxu/espresso-4.3/espresso-4.3/examples/example15: done
- - -- - -- ----- -- ----- ------
------------------------------------------------------------------------------------
the make.sys ?( intel compier 11.1-072, intel mpi, intel MKL)
# make.sys. Generated from make.sys.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 $<
# DFLAGS = precompilation options (possible arguments to -D and -U)
# used by the C compiler and preprocessor
# FDFLAGS = as DFLAGS, for the f90 compiler
# 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
DFLAGS = -D__INTEL -D__FFTW3 -D__MPI -D__PARA
FDFLAGS = $(DFLAGS)
# IFLAGS = how to locate directories where files to be included are
# In most cases, IFLAGS = -I../include
IFLAGS = -I../include
# MOD_FLAGS = flag used by f90 compiler to locate modules
# Each Makefile defines the list of needed modules in MODFLAGS
MOD_FLAG = -I
# 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 = mpiifort
#F90 = ifort
CC = icc
F77 = ifort
# 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) -nomodule -fpp $(FDFLAGS) $(IFLAGS) $(MODFLAGS)
FFLAGS = -O2 -assume byterecl -g -traceback -par-report0
-vec-report0
# compiler flags without optimization for fortran-77
# the latter is NEEDED to properly compile dlamch.f, used by lapack
FFLAGS_NOOPT = -O0 -assume byterecl -g -traceback
# Linker, linker-specific flags (if any)
# Typically LD coincides with F90 or MPIF90, LD_LIBS is empty
LD = mpiifort
LDFLAGS = -static-intel
LD_LIBS =
# External Libraries (if any) : blas, lapack, fft, MPI
# If you have nothing better, use the local copy :
# BLAS_LIBS = /your/path/to/espresso/BLAS/blas.a
# BLAS_LIBS_SWITCH = internal
BLAS_LIBS =-L/home/yxu/intel/Compiler/11.1/072/ifort/mkl/lib/em64t
-lmkl_intel_lp64 -lmkl_sequential -lmkl_core -i-static
BLAS_LIBS_SWITCH = external
# If you have nothing better, use the local copy :
# LAPACK_LIBS = /your/path/to/espresso/lapack-3.2/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 = -L/home/yxu/intel/Compiler/11.1/072/ifort/mkl/lib/em64t
-lmkl_intel_lp64 -lmkl_sequential -lmkl_core -i-static
LAPACK_LIBS_SWITCH = external
SCALAPACK_LIBS =
# nothing needed here if the the internal copy of FFTW is compiled
# (needs -D__FFTW in DFLAGS)
#FFT_LIBS = -lfftw3xf
# 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 =
# 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 = ../flib/ptools.a ../flib/flib.a ../clib/clib.a
../iotk/src/libiotk.a
LIBS = $(SCALAPACK_LIBS) $(LAPACK_LIBS) $(FFT_LIBS) $(BLAS_LIBS)
$(MPI_LIBS) $(MASS_LIBS) $(LD_LIBS)
# topdir for linking espresso libs with plugins
TOPDIR = /home/giannozz/CVS/espresso
--
Yuehua Xu
Group of Computational Condensed Matter Physics,
National Laboratory of Solid State Microstructures and Department of
Physics,
Nanjing University,
Nanjing 210093,
P. R. China
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quantum-espresso.org/pipermail/users/attachments/20110618/52137a5c/attachment.html>
More information about the users
mailing list