openmpi

Matthias Jurenz e0844f3a40 - enforced creating of event/summary files even process/thread doesn't produce trace data (reworked r23550) - append "vampirtrace" to ${datarootdir} and ${includedir} even the options '--includedir' and '--datarootdir' are specified (this is meaningful for the creation of the Open MPI distribution packages) - disable OpenMP support in otfprofile if the PGI compiler is used to work around the following errors: compiler version compiler error < 9.0-3 PGCC-S-0000-Internal compiler error. calc_dw_tag:no tag (see Technical Problem Report 4337 at http://www.pgroup.com/support/release_tprs_90.htm) 10.1 - 10.6 this kind of pragma may not be used here #pargma omp barrier This commit was SVN r23564. The following SVN revision numbers were found above: r23550 --> open-mpi/ompi@3ef374478f		2010-08-06 12:47:40 +00:00
..
libompitrace	Rename "libtrace" to be "libompitrace" so as not to conflict with an	2010-07-06 21:48:15 +00:00
vt	- enforced creating of event/summary files even process/thread doesn't produce trace data	2010-08-06 12:47:40 +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).