openmpi

Jeff Squyres ea13687547 Minor change to VT: use the "foreign" keyword with AM_INIT_AUTOMAKE so

that Automake doesn't assume that these are GNU standard packages
that conform to the GNU coding standards.  Without this keyword,
Automake can replace the VT INSTALL files with the GNU standard
INSTALL text file.

This change is ''necessary'' for the autogen improvements that are
coming shortly (see
http://www.open-mpi.org/community/lists/devel/2010/09/8478.php); I'm
committing this change ahead of time so that I can pass it upstream to
the VT developers.

This commit was SVN r23740.

2010-09-12 08:44:41 +00:00

libompitrace

Rename "libtrace" to be "libompitrace" so as not to conflict with an

2010-07-06 21:48:15 +00:00

Minor change to VT: use the "foreign" keyword with AM_INIT_AUTOMAKE so

2010-09-12 08:44:41 +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).