openmpi

Matthias Jurenz cf926da7e1 Changes to VT:

- configure: VPATH building: Moved adding of -I$top_srcdir to CPPFLAGS to the end of configure to prevent using this flags for configure checks
	- VT libs: Fixed potential segmentation fault (infinite recursion) when writing intermediate statistics (VT_STAT_INTV != 0)
	- vtunify: Fixed header include to disable OpenMP in the library version of vtunify (libvt-mpi-unify)
	- fixed several Coverity warnings

This commit was SVN r28187.

2013-03-20 15:22:21 +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

Changes to VT:

2013-03-20 15:22:21 +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).