[Pw_forum] Can I get pw.x and memory.x for my linux pc cluster
Abdelouahab O.
aouahab at yahoo.fr
Sat Feb 12 17:25:37 CET 2005
Thanks;
I've changed the make.sys like you's
# make.sys. Generated from make.sys.in by configure.
CC = mpicc
CCFLAGS = -O3 -fomit-frame-pointer -funroll-loops $(DFLAGS) $(IFLAGS)
# See include/defs.h.README for a list of precompilation options
# (possible arguments to -D or -U) and their meaning
DFLAGS = -D__LINUX -D__INTEL -D__MPI -D__PARA -D__FFTW -D__LAM -D__USE_INTERNAL_FFTW
FDFLAGS = $(DFLAGS)
IFLAGS = -I. -I../include -I../Modules -I../PW -I../PH
CPP = cpp
CPPFLAGS = -P -traditional $(DFLAGS) $(IFLAGS)
F77 = mpiifort
F90 = mpiifort
FFLAGS = -O2 -unroll -tpp7 -assume byterecl $(IFLAGS)
F77FLAGS = $(FFLAGS)
F90FLAGS = $(FFLAGS) -nomodule -fpp $(FDFLAGS)
F77FLAGS_NOOPT = -O0
LD = mpiifort -i-static
LDFLAGS = -static-libcxa $(LIBOBJS)
LIBOBJS = ../flib/ptools.a ../flib/flib.a ../clib/clib.a
# LIBS must contain the location of all needed external libraries
LIBS = -L/home/wahab/atals -latlas_p4 -L/opt/intel/mkl72/lib/32 -lmkl_lapack -lmkl_ia32 -lguide -L/usr/lib/lam
# MYLIB can be one of the following (depending on LIBS):
# blas : compile the local copy of blas routines
# lapack : compile the local copy of lapack routines
# blas_and_lapack : all of the above - use this for a quick test
# or if you don't have an optimized blas/lapack library
# lapack_ibm : compile only lapack routines not present in IBM ESSL
# use this together with IBM ESSL
# lapack_t3e : compile only lapack routines not present in T3E scilib
# use this together with T3E scilib
# lapack_mkl : compile only lapack routines not present in Intel MKL
# use this together with Intel MKL
MYLIB =
AR = ar
ARFLAGS = ruv
RANLIB = echo
//////////////////////////////////////
but the line: LIBS = -L/home/wahab/atals -latlas_p4 -L/opt/intel/mkl72/lib/32 -lmkl_lapack -lmkl_ia32
because i think the library in your "/home/akohlmey/lib" is atlas libs; so I added the atlas library with the mkl
since I have the 8.1.20 version of intel complier i used "-static-libcxa $(LIBOBJS)"
make clean;./makedeps.sh make all I got:
make[1]: Entering directory `/home/wahab/pw2.1.2/Modules'
mpiifort -O2 -unroll -tpp7 -assume byterecl -I. -I../include -I../Modules -I../PW -I../PH -nomodule -fpp -D__LINUX -D__INTEL -D__MPI -D__PARA -D__FFTW -D__LAM -D__USE_INTERNAL_FFTW -c io_global.f90
........
........ (making clib, flib is ok)
........ but
all programs in PW/ were compiled but linking them fails:
mpiifort -i-static -o memory.x memory.o add_efield.o add_vuspsi.o addusdens.o addusforce.o addusstress.o allocate_fft.o
allocate_locpot.o allocate_nlpot.o allocate_wfc.o atomic_rho.o atomic_wfc.o bachel.o becmod.o bfgs.o bp_bess.o bp_c_phase.o
bp_calc_btq.o bp_dbess.o bp_qvan3.o bp_radin.o bp_strings.o bp_ylm_q.o c_bands.o c_gemm.o ccalbec.o ccgdiagg.o cdiagh.o
cdiaghg.o cegterg.o cft3.o cft3s.o cft_3.o cft_sgi.o cft_sp.o cft_sun.o cft_t3e.o cfts_3.o cgramg1.o checkallsym.o
checksym.o cinitcgg.o clean_pw.o close_files.o compute_dip.o compute_scf.o constraints_module.o coset.o cryst_to_car.o
cubicsym.o d_matrix.o data_structure.o davcio.o delta_e.o deriv_drhoc.o diis_base.o real_diis_module.o
complex_diis_module.o diropn.o divide.o divide_et_impera.o dndepsilon.o dndtau.o dprojdepsilon.o dprojdtau.o
dqvan2.o drhoc.o dvloc_of_g.o dynamics.o efermig.o efermit.o electrons.o eqvect.o error_handler.o estimate.o ewald.o
ewald_dipole.o fftw.o force_cc.o force_corr.o force_ew.o force_hub.o force_lc.o force_us.o forces.o functionals.o g_psi.o
g_psi_mod.o gen_at_dj.o gen_at_dy.o gen_us_dj.o gen_us_dy.o ggen.o gk_sort.o gradcorr.o gweights.o h_1psi.o h_psi.o
hexsym.o hinit0.o hinit1.o init_ns.o init_paw_1.o init_paw_2.o init_pool.o init_run.o init_us_1.o init_us_2.o init_at_1.o
init_vloc.o input.o interpolate.o io_pot.o ions.o irrek.o iweights.o kpoint_grid.o lchk_tauxk.o linmin.o lsda_functionals.o
make_pointlists.o mix_pot.o mix_rho.o mode_group.o move_ions.o multable.o n_plane_waves.o new_ns.o ns_adj.o newd.o
noncol.o openfil.o ortho.o orthoatwfc.o output_tau.o para.o paw.o potinit.o print_clock_pw.o psymrho.o punch.o pw_gemm.o
pwcom.o qvan2.o rdiaghg.o read_conf_from_file.o read_file.o read_ncpp.o read_pseudo.o readin.o readnewvan.o readvan.o
regterg.o remove_atomic_rho.o reset_k_points.o restart.o restart_from_file.o restart_in_electrons.o restart_in_ions.o
rgen.o rho2zeta.o rotate_wfc.o rotate_wfc_gamma.o ruotaijk.o s_1psi.o s_axis_to_ca.o s_gemm.o s_psi.o save_in_cbands.o
save_in_electrons.o save_in_ions.o scala_cdiag.o scala_cdiaghg.o scala_utils.o scale_h.o scopy_t3e.o seqopn.o
set_fft_dim.o set_hubbard_l.o set_kplusb.o set_kplusq.o set_kup_and_kdw.o set_rhoc.o set_vrs.o setlocal.o setqf.o
setup.o setupkpt.o sgam_at.o sgam_at_mag.o sgam_ph.o sgama.o show_memory.o smallg_q.o spinor.o sph_ind.o startup.o
stop_pw.o stres_cc.o stres_ewa.o stres_gradcorr.o stres_har.o stres_hub.o stres_knl.o stres_loc.o stres_us.o stress.o
struct_fact.o sum_band.o sumkg.o sumkt.o summary.o swap.o symrho.o symtns.o symvect.o symz.o tabd.o trntns.o trnvecc.o
trnvect.o tweights.o update_pot.o updathes.o upf_to_internal.o usnldiag.o v_of_rho.o vcsmd.o vcsubs.o vhpsi.o
vloc_of_g.o vloc_psi.o vpack.o w0gauss.o w1gauss.o wfcinit.o wgauss.o write_config_to_file.o write_ns.o wsweight.o
../Modules/atom.o ../Modules/basic_algebra_routines.o ../Modules/berry_phase.o ../Modules/bfgs_module.o
../Modules/cell_base.o ../Modules/check_stop.o ../Modules/clocks.o ../Modules/constants.o ../Modules/control_flags.o
../Modules/fft_base.o ../Modules/fft_scalar.o ../Modules/fft_types.o ../Modules/functionals.o
../Modules/input_parameters.o ../Modules/io_base.o ../Modules/io_files.o ../Modules/io_global.o
../Modules/ions_base.o ../Modules/kind.o ../Modules/mp_buffers.o ../Modules/mp_global.o ../Modules/mp_wave.o
../Modules/mp.o ../Modules/path_base.o ../Modules/path_formats.o ../Modules/path_variables.o
../Modules/path_opt_routines.o ../Modules/path_io_routines.o ../Modules/parallel_include.o ../Modules/parameters.o
../Modules/parser.o ../Modules/pseudo_types.o ../Modules/read_cards.o ../Modules/read_namelists.o
../Modules/readpseudo.o ../Modules/recvec.o ../Modules/shmem_include.o ../Modules/stick_base.o ../Modules/supercell.o
../Modules/uspp.o ../Modules/version.o ../Modules/wavefunctions.o -static-libcxa ../flib/ptools.a ../flib/flib.a ../clib/clib.a
ld: cannot find -lirc_s
/usr/bin/mpif77: No such file or directory
make[1]: *** [memory.x] Error 1
make[1]: Leaving directory `/home/wahab/pw2.1.2/PW'
make: *** [pw] Error 2
What is tjhe meaning of ld: cannot find -lirc_s ?
thanks
Axel Kohlmeyer <axel.kohlmeyer at theochem.ruhr-uni-bochum.de> wrote:On Tue, 8 Feb 2005, Abdelouahab O. wrote:
AO> Hello
AO> Thanks for your relpay;
AO> This is make.sys
hi,
the current version of pwscf (or Quantum-ESPRESSO) is 2.1.2.
with many new features, bugfixes and improvements.
if you have installed you LAM/MPI properly for the intel
compilers you should be able to just use
CC=mpicc
F77=mpif77
F90=mpif90
alternatively you can try to use
CC=env LAMHCC=icc mpicc
F77=env LAMHF77=ifort mpif77
F90=env LAMHF77=ifort mpif77
using the mpiXXX wrappers will make sure, that you include
the proper headers that are matching your LAM installation.
AO> =======================================================
AO> # make.sys. Generated from make.sys.in by configure.
AO> CC = gcc
AO> CCFLAGS = -O3 -fomit-frame-pointer $(DFLAGS)
AO> $(IFLAGS)
AO> # See include/machine.h.README for a list of
AO> precompilation options
AO> # (possible arguments to -D or -U) and their meaning
AO> DFLAGS = -D__LINUX -D__INTEL -D__LAM -D__PARA
AO> -DHAS_ZHEGVX -D__FFTW -D__USE_INTERNAL_FFTW
AO> IFLAGS = -I. -I../include -I../Modules -I../PW
AO> -I../PH
AO> CPP = gcc -E
AO> CPPFLAGS = $(DFLAGS) $(IFLAGS)
AO> F77 = ifort
AO> F90 = ifort
AO> FFLAGS = -Vaxlib -O3 -tpp7 $(IFLAGS)
AO> F77FLAGS = $(FFLAGS)
AO> F90FLAGS = $(FFLAGS) -nomodule -fpp $(DFLAGS)
AO> F77FLAGS_NOOPT = -O0
AO> LD = ifort
AO> LDFLAGS = -Vaxlib -O3 -tpp7 $(LIBOBJS) $(LIBS)
AO> LIBOBJS = ../flib/ptools.a ../flib/flib.a
AO> ../clib/clib.a
AO> # LIBS must contain the location of all needed
AO> external libraries
AO> LIBS = -L/opt/intel/mkl72/lib/32
AO> -lmkl_lapack -lmkl_ia32 -lguide -L/usr/lib/lam
AO> # MYLIB can be one of the following (depending on
AO> LIBS):
AO> # blas : compile the local copy of blas routines
AO> # lapack : compile the local copy of lapack
AO> routines
AO> # blas_and_lapack : all of the above - use this for a
AO> quick test
AO> # or if you don't have an optimized
AO> blas/lapack library
AO> # lapack_ibm : compile only lapack routines not
AO> present in IBM ESSL
AO> # use this together with IBM ESSL
AO> # lapack_t3e : compile only lapack routines not
AO> present in T3E scilib
AO> # use this together with T3E scilib
AO> # lapack_mkl : compile only lapack routines not
AO> present in Intel MKL
AO> # use this together with Intel MKL
AO> MYLIB = lapack_mkl
AO> AR = ar
AO> ARFLAGS = ruv
AO> =======================================================
AO>
AO> And make all gives:
AO> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
AO> make[1]: Entering directory
AO> `/home1/wahab/pwscf2.0.4/pwscf/Modules'
[...]
AO> fortcom: Warning: mp_wave.f90, line 130: A dummy
AO> argument with an expl
AO> icit INTENT(OUT) declaration is not given an explicit
AO> value. [PW]
AO> SUBROUTINE splitwf ( pw, pwt, ngwl, ig_l2g,
AO> mpime, nproc, root,
AO> comm )
AO> ...........................^
AO> fortcom: Warning: mp_wave.f90, line 23: A dummy
AO> argument with an expli
this looks like a 'feature', that only the recent intel
fortran (and the DEC/Compaq) compilers choke on. this
may have been fixed in the newer releases. i remember
to have seen several of those with version 2.1 which
are now fixed.
AO> -D__USE_INTERNAL_FFTW -c broadcast.f90
AO> fortcom: Error: broadcast.f90, line 146: This name has
AO> already been assigned a data type.
AO> [MPI_DOUBLE_PRECISION]
AO> INTEGER MPI_REAL4, MPI_DOUBLE_PRECISION,
AO> MPI_REAL16
AO> .........................^
AO> compilation aborted for broadcast.f90 (code 1)
AO> make[1]: *** [broadcast.o] Error 1
AO> make[1]: Leaving directory
AO> `/home1/wahab/pwscf2.0.4/pwscf/PW'
AO> make: *** [pw] Error 2
i cannot reproduce this on my desktop with pwscf v2.0.4,
my installation of LAM/MPI version 7.0.6 and the intel
compiler version 8.1. in my distribution broadcast.f90
only has 41 lines, so your error on line 146 looks
very suspicious. same is for the content, 'MPI_REAL4'
is only present in MPICH installations and not in LAM/MPI.
if you have administrator priviledge on your machine,
you can download my LAM/MPI package as rpm from:
http://www.theochem.ruhr-uni-bochum.de/~axel.kohlmeyer/cpmd-linux.html#mpi
these rpm are compiled special to be compatible to the intel
compilers as well as g77 or the pgi compilers. you simply need
to use mpiifort/mpiicc instead of mpif77/mpicc.
regards,
axel.
AO>
AO> --- Paolo Giannozzi a écrit :
AO> > On Sunday 06 February 2005 10:46, Abdelouahab O.
AO> > wrote:
AO> >
AO> > > I have a pc linux cluster with ifort8.0, mkl7.2,
AO> > and
AO> > > LAM7.0.6: the parallel compilation cant be
AO> > finilized
AO> > > using the -D__LAM -D__PARA, the error apppears
AO> > when
AO> > > compiling broadcast.f90
AO> >
AO> > which error?
AO> > _______________________________________________
AO> > Pw_forum mailing list
AO> > Pw_forum at pwscf.org
AO> > http://www.democritos.it/mailman/listinfo/pw_forum
AO> >
AO>
AO>
AO>
AO>
AO>
AO>
AO>
AO> Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails !
AO> Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/
AO> _______________________________________________
AO> Pw_forum mailing list
AO> Pw_forum at pwscf.org
AO> http://www.democritos.it/mailman/listinfo/pw_forum
AO>
AO>
--
=======================================================================
Dr. Axel Kohlmeyer e-mail: axel.kohlmeyer at theochem.ruhr-uni-bochum.de
Lehrstuhl fuer Theoretische Chemie Phone: ++49 (0)234/32-26673
Ruhr-Universitaet Bochum - NC 03/53 Fax: ++49 (0)234/32-14045
D-44780 Bochum http://www.theochem.ruhr-uni-bochum.de/~axel.kohlmeyer/
=======================================================================
If you make something idiot-proof, the universe creates a better idiot.
_______________________________________________
Pw_forum mailing list
Pw_forum at pwscf.org
http://www.democritos.it/mailman/listinfo/pw_forum
---------------------------------
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails !
Créez votre Yahoo! Mail
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/attachments/20050212/ce762628/attachment.htm
More information about the Pw_forum
mailing list