My testing of real hardware is almost complete and I've reported the only
two issues[*] I encountered:
http://www.open-mpi.org/community/lists/devel/2015/04/17183.php
http://www.open-mpi.org/community/lists/devel/2015/04/17184.php
There were roughly 5 failing configurations out of about 70.
On Mon, Apr 6, 2015 at 5:13 PM, Ralph Castain wrote:
[...]
> I believe we have seen this before, and it was an issue caused by a change
> in libtool itself. The Mac automatically updated to the new version, which
> triggers the problem.
>
> This is why we embedded ltdl directly into the OMPI mast
FWIW: this is on Mac 10.10.2, using clang and clang++
OMPI master - bunch of warnings, but it successfully builds:
In file included from ./libevent/event-internal.h:38:
./libevent/minheap-internal.h:64:6: warning: unused function 'min_heap_ctor'
[-Wunused-function]
void min_heap_ctor(min_heap_t*
I think either solution would be valuable - this is something that came up a
few months ago, but the Java team members couldn’t trace it down, and neither
Jeff nor I had time to pursue it.
> On Apr 6, 2015, at 3:30 PM, Howard Pritchard wrote:
>
> Hi Folks,
>
> There seems to have been recent
Hi Folks,
There seems to have been recent outburst of interest in the mpi java
bindings, so moving in retrograde fashion back to what I use to be doing,
I've started investigating the Ompi JNI code.
I'm noticing that at least on sles11sp3, that soon after the java vm
invokes the JNI_OnUnload of t
On MacOS X 10.8 (where cc and c++ are clang and clang++, and the default
ABI is LP64) I've configured the release candidate with
--prefix= --enable-debug CC=cc CXX=c++
The build fails linking opal_wrapper as shown in the "make V=1" output
below.
Based on the undefined symbol (_lt_libltdlc_
I am trying to build Open MPI 1.8.5rc1 wit AMDs Open64 4.5.2.1.
I see the following failure (from "make V=1") while building VT:
openCC -DHAVE_CONFIG_H -I.
-I/scratch/phargrov/OMPI/openmpi-1.8.5rc1-linux-x86_64-open64/openmpi-1.8.5rc1/ompi/contrib/vt/vt/tools/vtfilter
-I../..
-I/scratch/phargro
> On Apr 6, 2015, at 11:47 AM, Paul Hargrove wrote:
>
> Two comments on the proposed NEWS:
>
>
> - Don't use inline functions with Clang compiler
>
> Without motivation/explanation that sounds like a bad thing.
Some versions of clang (at least >= 3.5 -- perhaps older versions, too?) will
wa
Two comments on the proposed NEWS:
- Don't use inline functions with Clang compiler
>
Without motivation/explanation that sounds like a bad thing.
> - Improved support for Cray
>
Cray's compilers, networks or the programming environment in general?
-Paul
--
Paul H. Hargrove
