9f9fded4de
- otfprofile: fixed build error when using the IBM XL C++ compiler Changes to VT: - configure: - use AC_CHECK_TYPES instead of AC_CHECK_DECLS to check for PAPI's long_long type - use AC_C_INLINE to check whether C 'inline' is present - VT libs: - set CUPTI tracing as default, if CUDA runtime wrapper has not been built - added a common interface for all NVIDIA CUPTI interfaces (events, activity, callbacks) - added support for concurrent kernel tracing (since CUDA 5.0) - removed almost unused VT_DEBUG env. variable - replaced calls to vt_debug_msg(DBG_LEVEL,...) by vt_cntl_msg (DBG_LEVEL+10,...) - added some more ifdefs to new CUDA 5 features - added several guards for internal malloc() and free() calls in CUDA related source files - revised memory allocation tracing: - intercept memory (de)alloaction functions by library wrapping (replaces deprecated hook technique from the GNU C library) - added support for multi-threaded applications - added wrapper functions for memalign, posix_memalign, and valloc - revised exec,system,fork tracing - retitled to "Child Process Execution Tracing" - introduced env. variable VT_EXECTRACE (marked VT_LIBCTRACE as deprecated) - added wrapper functions for execvpe, fexecve, waitid, wait3, and wait4 - changes default function group name for - memory (de)allocation functions: "MEM" -> "LIBC-MALLOC" - I/O functions: "I/O" -> "LIBC-I/O" - child process execution: "LIBC" -> "LIBC-EXEC" - plugin counter interface: - added check for initialized vt_plugin_cntr_info.info - vtdyn: - added missing header includes for Dyninst 8 - vtrun: - do not preload the Dyninst Runtime library; it is loaded by Dyninst itself This commit was SVN r27679.
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).