I have succesfully been using OpenMPI 1.8.3 compiled with Intel-14, using

./configure --prefix=/usr/local/mpi/$(basename $PWD) --with-threads=posix
--enable-mpi-thread-multiple --disable-vt --with-scif=no

I have now switched to Intel 15.0.1, and configuring with the same options,
I get minor changes in config.log about warning spotting, but it makes all
the binaries, and I can compile my own fortran code with mpif90/mpicc

but a command 'mpiexec --verbose -n 12 ./fortran_binary' does nothing

I checked the FAQ and started using

./configure --prefix=/usr/local/mpi/$(basename $PWD) --with-threads=posix
--enable-mpi-thread-multiple --disable-vt --with-scif=no CC=icc CXX=icpc
F77=ifort FC=ifort

but that makes no difference.

Only with -d do I get any more information

mpirun -d --verbose -n 12
/home/jbray/5.0/mic2/one/intel-15_openmpi-1.8.3/one_f_debug.exe
[mic2:21851] procdir: /tmp/openmpi-sessions-jbray@mic2_0/27642/0/0
[mic2:21851] jobdir: /tmp/openmpi-sessions-jbray@mic2_0/27642/0
[mic2:21851] top: openmpi-sessions-jbray@mic2_0
[mic2:21851] tmp: /tmp
[mic2:21851] sess_dir_cleanup: job session dir does not exist
[mic2:21851] procdir: /tmp/openmpi-sessions-jbray@mic2_0/27642/0/0
[mic2:21851] jobdir: /tmp/openmpi-sessions-jbray@mic2_0/27642/0
[mic2:21851] top: openmpi-sessions-jbray@mic2_0
[mic2:21851] tmp: /tmp
[mic2:21851] sess_dir_finalize: proc session dir does not exist
<12 times>


[mic2:21851] sess_dir_cleanup: job session dir does not exist
exiting with status 139

My C codes do not have this problem

Compiler options are

mpicxx -g -O0 -fno-inline-functions -openmp -o one_c_debug.exe async.c
collective.c compute.c memory.c one.c openmp.c p2p.c variables.c
auditmpi.c   control.c inout.c perfio.c ring.c wave.c io.c   leak.c mpiio.c
pthreads.c -openmp -lpthread

mpif90 -g -O0  -fno-inline-functions -openmp -o one_f_debug.exe control.o
io.f90 leak.f90 memory.f90 one.f90 ring.f90 slow.f90 swapbounds.f90
variables.f90 wave.f90 *.F90 -openmp

Any suggestions as to what is upsetting Fortran with Intel-15

John

Reply via email to