I can't replicate these problems - I tried both the current trunk and v1.7
branches. All appears to be in order. The Java support compiles without error,
and mpijavac appears and functions as it should.
What system are you using? Here's what I have:
Linux bend001 2.6.32-358.18.1.el6.x86_64 #1 S
On 02/11/2013 09:51 AM, Stefan Mauerberger wrote:
Hi Everyone!
Playing around with MPI_FILE_READ() puzzles me a little. To catch all
errors I set the error-handler - the one which is related to file I/O -
to MPI_ERRORS_ARE_FATAL.
However, when reading from a file which has not the necessary size
Hi,
I'm currently trying to get the included java bindings running but as I've
mentioned in a previous post I've had some problems.
./configure --prefix=/opt/openmpi-1.9-java --without-openib --enable-static
--with-threads=posix --enable-mpi-thread-multiple --enable-mpi-java
--with-jdk-bindir=/us
Further information.
I first time encountered this problem in openmpi-1.7.4.x,
while opnempi-1.7.3 and 1.6.x works fine.
My directory below is "testbed-openmpi-1.7.3", but it's realy
1.7.4a1r29646. I'm sorry, if I confuse you.
[mishima@manage testbed-openmpi-1.7.3]$ ompi_info | grep "Open MPI:
Indeed it should - most puzzling. I'll try playing with it on slurm using
sbatch and see if I get the same behavior. Offhand, I can't see why the
difference would exist unless somehow the script itself is taking one of the
execution slots, and somehow Torque is accounting for it.
Will have to e
