Talked to Nathan and he concurs with your proposed fix, so I'll add it only to
v1.7 (leaving trunk alone)
Thanks Paul!
On Mar 19, 2014, at 9:40 PM, Paul Hargrove wrote:
> Sorry to be the bearer of bad news...
>
> I configured on an SGI Altix UV with only "--enable-debug --enable-static
> --p
You may have noticed that some of the SVN and Trac mails were delayed
yesterday, sometimes by a few hours.
IU had some email difficulties yesterday; they have been fixed. The backlog is
likely cleared out by now, but a few more may trickle in over the course of
today.
--
Jeff Squyres
jsquy..
No, it builds by default on 1.7.5 - if we see too many issues, then we'll turn
it off unless requested
On Mar 19, 2014, at 10:31 PM, Paul Hargrove wrote:
> Maybe I misunderstood, but I though it had been decided 1.7.5 was *not* going
> to build oshmem by default. If I am mistaken, then feel f
Maybe I misunderstood, but I though it had been decided 1.7.5 was *not*
going to build oshmem by default. If I am mistaken, then feel free to
ignore the rest of this post.
Though I don't configure with any options which mention oshmem, I still see
(known as ticket #4262) failures linking the oshm
Sorry to be the bearer of bad news...
I configured on an SGI Altix UV with only "--enable-debug --enable-static
--prefix=..."
The configure script found the sn/xpmem.h header and threfore enabled
btl:vader:
--- MCA component btl:vader (m4 configuration macro)
checking for MCA component btl:vader
