Re: [OMPI users] some problems with openmpi-1.9a1r30100

2014-01-06 Thread Jeff Squyres (jsquyres)
Oscar and Siegmar have both asked for this before, and I haven't done it yet. :-( I just filed a ticket for it: https://svn.open-mpi.org/trac/ompi/ticket/4054 On Jan 1, 2014, at 10:57 AM, Ralph Castain wrote: > I believe that the Javadoc doesn't install by default - Jeff? > > On Jan 1,

Re: [OMPI users] some problems with openmpi-1.9a1r30100

2014-01-02 Thread Ralph Castain
I restored the -bycore option, but that isn't what you want here. Setting aside the behavior of the 1.6 series, which I believe is incorrect, when you tell us to map "bycore" we will map each process to one core. Thus, all four of your processes will be mapped onto linpc0 in your command line s

Re: [OMPI users] some problems with openmpi-1.9a1r30100

2014-01-01 Thread Ralph Castain
The fix to build Java hasn't moved to 1.7 yet - waiting for Jeff to return from vacation to review it. Per your prior note about mpiexec hanging on Sparc, there is no reason why the Java bindings would alter that situation. So the problem is the same, and I won't create a new ticket for the jav

Re: [OMPI users] some problems with openmpi-1.9a1r30100

2014-01-01 Thread Ralph Castain
-bycore should still be available for backward compatibility, so I'll check that one. I'll have to look to see what your binding pattern didn't work https://svn.open-mpi.org/trac/ompi/ticket/4044 On Jan 1, 2014, at 1:48 AM, Siegmar Gross wrote: > > Option "-bycore" isn't available any longe

Re: [OMPI users] some problems with openmpi-1.9a1r30100

2014-01-01 Thread Ralph Castain
I believe that the Javadoc doesn't install by default - Jeff? On Jan 1, 2014, at 1:48 AM, Siegmar Gross wrote: > "make install" didn't install the Javadoc documentation for the > new Java interface. Is it necessary to install it in a separate > step? > > tyr small_prog 118 ls -l /usr/local/ope