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