Dear Pwscf users,<br>I am using mpif90 and /mkl/<a href="http://10.0.3.020/lib/em64t">10.0.3.020/lib/em64t</a> and trying to compile espresso-4.1<br>During compilation, there comes LOOP WAS VECTORISED<br><br>I have gone through the previous pwscf post and use all the solution which the users said, but still the remark comes.<br>
<br>So is that some error in compilation?<br>If so how can i remove it.<br>Following is my make.sys file<br># make.sys. Generated from <a href="http://make.sys.in">make.sys.in</a> by configure.<br><br># compilation rules<br>
<br>.SUFFIXES :<br>.SUFFIXES : .o .c .f .f90<br><br># most fortran compilers can directly preprocess c-like directives: use<br># $(MPIF90) $(F90FLAGS) -c $<<br># if explicit preprocessing by the C preprocessor is needed, use:<br>
# $(CPP) $(CPPFLAGS) $< -o $*.F90<br># $(MPIF90) $(F90FLAGS) -c $*.F90 -o $*.o<br># remember the tabulator in the first column !!!<br><br>.f90.o:<br> $(MPIF90) $(F90FLAGS) -c $<<br><br># .f.o and .c.o: do not modify<br>
<br>.f.o:<br> $(F77) $(FFLAGS) -c $<<br><br>.c.o:<br> $(CC) $(CFLAGS) -c $<<br><br><br># DFLAGS = precompilation options (possible arguments to -D and -U)<br># used by the C compiler and preprocessor<br>
# FDFLAGS = as DFLAGS, for the f90 compiler<br># See include/defs.h.README for a list of options and their meaning<br># With the exception of IBM xlf, FDFLAGS = $(DFLAGS)<br># For IBM xlf, FDFLAGS is the same as DFLAGS with separating commas<br>
<br>DFLAGS = -D__INTEL -D__FFTW -D__MPI -D__PARA<br>FDFLAGS = $(DFLAGS)<br><br># IFLAGS = how to locate directories where files to be included are<br># In most cases, IFLAGS = -I../include<br><br>IFLAGS = -I../include<br>
<br># MODFLAGS = flag used by f90 compiler to locate modules<br># You need to search for modules in ./, in ../iotk/src, in ../Modules<br># Some applications also need modules in ../PW and ../PH<br><br>MODFLAGS = -I./ -I../Modules -I../iotk/src \<br>
-I../PW -I../PH -I../EE -I../GIPAW<br><br># Compilers: fortran-90, fortran-77, C<br># If a parallel compilation is desired, MPIF90 should be a fortran-90<br># compiler that produces executables for parallel execution using MPI<br>
# (such as for instance mpif90, mpf90, mpxlf90,...);<br># otherwise, an ordinary fortran-90 compiler (f90, g95, xlf90, ifort,...)<br># If you have a parallel machine but no suitable candidate for MPIF90,<br># try to specify the directory containing "mpif.h" in IFLAGS<br>
# and to specify the location of MPI libraries in MPI_LIBS<br><br>MPIF90 = mpif90<br>#F90 = ifort<br>CC = mpicc<br>F77 = mpif90<br><br># C preprocessor and preprocessing flags - for explicit preprocessing,<br>
# if needed (see the compilation rules above)<br># preprocessing flags must include DFLAGS and IFLAGS<br><br>CPP = cpp<br>CPPFLAGS = -P -traditional $(DFLAGS) $(IFLAGS)<br><br># compiler flags: C, F90, F77<br>
# C flags must include DFLAGS and IFLAGS<br># F90 flags must include MODFLAGS, IFLAGS, and FDFLAGS with appropriate syntax<br><br>CFLAGS = -O3 $(DFLAGS) $(IFLAGS)<br>F90FLAGS = $(FFLAGS) -nomodule -fpp $(FDFLAGS) $(IFLAGS) $(MODFLAGS)<br>
FFLAGS = -O2 -assume byterecl<br><br># compiler flags without optimization for fortran-77<br># the latter is NEEDED to properly compile dlamch.f, used by lapack<br><br>FFLAGS_NOOPT = -O0 -assume byterecl<br><br>
# Linker, linker-specific flags (if any)<br># Typically LD coincides with F90 or MPIF90, LD_LIBS is empty<br><br>LD = mpif90<br>LDFLAGS = -i-static -openmp<br>LD_LIBS =<br><br># External Libraries (if any) : blas, lapack, fft, MPI<br>
<br># If you have nothing better, use the local copy : ../flib/blas.a<br><br>BLAS_LIBS = -L/opt/intel/mkl/<a href="http://10.0.3.020/lib/em64t">10.0.3.020/lib/em64t</a> -lmkl_em64t<br><br># The following lapack libraries will be available in flib/ :<br>
# ../flib/lapack.a : contains all needed routines<br># ../flib/lapack_atlas.a: only routines not present in the Atlas library<br># For IBM machines with essl (-D__ESSL): load essl BEFORE lapack !<br># remember that LAPACK_LIBS precedes BLAS_LIBS in loading order<br>
<br>LAPACK_LIBS = -L/opt/intel/mkl/<a href="http://10.0.3.020/lib/em64t">10.0.3.020/lib/em64t</a> -lmkl_lapack -lmkl_ia32 -lguide -lpthread -lmkl_core -lmkl_em64t<br><br># nothing needed here if the the internal copy of FFTW is compiled<br>
# (needs -D__FFTW in DFLAGS)<br><br>FFT_LIBS =<br><br># For parallel execution, the correct path to MPI libraries must<br># be specified in MPI_LIBS (except for IBM if you use mpxlf)<br><br>MPI_LIBS =<br><br># IBM-specific: MASS libraries, if available and if -D__MASS is defined in FDFLAGS<br>
MASS_LIBS = <br><br># pgplot libraries (used by some post-processing tools)<br><br>PGPLOT_LIBS = <br><br># ar command and flags - for most architectures: AR = ar, ARFLAGS = ruv<br># ARFLAGS_DYNAMIC is used in iotk to produce a dynamical library,<br>
# for Mac OS-X with PowerPC and xlf compiler. In all other cases<br># ARFLAGS_DYNAMIC = $(ARFLAGS)<br><br>AR = ar<br>ARFLAGS = ruv<br>ARFLAGS_DYNAMIC= ruv<br><br># ranlib command. If ranlib is not needed (it isn't in most cases) use<br>
# RANLIB = echo<br><br>RANLIB = ranlib<br><br># all internal and external libraries - do not modify<br><br>LIBOBJS = ../flib/ptools.a ../flib/flib.a ../clib/clib.a ../iotk/src/libiotk.a ../Multigrid/mglib.a<br>
LIBS = $(LAPACK_LIBS) $(BLAS_LIBS) $(FFT_LIBS) $(MPI_LIBS) $(MASS_LIBS) $(PGPLOT_LIBS) $(LD_LIBS)<br><br>-- <br>Dr. Bipul Rakshit<br>Research Associate,<br>S N Bose Centre for Basic Sciences,<br>Salt Lake,<br>Kolkata 700 098<br>
India<br>