openmpi

Matthias Jurenz 03ea0245f0 Changes to OTF: - general: - corrected OTF version number - otfprofile: - removed leading '=' from CSV lines to make it loadable into spreadsheets (e.g. Open Office) - fixed process naming in CSV output of collective operation statistics Changes to VT: - configure: - added *_FOR_BUILD variables to CrayXE's default configure options; required for cross-building - VT libs: - fixed GPU communication, due to new process ID splitting - fixed parsing of PAPI native events in VT_METRICS; use strtok_r instead of strtok which is successively called inPAPI_event_name_to_code - added VT_METRICS_SEP to definition comments (-> Vampir's trace info) - Docu: - fixed link to TAU Reference Guide This commit was SVN r26137.		2012-03-14 12:36:28 +00:00
..
libompitrace	WARNING: Work on the temp branch being merged here encountered problems with bugs in subversion. Considerable effort has gone into validating the branch. However, not all conditions can be checked, so users are cautioned that it may be advisable to not update from the trunk for a few days to allow MTT to identify platform-specific issues.	2010-09-17 23:04:06 +00:00
vt	Changes to OTF:	2012-03-14 12:36:28 +00:00
README.txt	Update the text; it was left over from autogen.sh days (i.e., it had	2012-01-26 13:11:36 +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 a configure.m4.  It may optionally also
have an autogen.subdirs file.

If it has a configure.m4 file, it must specify its own relevant files
to AC_CONFIG_FILES to create during AC_OUTPUT -- just like MCA
components (at a minimum, usually its own Makefile).  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
-- it probably won't not be too difficult to extend autogen.pl to
support this scenario, similar to how it is done for MCA components.
:-)

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