[OMPI devel] v1.4.5rc6 released

Usual location: http://www.open-mpi.org/software/ompi/v1.4/ Changes since rc5: - document LD_LIBRARY_PATH for -m32 with Ubuntu/Sun compilers - refuse to configure with gccffs - LANL TLCC2 platform files -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to:

[hwloc-devel] Create success (hwloc r1.3.2rc2r4296)

Creating nightly hwloc snapshot SVN tarball was a success. Snapshot: hwloc 1.3.2rc2r4296 Start time: Fri Feb 10 21:07:18 EST 2012 End time: Fri Feb 10 21:10:39 EST 2012 Your friendly daemon, Cyrador

[hwloc-devel] Create success (hwloc r1.4.1a1r4298)

Creating nightly hwloc snapshot SVN tarball was a success. Snapshot: hwloc 1.4.1a1r4298 Start time: Fri Feb 10 21:04:18 EST 2012 End time: Fri Feb 10 21:07:18 EST 2012 Your friendly daemon, Cyrador

Re: [OMPI devel] 1.4.5rc5 has been released

On Feb 10, 2012, at 8:57 PM, Jeff Squyres wrote: > 1.5.5rc2 coming soon. I should qualify that statement: many things have been resolved, but there's a few more things to go. A new rc will come when they have been resolved: https://svn.open-mpi.org/trac/ompi/report/15 -- Jeff Squyres

Re: [OMPI devel] 1.4.5rc5 has been released

On Feb 7, 2012, at 4:25 PM, Paul H. Hargrove wrote: > + I can't build w/ the PGI compilers on MacOS Lion. > This was previously reported in > http://www.open-mpi.org/community/lists/devel/2012/01/10258.php I'm officially pushing this to v1.6. See

Re: [OMPI devel] RFC: Add "virbr0" to [btl|oob]_tcp_if_exclude?

That's probably a reflection of the status of the "Open MPI User Documentation" sub-project :-) On 2/10/2012 5:12 PM, Jeff Squyres wrote: FWIW: google analytics indicates that the FAQ and the mailing list archives are among the most heavily used sections of the web site. :-) -- Paul H.

Re: [OMPI devel] RFC: Add "virbr0" to [btl|oob]_tcp_if_exclude?

FWIW: google analytics indicates that the FAQ and the mailing list archives are among the most heavily used sections of the web site. :-) On Feb 10, 2012, at 8:09 PM, Paul H. Hargrove wrote: > Much better - at least to the extent that users actually read FAQs :-) > -Paul > > On 2/10/2012 5:01

Re: [OMPI devel] RFC: Add "virbr0" to [btl|oob]_tcp_if_exclude?

Much better - at least to the extent that users actually read FAQs :-) -Paul On 2/10/2012 5:01 PM, Jeff Squyres (jsquyres) wrote: Check out #220 now; I updated it. -- Paul H. Hargrove phhargr...@lbl.gov Future Technologies Group HPC Research Department

Re: [OMPI devel] RFC: Add "virbr0" to [btl|oob]_tcp_if_exclude?

Check out #220 now; I updated it. Sent from my phone. No type good. On Feb 10, 2012, at 4:46 PM, "Jeff Squyres" wrote: > On Feb 10, 2012, at 3:32 PM, Paul H. Hargrove wrote: > >> The point of the question isn't related to WHY eth8 is useless - just assume >> it is. >>

Re: [OMPI devel] RFC: Add "virbr0" to [btl|oob]_tcp_if_exclude?

On Feb 10, 2012, at 3:32 PM, Paul H. Hargrove wrote: > The point of the question isn't related to WHY eth8 is useless - just assume > it is. > Assume it is UP, but useless for whatever reasons motivated writing FAQ #220. > It could be Terry's example of a port connected to the service processor.

Re: [OMPI devel] RFC: Java MPI bindings

This topic has gotten a *lot* of off-list discussion. :-) Just to tie up the thread for the web archives: this topic will be discussed on the Tuesday teleconf next week. Terry: please add this to the Tuesday agenda. On Feb 8, 2012, at 9:53 PM, Ralph Castain wrote: > I agree - we do have

Re: [OMPI devel] RFC: Add "virbr0" to [btl|oob]_tcp_if_exclude?

On 2/10/2012 12:21 PM, Jeff Squyres wrote: On Feb 10, 2012, at 3:14 PM, Paul H. Hargrove wrote: + User knows nothing about xen, and thus nothing about virbr0 + User has a local-only interface (eth8 in my made up example) + User reads FAQ entry "220. How do I tell Open MPI which TCP networks

Re: [OMPI devel] RFC: Add "virbr0" to [btl|oob]_tcp_if_exclude?

On Feb 10, 2012, at 3:14 PM, Paul H. Hargrove wrote: > + User knows nothing about xen, and thus nothing about virbr0 > + User has a local-only interface (eth8 in my made up example) > + User reads FAQ entry "220. How do I tell Open MPI which TCP networks to > use?" > + User follows instructions

Re: [OMPI devel] RFC: Add "virbr0" to [btl|oob]_tcp_if_exclude?

On 2/10/2012 12:03 PM, Jeff Squyres wrote: On Feb 10, 2012, at 1:44 PM, Paul H. Hargrove wrote: Since the situation described is one where the user didn't know they could/should disable xen, it is reasonable to think they ALSO don't know they need to exclude virbr0. That's what I'm

Re: [OMPI devel] RFC: Add "virbr0" to [btl|oob]_tcp_if_exclude?

On Feb 10, 2012, at 1:44 PM, Paul H. Hargrove wrote: > Since the situation described is one where the user didn't know they > could/should disable xen, it is reasonable to think they ALSO don't know they > need to exclude virbr0. That's what I'm thinking. > So, I read the question as

Re: [hwloc-devel] 1.3.2rc1 failures w/ icc on x86 (visibility?)

Committed to v1.3. On Feb 10, 2012, at 2:30 PM, Paul H. Hargrove wrote: > > > On 2/10/2012 11:19 AM, Jeff Squyres wrote: >> I'll go compare. > > I already did... > > > HWLOC (1.3.2rc1) tries: >AC_LINK_IFELSE([AC_LANG_PROGRAM([[ >

Re: [hwloc-devel] 1.3.2rc1 failures w/ icc on x86 (visibility?)

On 2/10/2012 11:19 AM, Jeff Squyres wrote: I'll go compare. I already did... HWLOC (1.3.2rc1) tries: AC_LINK_IFELSE([AC_LANG_PROGRAM([[ __attribute__((visibility("default"))) int foo; ]],[[int i;]])], [],

Re: [hwloc-devel] 1.3.2rc1 has escaped

Coolio. Thanks. On Feb 10, 2012, at 2:16 PM, Paul H. Hargrove wrote: > > > On 2/10/2012 11:00 AM, Jeff Squyres wrote: >> Here's the final logic -- is it what you intended? > > Yes, that works for me. > I pasted you version into config/hwloc.m4 on 1.3.2rc1 and faked the > $hwloc_c_vendor

Re: [hwloc-devel] 1.3.2rc1 failures w/ icc on x86 (visibility?)

On Feb 10, 2012, at 2:09 PM, Paul H. Hargrove wrote: >> It's kinda weird that icc supported the visibility stuff but gcc did not... > > See my post that crossed yours in flight. > The configure logic in ompi thinks icc does NOT support visibility on this > platform. > I think ompi is a touch

Re: [hwloc-devel] 1.3.2rc1 has escaped

On 2/10/2012 11:00 AM, Jeff Squyres wrote: Here's the final logic -- is it what you intended? Yes, that works for me. I pasted you version into config/hwloc.m4 on 1.3.2rc1 and faked the $hwloc_c_vendor setting. The results were the same as with my version. (Yes, I did autoreconf to make

Re: [hwloc-devel] 1.3.2rc1 failures w/ icc on x86 (visibility?)

On 2/10/2012 11:04 AM, Jeff Squyres wrote: It's kinda weird that icc supported the visibility stuff but gcc did not... See my post that crossed yours in flight. The configure logic in ompi thinks icc does NOT support visibility on this platform. I think ompi is a touch smarter than hwloc

Re: [hwloc-devel] 1.3.2rc1 failures w/ icc on x86 (visibility?)

On 2/10/2012 9:27 AM, Paul H. Hargrove wrote: I have versions 8.1.032, 9.0.024 and 9.1.042 of the Intel compilers on a Linux/x86 (32-bit) host. All three can configure and build hwloc-1.3.2rc1, but all are failing "make check" in the same way. What I see is ton(ne)s of linker messages and

Re: [hwloc-devel] 1.3.2rc1 failures w/ icc on x86 (visibility?)

What does nm say about libhwloc.so? Are those symbols public or private? Was everything properly built as 32 bit? It's kinda weird that icc supported the visibility stuff but gcc did not... On Feb 10, 2012, at 12:27 PM, Paul H. Hargrove wrote: > > I have versions 8.1.032, 9.0.024 and

Re: [hwloc-devel] 1.3.2rc1 has escaped

On Feb 9, 2012, at 5:38 PM, Paul H. Hargrove wrote: >> We then test if *either* set the variable. >> Sort of a double-negative. > > One of De Morgan's Laws: >NOT (A AND B) = (NOT A) OR (NOT B) > > Applied to give: >NOT (TEST1_FAIL AND TEST2_FAIL) > = (NOT TEST1_FAIL) OR (NOT

Re: [OMPI devel] RFC: Add "virbr0" to [btl|oob]_tcp_if_exclude?

On 2/10/2012 10:38 AM, Jeff Squyres wrote: On Feb 10, 2012, at 1:00 PM, TERRY DONTJE wrote: >> Should we add "virbr0" to the default value for [btl|oob]_tcp_if_exclude? >> > What happens to that value if you then set btl_tcp_if_exclude to some value on the mpirun command line? It

Re: [OMPI devel] RFC: Add "virbr0" to [btl|oob]_tcp_if_exclude?

On Feb 10, 2012, at 1:00 PM, TERRY DONTJE wrote: >> Should we add "virbr0" to the default value for [btl|oob]_tcp_if_exclude? >> > What happens to that value if you then set btl_tcp_if_exclude to some value > on the mpirun command line? It works just fine. I.e., if you mpirun --mca

Re: [OMPI devel] RFC: Add "virbr0" to [btl|oob]_tcp_if_exclude?

On 2/10/2012 11:50 AM, Jeff Squyres wrote: This is an open question to OMPI developers... It looks like RHEL (and maybe others?) adds the "virbr0" IP interface when Xen is activated. This IP interface is only used to communicate with the local Xen instance(s); it is not used to communicate

Re: [OMPI devel] RFC: Add "virbr0" to [btl|oob]_tcp_if_exclude?

On Feb 10, 2012, at 9:50 AM, Jeff Squyres wrote: > This is an open question to OMPI developers... > > It looks like RHEL (and maybe others?) adds the "virbr0" IP interface when > Xen is activated. This IP interface is only used to communicate with the > local Xen instance(s); it is not used

[OMPI devel] RFC: Add "virbr0" to [btl|oob]_tcp_if_exclude?

This is an open question to OMPI developers... It looks like RHEL (and maybe others?) adds the "virbr0" IP interface when Xen is activated. This IP interface is only used to communicate with the local Xen instance(s); it is not used to communicate over the real network. In a case that I