- Updated date in copyright header of each source file
VT configure fixes:
- fixed configure's version detection for PAPI to support version 4.x
- added configure tests to detect Bull MPICH2
VT new features:
- added support for "re-locate" an existing VampirTrace? installation without re-build it from source (fixes OMPI's ticket #1990)
- added support for tracing functions in shared libraries instrumented by the GNU, Intel, Pathscale, ot PGI 9 compiler
- added support for PAPI-C counters which belong to different components
- extended usability of environment variable VT_METRICS for PAPI counters to specifiy whether a counter provides increasing or absolute values
This commit was SVN r22637.
- patch libtool.m4 to fix detection of PGI 10 C++ compiler
- patch configure to fix detection of PGI 10 Fortran compiler (pgfortran)
- checks for MPI:
- do only check Fortran interoperability if F77 compiler given
- do not enable MPI-2 I/O support for LAM/MPI
- added configure checks for PMPI_Win_<lock|unlock|test>, because in LAM-MPI these functions are missing
- checks for LIBC-I/O tracing:
- pass ldd's stderr output to /dev/null
VT source fixes:
- fixed detection of unique node id on MacOS platforms (use sysctl instead of gethostid)
- fixed yet another Coverity warning
- fixed compiler warnings on MacOS
This commit was SVN r22508.
- set configure variable 'inside_openmpi' to "no", if hidden argument '--with-openmpi-inside' not given
- added functions 'MPI_Group_range_<incl|excl>' to Fortran MPI wrappers
- updated default configure options for NECSX, BlueGene/L+P
- repaired tools/opari/doc/lacsi01.pdf
- fixed several Coverity warnings
This commit was SVN r22476.
- added support for shared libraries inside Open MPI
- hidden configure option '--with-openmpi-inside'
- do not show config titles/summary if configuring inside Open MPI
This commit was SVN r22440.
- removed tools/opari/doc/lacsi01.ps.gz which is equivalent to tools/opari/doc/lacsi01.pdf
- corrected svn:mime-type of tools/opari/doc/opari-logo-100.gif
This commit was SVN r22267.
use the new Automake "silent rules" if available.
If you are using an Automake prior to v1.11, you won't see the new
silent rules -- it will automatically default back to the "verbose"
rules.
Note, too, that even with these changes, you can enable the verbose
"make all" output in one of two ways:
1. Add "V=1" to your "make" command line
{{{
shell$ make all V=1
}}}
2. Add "--disable-silent-rules" to your "configure" command line:
{{{
shell$ ./configure --disable-silent-rules ...
}}}
The one down side of using the silent rules by default is that we'll
get less diagnostic information when users send their build logs. I
think we should update the web page to request that users send build
logs of "make V=1", but I'm guessing that not everyone will do it.
Note that I did ''not'' silent-ize the libltdl build (which is a dozen
or so files in the beginning of the build) because we wholly import
libltdl at autogen time. I therefore didn't want to patch libltdl
(further) after importing it a) to remain as forward- compatible as
possible, and b) patching the imported libltdl build system might be
tricky in terms of timestamps / dependencies. So those dozen-or-so
files will still be "verbose", but the rest of the files in OMPI will
be "silent".
This commit was SVN r22189.
Continue the reorganization of the configure system. Move files from the main config directory to their appropriate level-specific config directories. Modify the configure system to correctly handle compiler detection, test, and setup so that all things pertaining to opal and orte are done at the lower level, with the ompi configure system only looking at mpi-specific options.
Ensure the wrapper compilers for orte and ompi only get built when appropriate. Add support for c++ to the orte wrapper compilers, both script and non-script versions.
This commit was SVN r22138.
- reduced list of supported MPI implementations to Open MPI
(changed meaning of configure option '--with-openmpi': this option indicates an Open MPI internal build)
- updated version number of integrated VT to 5.4.10
This commit was SVN r21679.
(also usable to check validation of a trace)
- removed OTF python bindings
(a working version of the OTF python bindings are available in the latest stand-alone release;
see http://www.tu-dresden.de/zih/otf/)
- incremented OTF version number
This commit was SVN r21601.
