On Feb 13, 2014, at 7:30 PM, Ralph Castain wrote:
> Hmmm...well, a little digging says that we probably didn't do this as
> thoroughly as we should have :-/
Actually, it works exactly as we designed it... but the reasons for doing so
(and its effects) are a bit obscure.
Hmmm...well, a little digging says that we probably didn't do this as
thoroughly as we should have :-/
Basically, the "MPI I/O Support" line is tied solely to the disable-mpi-io
flag. In the 1.6 series, you only had one option for MPI I/O support, and that
was romio. So if you disable romio,
Why does ompi_info -c say "MPI I/O Support: yes" even though I configured using
-disable-io-romio? If ompi_info is going to tell me MPI I/O is supported, then
shouldn't I expect my test program (attached) to work correctly? (it doesn't).
I didn't disable "built-in" mpi-io, only io-romio.