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