INSTALL revision 69626 
1To install groff, follow the instructions in the file INSTALL.gen.
2
3This file contains information that supplements those instructions.
4
5(For instructions how to build groff with DJGPP tools for MS-DOS and
6MS-Windows, see the file arch/djgpp/README.)
7
8groff is written in C++, so you will need a C++ compiler.  The C++
9source files use a suffix of `.cc', so your C++ compiler must be able
10to handle this.  If you don't already have a C++ compiler, I suggest
11gcc 2.7.1 or later (gcc version 2 includes GNU C++ as well as GNU C).
12From gcc 2.5, it is no longer necessary to install libg++: the C++
13header files needed by groff are created by the gcc installation
14process.  To override configure's choice of C++ compiler, you can set
15the CXX environment variable.
16
17If you have a library that provides a faster malloc than your system's
18usual malloc, it is good idea to include it in LIBS.  For example,
19using the malloc that comes with GNU Emacs version 20 can give a
20worthwhile (and sometimes spectacular) performance improvement.
21
22When you have built groff, you can use the test-groff script to try
23groff out on one of the man pages.  (Use the .n files not the .man
24files.)  The test-groff script sets up environment variables to allow
25groff to run without being installed.  The current directory must be
26the build directory when the script is run.  For example, you could do
27
28  ./test-groff -man -Tascii src/roff/groff/groff.n | less
29
30If you want to compile and install gxditview (an X11 previewer),
31follow the instructions in the INSTALL file in the src/xditview
32subdirectory.
33
34To get PostScript versions of the documentation resp. reference files
35for the `me' macros and the `pic' preprocessor, simply say `make' in
36the `doc' subdirectory.
37
38If you have problems, read the PROBLEMS file.  If this doesn't help
39send a bug report using the form in the file BUG-REPORT.
40