Hi George
I don't think this is a library mismatch. I just followed your
instructions and got:
$ otool -L a.out
a.out:
/opt/openmpi/1.3.3-g95-32/lib/libmpi_f77.0.dylib (compatibility
version 1.0.0, current version 1.0.0)
/opt/openmpi/1.3.3-g95-32/lib/libmpi.0.dylib (compatibility version
1.0.0, current version 1.0.0)
/opt/openmpi/1.3.3-g95-32/lib/libopen-rte.0.dylib (compatibility
version 1.0.0, current version 1.0.0)
/opt/openmpi/1.3.3-g95-32/lib/libopen-pal.0.dylib (compatibility
version 1.0.0, current version 1.0.0)
/usr/lib/libutil.dylib (compatibility version 1.0.0, current version
1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 111.1.4)
/usr/lib/libmx.A.dylib (compatibility version 1.0.0, current version
292.4.0)
My configure line is just:
./configure --prefix=/opt/openmpi/1.3.3-g95-32 \
--enable-mpirun-prefix-by-default \
F77=g95 FC=g95
Ricardo
On Jul 28, 2009, at 17:00 , users-requ...@open-mpi.org wrote:
Ricardo,
I checked on Linux and on Mac OS X 10.5.7 with the fortran compilers
from (hpc.sourceforge.net) and I get the correct answer. As you only
report problems on Mac OS X I wonder if the real source of the problem
is not coming from a library mismatch. As you know, Open MPI is
bundled in Leopard. We had problems in the past if the user install
their own version, if the paths are not correctly set.
Let's try to understand what the problem is on your system. First
please compile your version of Open MPI by adding --enable-mpirun-
prefix-by-default to the configure line. Then once everything is
installed, compile a simple application (inplace.F is a good example),
do a "otool -L a.out" and send out the output.
Thanks,
george.
