Lines Matching +full:re +full:- +full:run
4 --------------------------------------
25 ------------
37 run the command "echo BUILD_CGI=1 >> configure.local".
38 Then run "cp cgi.h.example cgi.h" and edit cgi.h as desired.
40 2. If you also want to build the catman(8) utility, run the
42 is unlikely to be a drop-in replacement providing the same
50 4. Run "./configure".
55 a file "configure.local", and re-run "./configure" until the
58 5. Run "make".
59 Any POSIX-compatible make, in particular both BSD make and GNU make,
63 6. Run "make -n install" and check whether everything will be
67 7. Optionally run the regression suite.
69 run, running all tests. For more fine-grained control,
70 read "./mandoc -l regress/regress.pl.1",
71 then run "cd regress && ./regress.pl" with optional arguments.
73 Examples of systems that are too old to run the regression suite
75 On Solaris 11, the suite does run, but some tests fail;
78 8. Run "sudo make install". If you intend to build a binary
80 command like "make DESTDIR=... install". Read the *-install targets
83 9. Run the command "sudo makewhatis" to build mandoc.db(5) databases
85 new manual pages, re-run makewhatis(8) to update the databases, or
90 Note that a very small number of man(7) pages contain low-level
92 systems using mandoc, third-party software is vetted on whether it
94 dependency and used to install pre-formatted "catpages" instead of
101 ---------------------------------
111 That was presumably fixed in glibc-2.23.
112 If you run into that problem, set "HAVE_FTS=0" in configure.local.
125 ----------------------------------
134 to reasonably modern POSIX-compliant tools rather than asking for
135 autoconf-style workarounds.
137 As far as mandoc is using any features not mandated by ANSI X3.159-1989
138 ("ANSI C") or IEEE Std 1003.1-2008 ("POSIX") that some modern systems
142 we do not slavishly restrict ourselves to POSIX-only interfaces.
143 For improved security and readability, we do use well-designed,
155 1. Run "make distclean".
157 2. Run "./configure"