version 1.10, 2015/03/09 21:00:14 |
version 1.14, 2016/07/07 23:46:36 |
Line 42 generates. If anything looks wrong or different from |
|
Line 42 generates. If anything looks wrong or different from |
|
wish, read the file "configure.local.example", create and edit |
wish, read the file "configure.local.example", create and edit |
a file "configure.local", and re-run "./configure" until the |
a file "configure.local", and re-run "./configure" until the |
result seems right to you. |
result seems right to you. |
|
On Solaris 10 and earlier, you may have to run "ksh ./configure" |
|
because the native /bin/sh lacks some POSIX features. |
|
|
3. Run "make". |
3. Run "make". |
Any POSIX-compatible make, in particular both BSD make and GNU make, |
Any POSIX-compatible make, in particular both BSD make and GNU make, |
Line 50 and go back to step 2. |
|
Line 52 and go back to step 2. |
|
|
|
4. Run "make -n install" and check whether everything will be |
4. Run "make -n install" and check whether everything will be |
installed to the intended places. Otherwise, put some *DIR or *NM* |
installed to the intended places. Otherwise, put some *DIR or *NM* |
variables into "configure.local" and go back to step 2. |
variables into "configure.local" and go back to step 2. |
|
|
5. Run "sudo make install". If you intend to build a binary |
5. Run "sudo make install". If you intend to build a binary |
package using some kind of fake root mechanism, you may need a |
package using some kind of fake root mechanism, you may need a |
Line 61 in the "Makefile" to understand how DESTDIR is used. |
|
Line 63 in the "Makefile" to understand how DESTDIR is used. |
|
manpath(1), make sure it is configured correctly, in particular, |
manpath(1), make sure it is configured correctly, in particular, |
it returns all directory trees where manual pages are installed. |
it returns all directory trees where manual pages are installed. |
Otherwise, if your system uses man.conf(5), make sure it contains |
Otherwise, if your system uses man.conf(5), make sure it contains |
a "_whatdb" line for each directory tree, and the order of these |
a "manpath" line for each directory tree, and the order of these |
lines meets your wishes. |
lines meets your wishes. |
|
|
7. If you compiled with database support, run the command "sudo |
7. If you compiled with database support, run the command "sudo |
Line 82 manual page source. |
|
Line 84 manual page source. |
|
|
|
Understanding mandoc dependencies |
Understanding mandoc dependencies |
--------------------------------- |
--------------------------------- |
The mandoc(1), man(1), and demandoc(1) utilities have no external |
The mandoc(1), man(1), and demandoc(1) utilities only depend |
dependencies, but makewhatis(8) and apropos(1) depend on the |
on the zlib library for decompressing gzipped manual pages, |
following software: |
but makewhatis(8) and apropos(1) depend on the following |
|
additional software: |
|
|
1. The SQLite database system, see <http://sqlite.org/>. |
1. The SQLite database system, see <http://sqlite.org/>. |
The recommended version of SQLite is 3.8.4.3 or newer. The mandoc |
The recommended version of SQLite is 3.8.4.3 or newer. The mandoc |
Line 106 If you run into that problem, set "HAVE_FTS=0" in conf |
|
Line 109 If you run into that problem, set "HAVE_FTS=0" in conf |
|
3. Marc Espie's ohash(3) library. |
3. Marc Espie's ohash(3) library. |
If your system does not have it, the bundled compatibility version |
If your system does not have it, the bundled compatibility version |
will be used, so you probably need not worry about it. |
will be used, so you probably need not worry about it. |
|
|
|
One of the chief design goals of the mandoc toolbox is to make |
|
sure that nothing related to documentation requires C++. |
|
Consequently, linking mandoc against any kind of C++ program |
|
would defeat the purpose and is not supported. |
|
|
|
|
Checking autoconfiguration quality |
Checking autoconfiguration quality |