On Oct 1, 2013, at 3:07 PM, Gus Correa wrote:
> Thanks Jeff for clarifying where is the hurdle (on Infiniband)
> when one tries to build Open MPI as group of static libraries.
> I tried to build OMPI static, and had failures in the past.
> I eventually gave up, but it was never clear why it would
Hi Damiano
Glad to know you sorted out the problem with
your environment variables.
Home-brewed Open MPI tastes much better
than those six-pack canned RPMs.
Did OpenFOAM (was it OpenFoam?) eventually compile and run?
Thanks Jeff for clarifying where is the hurdle (on Infiniband)
when one tries t
If you are using a TCP network for MPI communications, static is fine.
However, if you're trying to use an OS-bypass network such as InfiniBand, RoCE,
or iWARP, using static libraries can be somewhat of a nightmare (because of how
the OpenFabrics Verbs support libraries work). Specifically, I
Hi Gus, today I noticed there was another ompi directory in my path and
maybe it gave some strange errors so I put the new ompi installation at the
first place in PATH and LD_LIBRARY_PATH before the building and everything
went nicely!
So, as you and Jeff said, the problem was in having the rigth
PS: Also, as I mentioned in my first message, disabling
shared libraries may also be a source of headaches.
Why do you need Open MPI to be purely static libraries?
What if you try to build Open MPI again using
the configuration defaults (enable shared, disable static)?
Make sure you cleanup the ol
Hi Damiano
OpenFOAM may have something funny in the Makefiles, perhaps?
Make sure you set the PATH and LD_LIBRARY_PATH right.
A suggestion. Try compiling something VERY SIMPLE with
mpif90.
Say:
my_test.f90:
program my_test
print *, 'This is my test.'
end program my_test
$ /path/to/mp
Dear Jeff,
thanks for your help.
Maybe I found a clue: in the ompi_info output is the following
Package: Open MPI dami...@caillou.dicat.unige.it
Distribution
Open MPI: 1.6.4
Open MPI SVN revision: r28081
Open MPI release date: Feb 19, 2013
On Sep 30, 2013, at 12:16 PM, Gus Correa wrote:
> "which mpif90" will tell you what you are actually using.
This is what I'm guessing is wrong -- if ompi_info is telling you that you have
Fortran bindings available, then I'm guessing you're somehow getting the
"wrong" mpif90 (i.e., an mpif90 f
Hi Gus, first of all thank you very much for you help. I really appreciate!
Then you are right, I have OpenFOAM so 'which mpif90' addresses to another
installation that probably wasn't meant to have f90 bindings. However, when
I compile my f90 code I use absolute path.
Even when I am in the /bin
Hi Damiano
Did you setup your PATH and LD_LIBRARY_PATH
to point to your OMPI installation?
I.e. to:
/home/damiano/fortran/openmpi-1.6.5/installation/bin
and
/home/damiano/fortran/openmpi-1.6.5/installation/lib
Some OS distributions, commercial compilers, and other software,
come with "extra" O
Dear list,
I'm trying to install openMPI on a Linux 64-bit OpenSuse machine with the
following lines
./configure FC=gfortran
--prefix=/home/damiano/fortran/openmpi-1.6.5/installation/ --disable-shared
--enable-static --with-mpi-f90-size=medium --enable-mpi-f90 cflags=-m64
cxxflags=-m64 fflags=-m6
11 matches
Mail list logo
