Solaris and NetBSD platforms which displayed the VT Makefile error w/
1.6.2rc2 have completed successful builds w/ 1.6.2rc3.
The PGI-8.0 platform which showed the other VT problem is down at the moment.
So, I've tested that fix on the older (and thus slower) PGI-7.2-5
platform which also displayed
Usual place:
http://www.open-mpi.org/software/ompi/v1.6/
Changes since rc2:
- Update README about IA64 and Intel compilers
- Fix VT compile problems
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
On Sep 12, 2012, at 4:45 PM, Paul Hargrove wrote:
> Sounds like that should resolve my failure - I'll try to verify from a
> nightly tarball when I have the opportunity.
Thanks! I'll probably make another RC this afternoon, because we're really
closing in on it.
> The fix I had in mind would
Sounds like that should resolve my failure - I'll try to verify from a
nightly tarball when I have the opportunity.
The fix I had in mind would have been to parse the mounts with sufficient
intelligence to match a bind-mount to the original mount and determine it's
type.
I suppose that is still po
Okay, yeah - that's a known problem that has previously been discussed on the
user list. Still hasn't been fixed, though it is on the short list for repair
(probably in the 1.7 series).
See bug tracker here:
https://svn.open-mpi.org/trac/ompi/ticket/2904
On Sep 12, 2012, at 10:12 AM, Suraj Pr
I am referring to v1.6.
On Sep 12, 2012, at 5:27 PM, Ralph Castain wrote:
> what version of ompi are you referring to?
>
> On Sep 12, 2012, at 8:13 AM, Suraj Prabhakaran
> wrote:
>
>> Dear all,
>>
>> I observed a strange behavior with MPI_Comm_connect and MPI_Comm_disconnect.
>> In short, a
what version of ompi are you referring to?
On Sep 12, 2012, at 8:13 AM, Suraj Prabhakaran
wrote:
> Dear all,
>
> I observed a strange behavior with MPI_Comm_connect and MPI_Comm_disconnect.
> In short, after two processes connect to each other with a port and merge to
> create a intra comm (
Dear all,
I observed a strange behavior with MPI_Comm_connect and MPI_Comm_disconnect.
In short, after two processes connect to each other with a port and merge to
create a intra comm (rank 0 and rank 1), only one of them (the root) is
thereafter able to reach a third new process through MPI_Co
Cool - thanks!
My configure is available in the code base at
contrib/platform/greenplum/bend/linux.
Appreciate it!
On Sep 12, 2012, at 7:53 AM, "Shamis, Pavel" wrote:
> Ralph,
>
> Please see our comment inline.
>
>> common_allgather.c: In function 'comm_allgather_pml':
>> common_allgather.c
On Sep 11, 2012, at 4:57 PM, Paul Hargrove wrote:
> So, I think the README could use an update with respect to IA64 and ICC.
> Note that I can build w/ gcc just fine on IA64, but I'd not exactly break
> down in tears if OMPI dropped support for IA64 entirely.
Thanks for the reminder!
I added:
Ralph,
Please see our comment inline.
> common_allgather.c: In function 'comm_allgather_pml':
> common_allgather.c:45: warning: 'recv_iov[1].iov_len' may be used
> uninitialized in this function
> common_allgather.c:45: warning: 'send_iov[1].iov_len' may be used
> uninitialized in this function
On Sep 11, 2012, at 3:29 PM, Bert Wesarg wrote:
>>> "/users/phargrov/SCRATCH/OMPI/openmpi-1.6.2rc2-linux-x86_64-pgi-8.0/openmpi-1.6.2rc2/ompi/contrib/vt/vt/tools/vtunify/hooks/vt_unify_hooks_aevents.cc",
>>> line 69: warning:
>>> variable "otf_rc" was set but never used
>>>uint8_t
I just updated the test to check and see if we get a "none" type of filesystem.
If so, we just skip it in the test.
On Sep 11, 2012, at 3:50 PM, Paul Hargrove wrote:
> I am NOT running on BG/Q.
> I am just building for Linux/PPC64 on its front-end node which has very
> recent XLC versions ins
13 matches
Mail list logo
