4.8.8. Miscellaneous functionality
The following are command line options that don’t fit any any of the
above categories that can be used with
--without-memory-manager: Disable building Open MPI’s memory manager. Open MPI’s memory manager is usually built on Linux based platforms, and is generally only used for optimizations with some OpenFabrics-based networks (it is not necessary for OpenFabrics networks, but some performance loss may be observed without it).
Open MPI’s memory management functionality, which provides important performance optimizations on OS-bypass networks such as InfiniBand, requires the
dlsym(3)interface, and therefore does not work with fully-static applications.
--with-ft=TYPE: Specify the type of fault tolerance to enable. The only allowed values are
none. See the ULFM section for more details.
--enable-peruse: Enable the PERUSE MPI data analysis interface.
--enable-heterogeneous: Enable support for running on heterogeneous clusters (e.g., machines with different endian representations). Heterogeneous support is disabled by default because it imposes a minor performance penalty.
The heterogeneous functionality is currently broken — do not use.
--with-wrapper-libs=LIBS: Add the specified flags to the default flags that are used in Open MPI’s “wrapper” compilers (e.g.,
mpicc— see below for more information about Open MPI’s wrapper compilers). By default, Open MPI’s wrapper compilers use the same compilers used to build Open MPI and specify a minimum set of additional flags that are necessary to compile/link MPI applications. These configure options give system administrators the ability to embed additional flags in OMPI’s wrapper compilers (which is a local policy decision). The meanings of the different flags are:
CFLAGS: Flags passed by the
mpiccwrapper to the C compiler
CXXFLAGS: Flags passed by the
mpiCCwrappers to the C++ compiler
FCFLAGS: Flags passed by the
mpifortwrapper to the Fortran compiler
LDFLAGS: Flags passed by all the wrappers to the linker
LIBS: Flags passed by all the wrappers to the linker
See the section on customizing wrapper compiler behavior to see how to alter the wrapper compiler behavior at run time.