openmpi

Matthias Jurenz f7822df9b8 VT configure fixes: - patch libtool.m4 to fix detection of PGI 10 C++ compiler - patch configure to fix detection of PGI 10 Fortran compiler (pgfortran) - checks for MPI: - do only check Fortran interoperability if F77 compiler given - do not enable MPI-2 I/O support for LAM/MPI - added configure checks for PMPI_Win_<lock\|unlock\|test>, because in LAM-MPI these functions are missing - checks for LIBC-I/O tracing: - pass ldd's stderr output to /dev/null VT source fixes: - fixed detection of unique node id on MacOS platforms (use sysctl instead of gethostid) - fixed yet another Coverity warning - fixed compiler warnings on MacOS This commit was SVN r22508.		2010-01-28 15:36:51 +00:00
..
libtrace	Add a new contrib area for "libtrace" - a debugger library that outputs the name of the called MPI function plus the value of all its arguments before passing them along to the corresonding PMPI call.	2009-08-20 04:36:20 +00:00
vt	VT configure fixes:	2010-01-28 15:36:51 +00:00
README.txt	Add a new contrib area for "libtrace" - a debugger library that outputs the name of the called MPI function plus the value of all its arguments before passing them along to the corresonding PMPI call.	2009-08-20 04:36:20 +00:00

README.txt

This is the OMPI contrib system.  It is (far) less functional and
flexible than the OMPI MCA framework/component system.

Each contrib package must have either both a configure.params and a
configure.m4 file, or it must have an autogen.subdirs file.

If it has (configure.params, configure.m4), configure.params can be
just like any MCA component's: specify a list of files to create
during AC_OUTPUT.  The configure.m4 file will be slurped up into the
main configure script, just like other MCA components.  Note that
there is currently no "no configure" option for contrib packages --
you *must* have a configure.m4 (even if all it does it call $1).
Feel free to fix this situation if you want -- see:

    https://svn.open-mpi.org/trac/ompi/ticket/1162

:-)

If it has an autogen.subdirs file, then it needs to be a subdirectory
that is autogen-able (see the vt project for an example).