I went through the compile process with openMPI - twice, using g95 and
gfortran (the default install on my openSuSE11.0 setup). It seems to
have trouble finding the libraries, in particular libopen-pal.so.0
I've seen shared-library problems with some x86_64 packages that I
contrib to SourceForge a
FWIW, we fixed this help message in the upcoming v1.3. The new help
message is:
mca:btl:openib:param:btl_openib_flags:help:BTL bit flags (general
flags: SEND=1, PUT=2, GET=4, SEND_INPLACE=8; flags only used by the
"dr" PML (ignored by others): ACK=16, CHECKSUM=32, RDMA_COMPLETION=128)
So
Hi,
Am 04.11.2008 um 16:54 schrieb Sangamesh B:
Hi all,
In Rocks-5.0 cluster, OpenMPI-1.2.6 comes by default. I guess it
gets installed through rpm.
# /opt/openmpi/bin/ompi_info | grep gridengine
MCA ras: gridengine (MCA v1.0, API v1.3, Component
v1.2.6)
Hi Olivier and list
I presume you are talking about Ethernet or GigE.
The basic information on how to launch jobs is on the OpenMPI FAQ pages:
http://www.open-mpi.org/faq/?category=tcp
http://www.open-mpi.org/faq/?category=tcp#tcp-selection
Here is what I did on our toy/test cluster made of sa
Hi all,
In Rocks-5.0 cluster, OpenMPI-1.2.6 comes by default. I guess it
gets installed through rpm.
# /opt/openmpi/bin/ompi_info | grep gridengine
MCA ras: gridengine (MCA v1.0, API v1.3, Component v1.2.6)
MCA pls: gridengine (MCA v1.0, API v1.3, Compon
Bonjour,
Working with OpenMPI 1.2.5 on RHEL5.2, I noticed a weird default value for
this mca parameter, as printed by ompi_info:
MCA btl: parameter "btl_openib_flags" (current value: "54")
BTL flags, added together: SEND=1, PUT=2, GET=4 (cannot be 0)
Is this expected or not ?
I could understa
Hello,
I am configuring a cluster with multiple nics for use with open mpi.
I have not found very much information on the best way of setting up
my network for open mpi. At the moment I have a pretty standard setup
with a single hostname and single ip address for each node.
Could someone advise me
> *** Fortran 90/95 compiler
> checking whether we are using the GNU Fortran compiler... yes
> checking whether g95 accepts -g... yes
> checking if Fortran compiler works... yes
> checking whether g95 and g95 compilers are compatible... no
> configure: WARNING: *** Fortran 77 and Fortran 90 compile