| … | |
… | |
| 47 | Running `configure' takes awhile. While running, it prints some |
47 | Running `configure' takes awhile. While running, it prints some |
| 48 | messages telling which features it is checking for. |
48 | messages telling which features it is checking for. |
| 49 | |
49 | |
| 50 | 2. Type `make' to compile the package. |
50 | 2. Type `make' to compile the package. |
| 51 | |
51 | |
| 52 | 3. Optionally, type `make check' to run any self-tests that come with |
|
|
| 53 | the package. |
|
|
| 54 | |
|
|
| 55 | 4. Type `make install' to install the programs and any data files and |
52 | 3. Type `make install' to install the programs and any data files and |
| 56 | documentation. |
53 | documentation. |
| 57 | |
54 | |
| 58 | 5. You can remove the program binaries and object files from the |
55 | 4. You can remove the program binaries and object files from the |
| 59 | source code directory by typing `make clean'. To also remove the |
56 | source code directory by typing `make clean'. To also remove the |
| 60 | files that `configure' created (so you can compile the package for |
57 | files that `configure' created (so you can compile the package for |
| 61 | a different kind of computer), type `make distclean'. There is |
58 | a different kind of computer), type `make distclean'. There is |
| 62 | also a `make maintainer-clean' target, but that is intended mainly |
59 | also a `make maintainer-clean' target, but that is intended mainly |
| 63 | for the package's developers. If you use it, you may have to get |
60 | for the package's developers. If you use it, you may have to get |
