| PROBLEMS (18099) | PROBLEMS (55839) |
|---|---|
| 1This file describes various problems that have been encountered in 2compiling, installing and running groff. Suggestions for additions or 3other improvements to this file are welcome. 4 5* I get lots of `numeric overflow' error messages whenever I run 6groff; I compiled groff with AT&T C++ 2.0 with an ANSI C compiler. 7 8Make sure -DCFRONT_ANSI_BUG is included in DEFINES in the top-level 9Makefile. If that doesn't solve the problem, define INT_MIN as 10-INT_MAX in libgroff/lib.h. 11 | 1This file describes various problems that have been encountered in 2compiling, installing and running groff. Suggestions for additions or 3other improvements to this file are welcome. 4 5* I get lots of `numeric overflow' error messages whenever I run 6groff; I compiled groff with AT&T C++ 2.0 with an ANSI C compiler. 7 8Make sure -DCFRONT_ANSI_BUG is included in DEFINES in the top-level 9Makefile. If that doesn't solve the problem, define INT_MIN as 10-INT_MAX in libgroff/lib.h. 11 |
| 12* I get errors when I try to compile groff with Sun C++ version 5.0 or 5.1. 13 14This is a known problem; see Sun bug #4301919. As of this writing, no 15patch is available. Use GCC 2.95.2 or later instead. 16 |
|
| 12* I get errors when I try to compile groff with Sun C++ version 3 or 13earlier. 14 15Groff requires header files that are moderately compatible with AT&T 16C++ and ANSI C. With some versions of Sun C++, the supplied header 17files need some of the following changes to meet this requirement: 18<string.h> must declare the mem* functions, (just add `#include 19<memory.h>' to <string.h>); the first argument to fopen and freopen --- 154 unchanged lines hidden (view full) --- 174by about 0.7 inches; I'm using 8.5x11 inch paper. 175 176Make sure that PAGE is defined to be `letter' in the top-level 177Makefile. 178 179* When I try to print the output of groff -Tps, I get no output at all 180from the printer, and the log file shows the error 181%%[ error: undefined; offendingcommand: BP ]%% | 17* I get errors when I try to compile groff with Sun C++ version 3 or 18earlier. 19 20Groff requires header files that are moderately compatible with AT&T 21C++ and ANSI C. With some versions of Sun C++, the supplied header 22files need some of the following changes to meet this requirement: 23<string.h> must declare the mem* functions, (just add `#include 24<memory.h>' to <string.h>); the first argument to fopen and freopen --- 154 unchanged lines hidden (view full) --- 179by about 0.7 inches; I'm using 8.5x11 inch paper. 180 181Make sure that PAGE is defined to be `letter' in the top-level 182Makefile. 183 184* When I try to print the output of groff -Tps, I get no output at all 185from the printer, and the log file shows the error 186%%[ error: undefined; offendingcommand: BP ]%% |
| 182I using TranScript spooling software. | 187I'm using TranScript spooling software. |
| 183 184This is a bug in the page reversal filter in early versions of 185TranScript. Change the `broken' parameter in 186/usr/local/lib/groff/font/devps/DESC to 7. 187 188* When I preview groff -Tps output using the Sun OpenWindows 2.0 pageview 189program, all the pages are displayed on top of each other. 190 191This is a defect in pageview. Change the `broken' parameter in 192/usr/local/lib/groff/font/devps/DESC to 2. 193 | 188 189This is a bug in the page reversal filter in early versions of 190TranScript. Change the `broken' parameter in 191/usr/local/lib/groff/font/devps/DESC to 7. 192 193* When I preview groff -Tps output using the Sun OpenWindows 2.0 pageview 194program, all the pages are displayed on top of each other. 195 196This is a defect in pageview. Change the `broken' parameter in 197/usr/local/lib/groff/font/devps/DESC to 2. 198 |
| 194* With groff -TX75, -TX100or -X, I can only view the first page. | 199* With groff -TX75, -TX100 or -X, I can only view the first page. |
| 195 196The left mouse button brings up a menu that allows you to view other 197pages. 198 199* When I print the output of groff -Tdvi, I just get a black dot in 200upper left corner. 201 202Some dvi drivers (notably early versions of xtex) do not correctly --- 33 unchanged lines hidden (view full) --- 236 .ev\" \" a comment 237 238* I don't like the page headers and footers produced by groff -man. 239 240There seem to be many different styles of page header and footer 241produced by different versions of the -man macros. You will need to 242modify macros/tmac.an to suit your personal taste. For example, if 243you want the center of the page header to say | 200 201The left mouse button brings up a menu that allows you to view other 202pages. 203 204* When I print the output of groff -Tdvi, I just get a black dot in 205upper left corner. 206 207Some dvi drivers (notably early versions of xtex) do not correctly --- 33 unchanged lines hidden (view full) --- 241 .ev\" \" a comment 242 243* I don't like the page headers and footers produced by groff -man. 244 245There seem to be many different styles of page header and footer 246produced by different versions of the -man macros. You will need to 247modify macros/tmac.an to suit your personal taste. For example, if 248you want the center of the page header to say |
| 244 UNIX Programmer's Manual | 249 System Programmer's Manual |
| 245you will need to change the line | 250you will need to change the line |
| 246 .el .ds an-extra3 \"UNIX Programmer's Manual | 251 .el .ds an-extra3 \"System Programmer's Manual |
| 247to | 252to |
| 248 .el .ds an-extra3 UNIX Programmer's Manual | 253 .el .ds an-extra3 System Programmer's Manual |
| 249 250* While formatting a manual page, groff complains about not being able to 251break lines. The problem seems to be caused by a line like: 252 .TP \w'label'+2 253 254The -man documentation says that the default scale indicator for TP 255macro is `n'. The groff -man macros implement this correctly, so that 256the argument will be evaluated as if it were --- 292 unchanged lines hidden --- | 254 255* While formatting a manual page, groff complains about not being able to 256break lines. The problem seems to be caused by a line like: 257 .TP \w'label'+2 258 259The -man documentation says that the default scale indicator for TP 260macro is `n'. The groff -man macros implement this correctly, so that 261the argument will be evaluated as if it were --- 292 unchanged lines hidden --- |