Hello I tried configure with FCFLAGS=-lSystemStubs and with both FCFLAGS=-lSystemStubs and LDFLAGS=-lSystemStubs. Again it died during configure both times. I can provide configure output if desired. I also decided to try version 1.1a7. With LDFLAGS=-lSystemStubs, with our without FCFLAGS=-lSyste
Already done. I grabbed the rc5 this morning and rebuilt everything. I am
still having the same issue. I sent a message to the openib list about it. I
wont cross-spam this list with that message. I was wondering if you have
access to that list or not ? I can send you a copy if you need it. The
sum
In further discussions with other OMPI team members, I double checked
(should have checked this in the beginning, sorry): OFED 1.0rc4 does not
support 64 bit on PPC64 platforms; it only supports 32 bit on PPC64
platforms.
Mellanox says that 1.0rc5 (cut this morning) supports 64 bit on PPC64
platf
Brian gave a much more complete description of the problem than me;
thanks.
We'll have this fixed in v1.0.3 (and later) such that you can use
LDFLAGS / LIBS, as expected, and you will not have to pass -l values
through FCFLAGS (which is quite definitely not the Right place to pass
in -l value).
N
On Wed, 24 May 2006, Terry Reeves wrote:
Here is the out put for both g95 and gfortran
???
From the output you sent, you ran "./configure FC=g95". Configure did
not find a valid F77 compiler, and therefore skipped both the F77 and
F90 bindings.
Can you try:
./configure FC=g95 F77=g95
an
On Thu, 25 May 2006, Brock Palen wrote:
We are trying to track down a problem with our network, the question
has come up, if its posable that the mpi lib (OMPI) could be using
ether multicast or broadcast (or both)
In what cases could multicast traffic be seen if OMPI is our mpi lib.
At this
We are trying to track down a problem with our network, the question
has come up, if its posable that the mpi lib (OMPI) could be using
ether multicast or broadcast (or both)
In what cases could multicast traffic be seen if OMPI is our mpi lib.
Brock
The commit is quite simple. You can simply modify the ompi/mca/ptl/gm/
ptl_gm_component.c at line 249 and replace the PTHREAD_CANCELED with
0 and your problem will be solved. This fix was committed yesterday
it will be on the next 1.0.3 release, or you can grab it from the
nightly build sect
I didn't do a formal uninstall as you demonstate below, but instead went
into the 'prefix' directory and renamed 'bin','lib','etc','include', and
'share'
before running the 1.0.2 build and install. That way I didn't blow up my
1.0.1 installation, and it was easy to switch back in case the 1.0.2
Is there a way to disable pthreads when building with gm? i can
build with just tcp just fine.
Brock
On May 25, 2006, at 3:34 PM, George Bosilca wrote:
That's kind of funny ... Look like the PTHREAD_CANCEL was missing
from the pthread.h on most of the Linux distributions until the
beginning
Okay, I rebuilt using those diffs. Currently I am still having issues with
pallas however. That being said I think my issue is more with
compiling/linking pallas. Here is my pallas make_$arch file:
MPI_HOME = /opt/ompi/
MPI_INCLUDE = $(MPI_HOME)/include
LIB_PATH =
LIBS =
CC = ${MPI_HOME}/bin/mpic
I actually had to set FCFLAGS, not LDFLAGS, to get arbitrary flags
passed down to the Fortran tests in configure.
Can you try that? (I'm not 100% sure -- you may need to specify LDFLAGS
*and* FCFLAGS...?)
We have made substantial improvements to the configure tests with
regards to the MPI F90
Gleb just committed some fixes for the PPC64 issue last night
(https://svn.open-mpi.org/trac/ompi/changeset/10059). It should only
affect the eager RDMA issues, but it would be a worthwhile datapoint if
you could test with (i.e., specify no MCA parameters on your mpirun
command line, so it should
> -Original Message-
> From: users-boun...@open-mpi.org
> [mailto:users-boun...@open-mpi.org] On Behalf Of ??
> Sent: Thursday, May 25, 2006 4:54 AM
> To: us...@open-mpi.org
> Subject: [OMPI users] SEGV_ACCERR Failing at addr ...
>
> Hi,all
> I tried to use hostfile option to launch MPI j
Just to follow up for the web archives -- this has now been fixed on the
trunk and v1.1 and v1.0 branches, and will show up in tonight's nightly
snapshots (r10062 or later).
> -Original Message-
> From: users-boun...@open-mpi.org
> [mailto:users-boun...@open-mpi.org] On Behalf Of Mykael
One possibility is that you didn't properly uninstall version 1.0.1
before installing version 1.0.2 & 1.0.3.
There was a change with some of the libraries a while back that
caused me a similar problem. An install of later versions of OpenMPI
do not remove certain libraries from 1.0.1.
Yo
I think I moved to OpenMPI 1.1 and 1.2 alphas because of problems
with spawn and OpenMPI 1.0.1 & 1.0.2.
You may wish to test building 1.1 and seeing if that solves your
problem.
Michael
On May 24, 2006, at 1:48 PM, Jens Klostermann wrote:
I did the following run with openmpi1.0.2
Hi,all
I tried to use hostfile option to launch MPI jobs on several nodes.Each node has
the same Open MPI package installed correctly (version 1.1ra9202).
But only node0 refused to work with other nodes.What should I do?
Can anybody help me? thank you.
[semper@node0]mpirun --hostfile h -np 4 /tmp/
18 matches
Mail list logo
