This has me stumped. My code seg faults (sometimes) while
it's attempting to free a communicator--at least, that's what the
stack trace indicates, and that's what Totalview also shows.
This happens when I run the program with 27 processes. If I run with 8,
the program finishes without error. (T
I knew that but have considered it again. I wonder whether the info at
the end of this mail suggests how to operate from the viewpoint of
openmpi in compiling a code.
In trying to compile openmpi-1.3.1 on debian amd64 lenny, intels
10.1.022 do not see their librar libimf.so, which is on the unix p
Hi Ankush
To test if OpenMPI works, compile and run the examples (hello_c, etc)
in the examples/ directory (on the directory where you decompressed
the OpenMPI tarball, not where you installed OpenMPI).
Compile them with mpicc, etc, and run them with mpiexec,
all from OpenMPI.
Using full path na
Ankush Kaul wrote:
I am able to run the program on de server node, but in de compute node
the program only runs in the directory on which the de /work is mounted
(/work on de server contains de Pi program).
Also while running Pi it shows de process running only on server not
compute node(us
Seeing the following building openmpi 1.3.1 on CentOS 5.3 with PGI pgf90
8.0-5 fortran compiler:
checking if C compiler and POSIX threads work with -Kthread... no
checking if C compiler and POSIX threads work with -kthread... no
checking if C compiler and POSIX threads work with -pthread... yes
Please send all the information listed here:
http://www.open-mpi.org/community/help/
Thanks.
On Apr 13, 2009, at 6:48 PM, Orion Poplawski wrote:
Seeing the following building openmpi 1.3.1 on CentOS 5.3 with PGI
pgf90
8.0-5 fortran compiler:
checking if C compiler and POSIX threads wo
