openmpi

Matthias Jurenz 00fd159d02 Changes to VT:

- configure:
		- fixed passing FCFLAGS to the Fortran compiler when building libvt-fmpi
		- temporary disabled memory allocation tracing for multi-threaded applications (introduced in v5.14.1) due to broken counter values when memory is freed in a different thread than where it was allocated
		- do not build the unification library when building with HP/Platform MPI (needs linking libmpiCC, even if the C++ MPI interface isn't used)
		- removed 'libfmpi' from list of MPI Fortran libraries to be searched (causes that 'libvt-fmpi' will be built when configuring for HP/Platform MPI)
		- do not build the MPI Fortran library 'libvt-fmpi' when building VT inside Open MPI
	- Java tracing:
		- minor performance improvment: call vt_java_check_error (now vt_java_error) only if a JVMTI function returns an error

This commit was SVN r28228.

2013-03-27 10:04:33 +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-27 10:04:33 +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).