-
Notifications
You must be signed in to change notification settings - Fork 0
/
INSTALL
360 lines (245 loc) · 13.1 KB
/
INSTALL
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
How to install and configure VampirTrace
========================================
Basics
------
Building VampirTrace is typically a combination of running "configure"
and "make". Execute the following commands to install VampirTrace from
within the directory at the top of the tree:
$ ./configure --prefix=/where/to/install
[...lots of output...]
$ make all install
If you need special access to install, then you can execute "make
all" as a user with write permissions in the build tree, and a
separate "make install" as a user with write permissions to the
install tree.
However, for more details, read also the following instructions. Sometimes
it might be necessary to provide ./configure with options, e.g.
specifications of paths or compilers.
VampirTrace comes with example programs written in C, C++, and Fortran.
They can be used to test different instrumentation types of the
VampirTrace installation.
You can find them in the directory examples of the VampirTrace package.
Configure Options
-----------------
* Compilers and Options
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. Run `./configure --help'
for details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
* Installation Names
By default, `make install' will install the package's files in
`/usr/local/bin', /usr/local/include', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
* Optional Features
--enable-compinst=LIST
enable support for compiler instrumentation,
(gnu,intel,pathscale,pgi,sun,xl,ftrace,openuh)
A VampirTrace installation can handle different
compilers. The first item in the list is the
run-time default.
default: automatically by configure
--enable-dyninst
enable support for Dyninst instrumentation,
default: enable if found by configure
Note: Requires Dyninst version 5.1 or higher!
--enable-dyninst-attlib
build shared library which attaches Dyninst to
the running application, default: enable if
Dyninst found by configure and system supports
shared libraries
--enable-iotrace
enable LIBC's I/O tracing support, default: enable
if libdl found by configure
--enable-libctrace
enable tracing support for several LIBC functions,
default: enable if libdl found by configure
--enable-memtrace
enable memory tracing support, default: enable if
found by configure
--enable-cpuidtrace
enable CPU ID tracing support, default: enable if
found by configure
--enable-rutrace
enable resource usage tracing support, default:
enable if found by configure
--enable-metrics=TYPE
enable support for hardware performance counter
(papi,cpc,necsx), default: automatically by
configure
--enable-zlib
enable ZLIB trace compression support, default:
enable if found by configure
--enable-mpi
enable MPI support, default: enable if
MPI found by configure
--enable-fmpi-lib
build the MPI Fortran support library, in case your
system does not have a MPI Fortran library.
default: enable if no MPI Fortran library
found by configure
--enable-fmpi-handle-convert
do convert MPI handles, default: enable if MPI
conversion functions found by configure
--enable-mpi2-thread
enable MPI-2 Thread support, default: enable if
found by configure
--enable-mpi2-1sided
enable MPI-2 One-Sided Communication support,
default: enable if found by configure
--enable-mpi2-extcoll
enable MPI-2 Extended Collective Operation support,
default: enable if found by configure
--enable-mpi2-io
enable MPI-2 I/O support, default: enable if found
by configure
--enable-mpicheck
enable support for Universal MPI Correctness
Interface (UniMCI), default: enable if
unimci-config found by configure
--enable-etimesync
enable enhanced timer synchronization support,
default: enable if C-LAPACK found by configure
--enable-threads=LIST
enable support for threads (pthread, omp), default:
automatically by configure
--enable-java
enable Java support, default: enable if JVMTI
found by configure
* Important Optional Packages
This a summary of the most important optional features. For a full list
of all available features run `./configure --help'.
--with-platform=PLATFORM
configure for given platform
(altix,bgl,bgp,crayt3e,crayx1,crayxt,ibm,linux,
macos,necsx,origin,sicortex,sun,generic),
default: automatically by configure
--with-bitmode=<32|64>
specify bit mode
--with-options=FILE
load options from FILE, default: configure
searches for a config file in config/defaults
based on given platform and bitmode
--with-local-tmp-dir=DIR
give the path for node-local temporary directory,
default: /tmp
Specify name of (SMP) node-local directory that can be used to store
temporary trace files.
If you would like to use an external version of OTF library, set
--with-extern-otf
use external OTF library, default: not seta
--with-extern-otf-dir=OTFDIR
give the path for OTF, default: /usr
--with-otf-flags=FLAGS
pass FLAGS to the OTF distribution configuration
(only for internal OTF version)
--with-otf-lib=OTFLIB
use given otf lib, default: -lotf -lz
If used OTF library was built without zlib support, then it will do
to set OTFLIB to '-lotf'.
--with-dyninst-dir=DYNIDIR
give the path for DYNINST, default: /usr
--with-papi-dir=PAPIDIR
give the path for PAPI, default: /usr
--with-cpc-dir=CPCDIR
give the path for CPC, default: /usr
If you don't have specified the environment variable MPICC
(MPI compiler command), use following options to set location
of your MPI installation:
--with-mpi-dir=MPIDIR
give the path for MPI, default: /usr
--with-mpi-inc-dir=MPIINCDIR
give the path for MPI-include-files, default:
MPIDIR/include
--with-mpi-lib-dir=MPILIBDIR
give the path for MPI-libraries, default:
MPIDIR/lib
--with-mpi-lib
use given mpi lib
--with-pmpi-lib
use given pmpi lib
If your system does not have a MPI Fortran library,
set '--enable-fmpi-lib' (see above), otherwise set
--with-fmpi-lib
use given fmpi lib
Use the following options to specify your MPI-implementation
--with-hpmpi set MPI-libs for HP MPI
--with-intelmpi set MPI-libs for Intel MPI
--with-intelmpi2 set MPI-libs for Intel MPI2
--with-lam set MPI-libs for LAM/MPI
--with-mpibgl set MPI-libs for IBM BG/L
--with-mpibgp set MPI-libs for IBM BG/P
--with-mpich set MPI-libs for MPICH
--with-mpich2 set MPI-libs for MPICH2
--with-mvapich set MPI-libs for MVAPICH
--with-mvapich2 set MPI-libs for MVAPICH2
--with-mpisx set MPI-libs for NEC MPI/SX
--with-mpisx-ew set MPI-libs for NEC MPI/SX with
8 Byte Fortran Integer
--with-openmpi set MPI-libs for Open MPI
--with-sgimpt set MPI-libs for SGI MPT
--with-sunmpi set MPI-libs for SUN MPI
--with-sunmpi-mt set MPI-libs for SUN MPI-MT
To enable enhanced timer synchronization a LAPACK library with C wrapper
support is needed:
--with-clapack-dir=LAPACKDIR
set the path for CLAPACK,
default: /usr
--with-clapack-lib
set CLAPACK-libs, default:
-lclapack -lcblas -lf2c
--with-clapack-acml set CLAPACK-libs for ACML
--with-clapack-essl set CLAPACK-libs for ESSL
--with-clapack-mkl set CLAPACK-libs for MKL
--with-clapack-sunperf set CLAPACK-libs for SUN Performance Library
To enable Java support the JVM Tool Interface (JVMTI) version 1.0 or
higher is needed:
--with-jvmti-dir=JVMTIDIR
give the path for JVMTI, default: JAVA_HOME
--with-jvmti-inc-dir=JVMTIINCDIR
give the path for JVMTI-include files, default:
JVMTI/include
Cross Compilation
-----------------
Building VampirTrace on cross compilation platforms needs some special attention.
The compiler wrappers, OPARI, and the Library Wrapper Generator are built for the
front-end (build system) whereas the VampirTrace libraries, vtdyn, vtunify, and
vtfilter are built for the back-end (host system). Some configure options which are
of interest for cross compilation are shown below:
* Set CC, CXX, F77, and FC to the cross compilers installed on the front-end.
* Set CC_FOR_BUILD and CXX_FOR_BUILD to the native compilers of the front-end.
* Set --host= to the output of config.guess on the back-end.
* Set --with-cross-prefix= to a prefix which will be prepended to the executables
of the compiler wrappers and OPARI (default: cross-)
* Maybe you also need to set additional commands and flags for the back-end
(e.g. RANLIB, AR, MPICC, CXXFLAGS).
For example, this configure command line works for an NEC SX6 system with an X86_64
based front-end:
./configure CC=sxcc CXX=sxc++ F77=sxf90 FC=sxf90 MPICC=sxmpicc
AR=sxar RANLIB="sxar st" CC_FOR_BUILD=cc CXX_FOR_BUILD=c++
--host=sx6-nec-superux14.1
--with-cross-prefix=sx
--with-otf-lib=-lotf
Set up the Environment
----------------------
Add the bin subdirectory of the installation directory to your PATH
environment variable. To use VampirTrace with Dyninst, you will also need
to add the lib subdirectory to your LD_LIBRARY_PATH environment variable:
for csh and tcsh:
> setenv PATH <vampirtrace-install>/bin:$PATH
> setenv LD_LIBRARY_PATH <vampirtrace-install>/lib:$LD_LIBRARY_PATH
for bash and sh:
$ export PATH=<vampirtrace-install>/bin:$PATH
$ export LD_LIBRARY_PATH=<vampirtrace-install>/lib:$LD_LIBRARY_PATH
Notes for Developers
--------------------
* Build from CVS
If you have checked out a DEVELOPER'S COPY of VampirTrace (i.e. you
checked out from CVS), you should first run:
$ ./bootstrap [--otf-package <package>] [--version <version>]
Note that GNU Autoconf >= 2.60 and GNU Automake >= 1.9.6 is required.
You can download them from http://www.gnu.org/software/autoconf and
http://www.gnu.org/software/automake.