openmpi

Matthias Jurenz f32aab5137 Changes to VT:

- configure:
		- patch Makefiles which define library targets that depend on other libraries to prevent the following Libtool warning:
		  "libtool: link: warning: `...//*.la' seems to be moved"
		  (Libtool getting confused by the "//" in the library paths,
		  so remove the trailing '/' from all *LIBDIR variables.)
	- vtwrapper:
		- added options '-vt:showme-<compile|link>' to the compiler wrapper to show the compiler/linker flags that would be supplied to the underlying compiler

This commit was SVN r25105.

2011-08-29 15:43:17 +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:

2011-08-29 15:43:17 +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).