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 java behavior. On Jan 1, 2014, at 1:48 AM, Siegmar Gross <siegmar.gr...@informatik.hs-fulda.de> wrote: > I have similar problems with Java. > > tyr java 197 mpiexec -np 4 java BcastIntArrayMain > > Process 0 running on tyr.informatik.hs-fulda.de. > intValues[0]: 0 intValues[1]: 11 intValues[2]: 22 intValues[3]: 33 > > Process 1 running on tyr.informatik.hs-fulda.de. > intValues[0]: 0 intValues[1]: 11 intValues[2]: 22 intValues[3]: 33 > > Process 2 running on tyr.informatik.hs-fulda.de. > intValues[0]: 0 intValues[1]: 11 intValues[2]: 22 intValues[3]: 33 > > Process 3 running on tyr.informatik.hs-fulda.de. > intValues[0]: 0 intValues[1]: 11 intValues[2]: 22 intValues[3]: 33 > > > tyr java 198 mpiexec -np 4 -host rs0,tyr java BcastIntArrayMain > tyr java 199 echo $status > 1 > tyr java 200 > > > Why? Both machines are big endian machines. By the way, I have similar > problems with openmpi-1.7.x. Java isn't available at the moment as I > reported before.
