On Jan 28, 2014, at 2:18 PM, Orion Poplawski <or...@cora.nwra.com> wrote:
> Why does mpio.h get installed? For the Fedora package I end up with: > > /usr/lib64/openmpi/include/mpio.h > > but it is listed here in openmpi-1.7.4rc2/ompi/mca/io/romio/romio/Makefile.am: > > # nodist_ b/c these are created by config.status and should not be distributed > nodist_include_HEADERS += include/mpio.h > noinst_HEADERS += include/io_romio_conv.h > > Confusion between nodist/noinst? We define --includedir to be > /usr/include/openmpi-x86_64 so if it should be installed it should be > installed there. I don't think there's any confusion. This is just the way that ROMIO comes from upstream (the MPICH distribution). The MPICH mpi.h file includes mpio.h by name, necessitating its installation: http://git.mpich.org/mpich.git/blob/HEAD:/src/include/mpi.h.in#l2159 http://git.mpich.org/mpich.git/blob/HEAD:/confdb/aclocal_mpi.m4#l509 ----8<---- $ cat -n mpi.h | grep -C4 'include "mpio.h"' 2141 #define MPIIMPL_HAVE_MPI_GREQUEST 1 2142 #define MPIIMPL_HAVE_STATUS_SET_BYTES 1 2143 #define MPIIMPL_HAVE_STATUS_SET_INFO 1 2144 2145 #include "mpio.h" 2146 2147 #if defined(__cplusplus) 2148 } 2149 /* Add the C++ bindings */ ----8<---- IIRC, OMPI does not need this to be installed, so we could probably modify that Makefile.am to use noinst. -Dave
