Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

From: Jonathan Day (imipak_at_[hidden])
Date: 2005-11-11 19:42:30


Still working on the Broadcom MIPS64 port, so no news
on that front yet except to say that I'm getting
there. (Which seems to be fairly common with people
using Broadcom CPUs.)

On the Pentium 4 front, I can say that recent
snapshots of the experimental GCC 4.1.0 compiled the
C, C++ and Fortran bindings just fine and all tests
worked great.

Because GFortran has serious bugs in it somewhere,
I've had to use G95 (g95.sourceforge.net) for a lot of
Fortran 90 and Fortran 95 code. You do have to set
both the Fortran 77 and Fortran 90 bindings to compile
with G95 if you do this, but it seems to work just
fine.

When enabling threads, remember that the configure
help menu lies. --with-threads=posix should be used,
not --with-threads=pthreads

I've not determined exactly what triggers it, but the
functions in ompi/ompi/mca/pml/pml_teg_ptl.c can clash
with functions from ompi/ompi/mca/pml/pml_uniq_ptl.c
on compile. I'm guessing that I'm using a combination
of compile options that aren't getting tested that
often, if I'm the only one noticing this:

./configure --prefix=/usr/openmpi --enable-mpi-threads
--enable-progress-threads --with-threads=posix
--enable-shared --enable-static --enable-mpi-f77
--enable-mpi-f90

Could someone verify that this problem is repeatable
and not simply a problem at this end?

Thanks.

Jonathan

                
__________________________________
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com