Hi Guys,
We have a very large executable written in C++, C, F77 and F90 (and we
use all of these compilers!). Our code compiles and links fine but when
we run it on our cluster (under PBSPro) we get the errors at the bottom
of the email.
I wondered if you guys could shed any light on this?
Hello list,
Is there a way to specify different working directories for
different hosts ?. I mean for a single application launched
from one of them. Seems I can't do that in the hostfile ... :/.
Thanks in advance,
Roberto
PS: I was unable to find the answer in the archives, sorry if
On Wed, Feb 20, 2008 at 06:15:27AM -0700, Jeff Squyres wrote:
> The #defines that are mpi.h are limited to the ones that we need for
> that file itself. More specifically: the majority of the #define's that
> are generated via OMPI's configure are not in mpi.h.
And that's much appreciated.
>
I noticed that I was spitting this out on stderr:
Is this an OpenMPI problem?
[prodnode31:26364] *** Process received signal ***
[prodnode31:26364] Signal: Segmentation fault (11)
[prodnode31:26364] Signal code: (128)
[prodnode31:26364] Failing at address: (nil)
[prodnode31:26364] [ 0]
Can you be more specific about what problems you're seeing?
http://www.open-mpi.org/community/help/
Note that the rdma mpool is the plugin that is used by the openib btl;
there is no openib mpool (there used to be, but its functionality got
generalized and put into the "rdma" plugin).
On Feb 19, 2008, at 12:52 PM, Ben Allan wrote:
Is there some subtle reason that ompi's mpi.h
leaves the following macros both
unguarded with an ifndef and un-prefixed with OMPI_ ?
Mainly because they come from standard autoconf/configure tests (e.g.,
AC_CHECK_SIZEOF), meaning that we (OMPI)
Hello everyone, I am facing problem while calling mpirun in a
loop when using with SGE. My sge version is SGE6.1AR_snapshot3. The script i am
submitting via sge is
xlet
i=0while [ $i -lt 100 ]do echo
Yoshi,
Is the appropriate verison of libgfortran.so.1 (32 bit or 64 bit in
your LD_LIBRARY_PATH. what is the out put from
ldd ./a.out
The version of libgfortran.so.1 it lists needs to be in your
LD_LIBRARY_PATH
what does file ./a.out say if it is an AMD x86-64 then you should
put
Dear sirs
I am a beginer with openmpi-1.2.3 (and opensuse10.2).
But, I have some experience with mpich-1.2 and FreeBSD5.4.
I am struggling with them to build scalapack, parallel-octave and matlab on.
I succeeded in installing intel fortran/c 10.0.026 and openMPI-1.2.3, now.
like belows
