File: INSTALL.md

package info (click to toggle)
dmtcp 2.6.0-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 6,496 kB
  • sloc: cpp: 33,592; ansic: 28,099; sh: 6,735; makefile: 1,950; perl: 1,690; python: 1,241; asm: 138; java: 13
file content (74 lines) | stat: -rw-r--r-- 2,194 bytes parent folder | download
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
## Installing DMTCP

### Prerequisites

### Build instructions

To build, use:
```
  ./configure
  make
  make check [Optional]
```

As usual, you may prefer to use `make` with `'-j'` for faster, parallel builds.

`make check2`, and `make check3` will exercise further examples in the
test subdirectory:
```
  check2: readline.c
  check3: shared-memory.c
```

This software runs in the original directory, and
```
  make install
```
will install to the install directory based on configure.

Distribution packages for Debian/Ubuntu, OpenSUSE and Fedora are available in their respective repositories.

### Multilib support
To support multilib (mixed use of 32- and 64-bit applications),
there are two possibilities:
1.  Install both the 32- and 64-bit versions of DMTCP packages for your distro.
OR:
2.  Build from source:
```bash
  ./configure
  make
  # Do NOT do 'make clean' here.  You will lose bin/dmtcp_launch, etc.
  ./configure --enable-m32
  make clean   # This won't remove the 64-bit binary and library files.
  make
  # Optionally, change 'make' to 'make install'' if desired.
```

When running DMTCP with multilib support, the 64-bit applicationss,
```
  dmtcp_launch, dmtcp_restart, and dmtcp_command
```
all inter-operate with both 32- and 64-bit applications.

If your process will create multiple processes, you should use standard DMTCP.
A brief overview follows.
The general methodology is:
```
  ./dmtcp_coordinator #in one window: type h to the coordinator to see commands
  ./dmtcp_launch a.out <args,...>
```

Note that files `/tmp/${USER}/dmtcp-${USER}@${HOST}/jassertlog.*` are created
with debugging information if you configured with `--enable-debug`.
See `./configure --help` for that and other options.

See the file [QUICK-START.md](QUICK-START.md) for further information on using DMTCP.


## Running without a separate coordinator process:

Usually, the most convenient procedure is to use DMTCP in its
default mode, which includes a separate DMTCP coordinator process.
In some rare cases, you may wish to avoid a separate coordinator process by
providing a `--no-coordinator` flag to `dmtcp_launch`. Multiprocess
computations are not supported with this flag.