INSTALL revision 18099
118099SpstTo install groff, follow the instructions in the file INSTALL.gen. 218099Spst 318099SpstThis file contains information that supplements those instructions. 418099Spst 518099Spstgroff is written in C++, so you will need a C++ compiler. The C++ 618099Spstsource files use a suffix of `.cc', so your C++ compiler must be able 718099Spstto handle this. If you don't already have a C++ compiler, I suggest 818099Spstgcc 2.7.1 or later (gcc version 2 includes GNU C++ as well as GNU C). 918099SpstFrom gcc 2.5, it is no longer necessary to install libg++: the C++ 1018099Spstheader files needed by groff are created by the gcc installation 1118099Spstprocess. To override configure's choice of C++ compiler, you can set 1218099Spstthe CXX environment variable. 1318099Spst 1418099SpstIf you have a library that provides a faster malloc than your system's 1518099Spstusual malloc, it is good idea to include it in LIBS. For example, 1618099Spstusing the malloc that comes with GNU Emacs version 18 can give a 1718099Spstworthwhile (and sometimes spectacular) performance improvement. 1818099Spst 1918099SpstWhen you have build groff, you can use the test-groff script to try 2018099Spstgroff out on one of the man pages. (Use the .n files not the .man 2118099Spstfiles.) The test-groff script sets up environment variables to allow 2218099Spstgroff to run without being installed. The current directory must be 2318099Spstthe build directory when the script is run. For example, you could do 2418099Spst 2518099Spst ./test-groff -man -Tascii groff/groff.n | less 2618099Spst 2718099SpstIf you want to install gxditview (an X11 previewer), follow the 2818099Spstinstructions in the INSTALL file in the xditview directory. 2918099Spst 3018099SpstIf you have problems, read the PROBLEMS file. If this doesn't help 3118099Spstsend a bug report using the form in the file BUG-REPORT. 32