Do you get any more of an error message than that? Did the process dump
core, and if so, what does a backtrace show?
> -Original Message-
> From: users-boun...@open-mpi.org
> [mailto:users-boun...@open-mpi.org] On Behalf Of Jeffrey B. Layton
> Sent: Wednesday, April 12, 2006 3:12 PM
> T
My mistake -- I missed the "orted" part of the error message.
"orted" is a helper application that is intentally launched by Open MPI
during mpirun. What is happening is that it is not able to find the
Intel libraries, and is therefore failing to launch.
So why is it not finding the Intel shared
FWIW, the "has a different size..." errors means that you may not have been
linking against the shared libraries that you thought you were. This typically
means that the executable expected to find an object in a library of a given
size, but the actual size of the object was different. So some
Do you have a static version of libnuma available? If not, then the
static linking will likely fail.
> -Original Message-
> From: users-boun...@open-mpi.org
> [mailto:users-boun...@open-mpi.org] On Behalf Of Jeffrey B. Layton
> Sent: Wednesday, April 12, 2006 11:31 AM
> To: layto...@cha
> -Original Message-
> From: users-boun...@open-mpi.org
> [mailto:users-boun...@open-mpi.org] On Behalf Of Adams Samuel
> D Contr AFRL/HEDR
> Sent: Wednesday, April 12, 2006 11:14 AM
> To: 'Open MPI Users'
> Subject: Re: [OMPI users] job running question
>
> I got it to work, but it didn
Hello,
I am trying to configure openmpi-1.0.2. However it gives me an error while
running the configuration step. It stops when
trying to determine the "aligment of bool". I attached the outputs as it
is suggested.
The system I am using to build openmpi is an intel P4 running RedHat
Enterpri
I'm using the 8.0 and 9.0 intel compilers on a Xeon cluster without
any problems. And I didn't have to specify any configure flags. Just
the default one:
./configure --prefix=/usr/local/ompi/1.0.2 --with-mvapi=/usr/local/
topspin/ --enable-mpi-f90 --enable-mpi-f77 --enable-mpi-cxx --enable-
m
Troy Telford wrote:
On Wed, 12 Apr 2006 14:34:06 -0600, Jeffrey B. Layton
wrote:
Good afternoon,
While we're on the subject of building OpenMPI-1.0.2 with
Intel, I'm having trouble building OpenMPI-1.0.2 with Intel 9.0.
I'm starting to wonder if I'm doing something magical; I've compile
On Wed, 12 Apr 2006 14:34:06 -0600, Jeffrey B. Layton
wrote:
Good afternoon,
While we're on the subject of building OpenMPI-1.0.2 with
Intel, I'm having trouble building OpenMPI-1.0.2 with Intel 9.0.
I'm starting to wonder if I'm doing something magical; I've compiled Open
MPI 1.0.2 w
Hello,
I got OpenMPI 1.0.2 built with PGI 6.0 that fixed my
previous problem (problem with 1.0.1 and multiple tcp
networks). However, when I tried to run the "is" code
from the NPB I get the following error:
[0] func:/home/jlayton/bin/OPENMPI-1.0.2-PGI6.0-OPTERON/lib/libopal.so.0
[0x2a95e2d4a
Good afternoon,
While we're on the subject of building OpenMPI-1.0.2 with
Intel, I'm having trouble building OpenMPI-1.0.2 with Intel 9.0.
I'm building OpenMPI-1.0.2 with the following options:
./configure --prefix=/home/jlayton/bin/OPENMPI-1.0.2-INTEL9.0-EM64T
--disable-io-romio \
--e
Hi,
I am able to run non-OpenMPI MPI jobs where the MPI library is built on top
of Intel compilers. Plus, non-MPI jobs built with Intel compilers run just
fine. So, I am not sure how to go about fixing this.
Thanks,
Aniruddha
- Original Message -
From: "Jeff Squyres (jsquyres)"
To: "Ope
Just a quick follow-up: Now even /without/ the debug flag, it just
works. I'm wondering if there was some sort of weird action going on with
the subnet manager... but that's not Open MPI's problem. Still, I'm quite
pleased that it works, with almost no effort on my (or hopefully anybody
OK, this is weird. I built 1.0.2 with the following options:
./configure --prefix=/home/jlayton/bin/OPENMPI-1.0.2-PGI6.0-OPTERON
--disable-io-romio \
--enable-static --enable-shared
and installed it. When I tried to build a code with static
links (linking in the libs), it yells about not
I got it to work, but it didn't have anything to do with the environment
variables on the shell.
I am running CentOS 4.2, and the system has everything compiled with the GCC
3.4, and it also has GCC 4.0 installed. I was building ompi with GCC 4.0,
and I think it was having trouble with loading
On Wed, 12 Apr 2006 10:04:18 -0600, Brian Barrett
wrote:
We've tested against the SilverStorm drivers for OS X with success,
but I don't think anyone has tried the Linux drivers. A quick poll
of the developers show that none of us has access to a Linux cluster
using the SilverStorm stack, so
On Apr 12, 2006, at 9:49 AM, Troy Telford wrote:
Disclaimer: This isn't a support request per se; just gathering data.
I'm able to compile Open MPI when SilverStorm's Linux IB drivers
are being
used (using the MVAPI device).
However, it doesn't really work.
A simple 'hello world' that sim
Disclaimer: This isn't a support request per se; just gathering data.
I'm able to compile Open MPI when SilverStorm's Linux IB drivers are being
used (using the MVAPI device).
However, it doesn't really work.
A simple 'hello world' that simply returns the MPI rank seems to work
fine, but
FWIW, I know that we saw similar issues with the Intel 8.1 series
(segv's during compilation). Since we are not doing anything illegal in
terms of C++, we already treated this as a compiler bug that we couldn't
really do much about. Plus, we [perhaps incorrectly] assumed that most
sites using th
Hi there,
We have a Mac network running xgrid and we have successfully installed
mpi. We want to run a parallell version of mrbayes. It did not have any
problem when we compiled mrbayes using mpicc. But when we tried to run the
compiled mrbayes, we got lots errror message
mpiexec -np 4 ./mb -i ye
Greetings.
Your logs look normal.
The problem appears to be how you compiled / linked your final
executable. You said that you used -static -- I don't know offhand if
that is a supported flag for the intel compiler or not. Did you *link*
with -static, or just *compile* with it?
Try running "ld
FWIW, I know that we saw similar issues with the Intel 8.1 series
(segv's during compilation). Since we are not doing anything illegal in
terms of C++, we already treated this as a compiler bug that we couldn't
really do much about. Plus, we [perhaps incorrectly] assumed that most
sites using the
Yoinks; I have no idea how we missed this. Thanks for bringing it to
our attention.
There's a few subtleties involved in fixing this -- we're internally
debating the correct fix. I'll get back to you when we come to a
conclusion on the Right way to fix it.
___
23 matches
Mail list logo
