I comfirmed openmpi-1.8.2rc3 with PGI-14.7 worked fine for me
except for the openib issue reported by Mike Dubman.
Tetsuya Mishima
> Sorry, finally got through all this ompi email and see this problem was
fixed.
>
> -Original Message-
> From: devel [mailto:devel-boun...@open-mpi.org]
Kewl - the openib issue has been fixed in the nightly tarball. I'm waiting for
review of a couple of pending CMRs, then we'll release a quick rc4 and move to
release the final version
On Aug 1, 2014, at 9:55 PM, tmish...@jcity.maeda.co.jp wrote:
>
>
> I comfirmed openmpi-1.8.2rc3 with
Hi Ralph,
I comfirmed that the openib issue was really fixed by r32395
and hope you'll be able to release the final version soon.
Tetsuya
> Kewl - the openib issue has been fixed in the nightly tarball. I'm
waiting for review of a couple of pending CMRs, then we'll release a quick
rc4 and
Good suggestion, Paul - I have committed it in r32407 and added it to cmr #4826
Thanks!
Ralph
On Aug 1, 2014, at 1:12 AM, Paul Hargrove wrote:
> Gilles,
>
> At the moment ompi/mca/osc/sm/osc_sm_component.c is using the following:
>
> #ifdef HAVE_GETPAGESIZE
>
This was apparently somewhat recent - here is the OpenBSD ticket regarding it:
http://sourceforge.net/p/levent/bugs/320/
If someone feels it important that we continue supporting OpenBSD, one might
explore the solution recommended in that ticket. It's also possible that the
libevent guys are
Ralph,
My position on support for OpenBSD is the same as the numerous other
operating systems, cpu architectures and compilers I help test on. I feel
that every additional platform for which one can maintain support improves
the chance of catching bugs in ones code and reduces the effort to port
I was just in Trak to open a new ticket and noticed that the Version
pull-down lacks entries for 1.8 and 1.8.1.
-Paul
--
Paul H. Hargrove phhargr...@lbl.gov
Future Technologies Group
Computer and Data Sciences Department Tel: +1-510-495-2352
Lawrence Berkeley
To be clear, I fully support what you say. Ordinarily, I would just do the
port, but sadly (a) I am totally buried at work right now, and (b) I have no
way to verify that the patches actually work.
If/when you have time, do let me know the results and I'll be happy to proceed.
Thanks
Ralph
Yeah, we remove back entries as we aren't going to backport patches to old
releases.
On Aug 2, 2014, at 12:59 PM, Paul Hargrove wrote:
> I was just in Trak to open a new ticket and noticed that the Version
> pull-down lacks entries for 1.8 and 1.8.1.
>
> -Paul
>
> --
>
Ralph,
I understand that I am likely the only one in a position to test.
I have already completed initial testing of the approach in the bug report
you fount at sourceforge: excise the sole *unused* routine that calls
arc4random_addrandom().
Assuming the remainder of my testing is successful, I
Not sure I understood that reply.
I see Version going back to 1.0, but none for the *current* release series.
Is that really the intent?
-Paul
On Sat, Aug 2, 2014 at 2:11 PM, Ralph Castain wrote:
> Yeah, we remove back entries as we aren't going to backport patches to old
Hmmm...I'll check with Jeff next week. I'm not sure why we would support
creation of tickets for releases that we know we'll never fix
On Aug 2, 2014, at 2:26 PM, Paul Hargrove wrote:
> Not sure I understood that reply.
>
> I see Version going back to 1.0, but none for
I'm more concerned with the INABILITY to file bug reports against the
current release.
One can pick "1.8 branch" but not 1.8 or 1.8.1.
-Paul
On Sat, Aug 2, 2014 at 2:33 PM, Ralph Castain wrote:
> Hmmm...I'll check with Jeff next week. I'm not sure why we would support
>
Creating nightly hwloc snapshot git tarball was a success.
Snapshot: hwloc dev-180-g16b88a7
Start time: Sat Aug 2 21:01:01 EDT 2014
End time: Sat Aug 2 21:02:28 EDT 2014
Your friendly daemon,
Cyrador
14 matches
Mail list logo