openmpi

Matthias Jurenz 1ce37bc5ce VT general:

- Updated date in copyright header of each source file
VT configure fixes:
- fixed configure's version detection for PAPI to support version 4.x
- added configure tests to detect Bull MPICH2
VT new features:
- added support for "re-locate" an existing VampirTrace? installation without re-build it from source (fixes OMPI's ticket #1990)
- added support for tracing functions in shared libraries instrumented by the GNU, Intel, Pathscale, ot PGI 9 compiler
- added support for PAPI-C counters which belong to different components
- extended usability of environment variable VT_METRICS for PAPI counters to specifiy whether a counter provides increasing or absolute values

This commit was SVN r22637.

2010-02-17 14:38:11 +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 general:

2010-02-17 14:38:11 +00:00

README.txt

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).