Problem with mpi

Wed Dec 13 08:59:52 CST 2006

Hi,

I can get some answers but they'r all of the wrong values. I'm basically
using a sample code to solve the poisson eqn by reading the A matrix and b
(rhs) from files. Then the answers (x) are written on a file to check. Using
another system (ia32 xeon), I got the correct ans. But using this server
(em64t xeon), I've got the ans but this time, they'r all wrong, although
they'r still finite e.g. 3.68e-2 compared to 1.56e2

I used ifort,icc 9,intel mkl 8 or blas. the previous sys uses the same
software, except that it's ia32. Of cos, the mpi software is also different.
Hence I wonder if the correct lib file is used.

Thanks.

On 12/13/06, Barry Smith <bsmith at mcs.anl.gov> wrote:
>
>
>
> On Wed, 13 Dec 2006, Ben Tay wrote:
>
> > Hi,
> >
> > I have some problems with using mpi. My code works with one server but
> when
> > I test it on another system, I get the wrong answers. In that system,
> the
> > mpi is located at /usr/local/topspin/mpi/mpich/. I tried to specify it
> with
> > --with-mpi-dir but it wasn't able to find during config. I then add
> > --with-mpirun=/usr/local/topspin/mpi/mpich/bin/mpirun_ssh and it
> > compiled but wrong answers when run.
>                ^^^^^^^^^^^
>
>   This could mean anything. What do you mean by wrong answers? Slightly
> different answers? Hugely different answers? Crashes?
>
>
>
>
>
> > May I know what file does it look for
> > if --with-mpi-lib is used? My lib64 directory has
> >
> > libfmpich.a     libfmpich_p.a   libmpich.a        libmpichf90nc_i.a
> > libmpichf90nc_p.so  libmpichfsup.a     libmpichfsup_p.a   libmpich_i.a
> > libmpich_p.so  libpmpich++.so
> > libfmpich_i.a   libfmpich_p.so  libmpichf90_i.a   libmpichf90nc_i.so
> > libmpichf90_p.a     libmpichfsup_i.a   libmpichfsup_p.so  libmpich_i.so
> > libmpich.so
> > libfmpich_i.so  libfmpich.so    libmpichf90_i.so  libmpichf90nc_p.a
> > libmpichf90_p.so    libmpichfsup_i.so  libmpichfsup.so    libmpich_p.a
> > libpmpich++.a
> >
> >
> > I then tried to use --download-mpich=yes but the error msg is
> >
> >
> *********************************************************************************
> >         UNABLE to CONFIGURE with GIVEN OPTIONS    (see configure.log for
> > details):
> >
> ---------------------------------------------------------------------------------------
> > Error running configure on MPICH: Could not execute 'cd
> > /nfs/lsftmp/g0306332/petsc-2.3.2-p7/externalpackages/mpich2-1.0.4p1
> ;./configure
> > --prefix=/nfs/lsftmp/g0306332/petsc-2.3.2-p7/externalpackages/mpich2-
> 1.0.4p1/linux64-mpi-shared
> > CC="icc  -fPIC -g " --disable-cxx F90="ifort  -fPIC -g  "
> F77="ifort  -fPIC
> > -g  " --enable-sharedlibs=libtool --without-mpe --with-pm=gforker':
> > Configuring MPICH2 version 1.0.4p1 with
> > '--prefix=/nfs/lsftmp/g0306332/petsc-2.3.2-p7/externalpackages/mpich2-
> > 1.0.4p1/linux64-mpi-shared' 'CC=icc  -fPIC -g ' '--disable-cxx'
> 'F90=ifort
> > -fPIC -g  ' 'F77=ifort  -fPIC -g  ' '--enable-sharedlibs=libtool'
> > '--without-mpe' '--with-pm=gforker'
> > Executing mpich2prereq in /nfs/lsftmp/g0306332/petsc-2.3.2-p7
> > /externalpackages/mpich2-1.0.4p1/src/mpid/ch3 with
> > Executing mpich2prereq in /nfs/lsftmp/g0306332/petsc-2.3.2-p7
> > /externalpackages/mpich2-1.0.4p1/src/mpid/ch3/channels/sock
> > sourcing /nfs/lsftmp/g0306332/petsc-2.3.2-p7/externalpackages/mpich2-
> 1.0.4p1
> > /src/pm/gforker/mpich2prereq
> > checking for gcc... icc  -fPIC -g
> > checking for C compiler default output file name... a.out
> > checking whether the C compiler works... yes
> > checking whether we are cross compiling... no
> > checking for suffix of executables...
> > checking for suffix of object files... o
> > checking whether we are using the GNU C compiler... yes
> > checking whether icc  -fPIC -g  accepts -g... yes
> > checking for icc  -fPIC -g  option to accept ANSI C... none needed
> > checking for type of weak symbol support... pragma weak
> > checking whether __attribute__ ((weak)) allowed... yes
> > checking for multiple weak symbol support... yes
> > checking whether we are using the GNU Fortran 77 compiler... no
> > checking whether ifort  -fPIC -g   accepts -g... yes
> > checking how to get verbose linking output from ifort  -fPIC -g  ... -v
> > checking for Fortran libraries of ifort  -fPIC -g  ...
> > -L/usr/local/intel/fc9.0/lib -L/usr/lib/gcc/x86_64-redhat-linux/3.4.6/
> > -L/usr/lib/gcc/x86_64-redhat-linux/3.4.6/../../../../lib64 -lsvml
> -lifport
> > -lifcore -limf -lm -lirc -lgcc_s -lirc_s
> > checking whether C can link with  -L/usr/local/intel/fc9.0/lib
> > -L/usr/lib/gcc/x86_64-redhat-linux/3.4.6/
> > -L/usr/lib/gcc/x86_64-redhat-linux/3.4.6/../../../../lib64 -lsvml
> -lifport
> > -lifcore -limf -lm -lirc -lgcc_s -lirc_s... yes
> > checking for linker for Fortran main programs... Use Fortran to link
> > programs
> > checking for Fortran 77 name mangling... lower underscore
> > checking that f works as the extension for Fortran 90 program... yes
> > checking whether we are using the GNU Fortran 90 compiler... no
> > checking whether ifort  -fPIC -g   accepts -g... yes
> > checking for extension for Fortran 90 programs... f90
> > checking whether the Fortran 90 compiler (ifort  -fPIC -g    ) works...
> yes
> > checking whether the Fortran 90 compiler (ifort  -fPIC -g    ) is a
> > cross-compiler... no
> > checking whether Fortran 90 works with Fortran 77... yes
> > checking whether Fortran accepts ! for comments... yes
> > checking for include directory flag for Fortran... -I
> > checking for Fortran 77 flag for library directories... -L
> > checking for which Fortran libraries are needed to link C with
> Fortran...
> > none
> > checking whether Fortran compiler processes .F files with C
> preprocessor...
> > yes
> > checking that f works as the extension for Fortran 90 program... yes
> > checking whether we are using the GNU Fortran 90 compiler... (cached) no
> > checking whether ifort  -fPIC -g   accepts -g... (cached) yes
> > checking for extension for Fortran 90 programs... f90
> > checking whether the Fortran 90 compiler (ifort  -fPIC -g    ) works...
> yes
> > checking whether the Fortran 90 compiler (ifort  -fPIC -g    ) is a
> > cross-compiler... no
> > checking for Fortran 90 module extension... mod
> > checking for Fortran 90 module include flag... -I
> > checking whether Fortran 90 accepts f90 suffix... yes
> > checking whether Fortran 90 compiler processes .F90 files with C
> > preprocessor... yes
> > checking for f90 compiler vendor... intel
> > checking for perl... /usr/bin/perl
> > checking for ar... ar
> > checking for ranlib... ranlib
> > checking for etags... etags
> > checking for etags argument to specify language... --language=c
> > checking whether global variables handled properly... yes
> > checking for a BSD-compatible install... /usr/bin/install -c
> > checking whether install works... yes
> > checking whether install breaks libraries... no
> > checking whether mkdir -p works... yes
> > checking for make... make
> > checking whether clock skew breaks make... no
> > checking whether make supports include... yes
> > checking whether make allows comments in actions... yes
> > checking for virtual path format... VPATH
> > checking whether make sets CFLAGS... no
> > checking for bash... /bin/sh
> > checking whether /bin/sh supports arrays... yes
> > configure: error: Creating shared libraries using libtool not yet
> supported
> >
> *********************************************************************************
> >
> > May I know what's wrong?
> >
> > Thank you.
> >
> > Regards
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20061213/6f144257/attachment.htm>