Hi,
I built and packaged openmpi-1.6.3 for cygwin.
Before deploying it as an official package, I would
like feedback from testers.
Source and binary here:
http://matzeri.altervista.org/cygwin-1.7/openmpi/
To install using cygwin setup program
setup.exe -X -O -s http://matzeri.altervista.org
Hello all,
Open MPI is clever and use by default multiple IB adapters, if available.
http://www.open-mpi.org/faq/?category=openfabrics#ofa-port-wireup
Open MPI is lazy and establish connections only iff needed.
Both is good.
We have kinda special nodes: up to 16 sockets, 128 cores, 4 boards,
On Oct 31, 2012, at 10:23 AM, Ralph Castain wrote:
> 2. you could go to the gnu site and download libtool yourself, build it, and
> then ensure it is in your default path
If you go this route, read the HACKING document at the top-level Open MPI
directory. It has directions on how to
The "libompi" was just a shorthand way of saying it can't load the OMPI
libraries - it actually is looking for the libopen-rte in your /lib directory.
But that isn't the problem. The problem is that we require ltdladvise in order
to correctly load those libraries. Given that you are building
Hello again.
The fault is still there and I can't locate it.
It seem's the first part of the message came from the file
ompi/mpi/java/c/mpi_MPI.c : NO LT_DLADVISE - CANNOT LOAD LIBOMPI
and the second part from
ompi/mpi/java/java/MPI.java
I run a 'make install' in both directories.
As the
Wow - you are quite correct. Thanks for chasing this down!!
On Oct 31, 2012, at 1:56 AM, marco atzeri wrote:
> looking on a solution for
> http://www.open-mpi.org/community/lists/users/2012/10/20495.php
>
> I noticed that the issue disappears on 1.6.2 with the patch:
>
Got it - thanks!
On Oct 31, 2012, at 1:11 AM, Aleksej Saushev wrote:
> Hello,
>
> (Once again...)
>
> Diff against openmpi-1.7rc5r27536
>
>
> --
> HE CE3OH...
> ___
> users mailing list
> us...@open-mpi.org
>
*** IF YOU RUN MTT, YOU NEED TO READ THIS.
Due to some server re-organization at Indiana University (read: our gracious
hosting provider), we are moving the Open MPI community MTT database to a new
server. Instead of being found under www.open-mpi.org/mtt/, the OMPI MTT
results will soon be
You might want to find errno.h in your machine and see what the #define'd name
for 108 is.
On Oct 31, 2012, at 3:04 AM, Mathieu Gontier wrote:
> I do not know too :-/
>
> On Tue, Oct 30, 2012 at 2:37 PM, Jeff Squyres wrote:
> What's errno=108 on your platform?
>
> On Oct
looking on a solution for
http://www.open-mpi.org/community/lists/users/2012/10/20495.php
I noticed that the issue disappears on 1.6.2 with the patch:
--- opal/util/path.c~ 2012-04-03 16:29:52.0 +0200
+++
Hello,
(Once again...)
Diff against openmpi-1.7rc5r27536
patch-orte_config_orte__setup__hadoop.m4
Description: test \"==\" portability fix
--
HE CE3OH...
I do not know too :-/
On Tue, Oct 30, 2012 at 2:37 PM, Jeff Squyres wrote:
> What's errno=108 on your platform?
>
> On Oct 30, 2012, at 9:22 AM, Damien Hocking wrote:
>
> > I've never seen that, but someone else might have.
> >
> > Damien
> >
> > On 30/10/2012 1:43 AM,
<#multipart type=mixed>
<#part type=text/plain nofile=yes>
Hello,
Diff against openmpi-1.7rc5r27536
<#part type=application/octet-stream
filename="patch-orte_config_orte__setup__hadoop.m4" disposition=attachment
buffer=" *mml*" description="test \"==\" portability fix">
<#/part>
<#part
13 matches
Mail list logo