None of the ncap2 stuff is MPI enabled right now, so this sounds perfectly fine. Hopefully, when/if ncap2 becomes mpi-enabled, I can figure out how to add it back for --enable-mpi.
-Daniel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm assuming that building ncap2 with MPI is not a requirement at this stage?
Reason for asking is that configure has to skip it if you ask for building for MPI.
Currently, --enable-mpi causes configure to emit an INFO line and skips the nco++ dir.
hjm
None of the ncap2 stuff is MPI enabled right now, so this sounds perfectly fine. Hopefully, when/if ncap2 becomes mpi-enabled, I can figure out how to add it back for --enable-mpi.
-Daniel
In the configure.in look for the following line and follow the directions :)
Daniel, just delete the following 3 lines when ncap2 is MPI-ready