
- general: - incremented version number to 1.12.3 - updated copyright information (2012->2013) - fixed compiler warnings occurred when NDEBUG is defined (--with-platform=optimized) - otfprofile, LaTeX output: - swapped x & y axis of the Message Data Rate Matrix - adapted labels to Vampir Changes to VT: - general: - incremented version number to 5.14.3 - updated copyright information (2012->2013) - fixed compiler warnings occurred when NDEBUG is defined (--with-platform=optimized) - configure / build system: - do not search for the MPI lib. when an MPI compiler wrapper was found (prevents double linkage of the MPI lib. when building vtunify-mpi and vtfilter-mpi) - prepend cross-prefix to the compiler wrappers *only* if '--with-cross-prefix[=PREFIX]' is given - removed unnecessary sources from libvt-java - VT libs: - extended inoffical API for manual region tracing: allow specifying a group name - plugin counters: Merge a set of post-mortem counters and write them under a single async key. This speeds up the unification. - Java tracing: - removed multiple asking for the current thread id when recording method enter/leave events - replaced hash function (id % prime) by Jenking's recommended one ( id & (hash_table_size-1) ) - vtdyn: Do not instrument regions where inserting instrumentation would requires using a trap - vtsetup: Fixed availability state of the exec tracing feature This commit was SVN r28162.
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).