PROBLEMS revision 104862
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---------------------------------------------------------------------- 6 7 8 9Generic Problems 10================ 11 12 13 14* My document says that the current year is 19100, not 2000. 15 16In groff, as in traditional troff, the yr number register yields the 17year minus 1900. Unfortunately, there is a longstanding bug in the 18Troff User's Manual <http://cm.bell-labs.com/cm/cs/cstr/54.ps.gz>, 19which incorrectly claims that yr is the last two digits of the year. 20This claim was never true of either Unix troff or of groff. 21 22If your text looks like this: 23 24 .\" Wrong: 25 This document was formatted in 19\n(yr. 26 27you can correct it as follows: 28 29 This document was formatted in \n[year]. 30 31or, if you want to be portable to older troff versions, as follows: 32 33 .nr y4 1900+\n(yr 34 This document was formatted in \n(y4. 35 36---------------------------------------------------------------------- 37 38* groff can't handle my troff document. It works fine with AT&T 39 troff. 40 41Read the section on incompatibilities in gtroff(1). Try using the -C 42option. Alternatively there's the sed script `tmac/fixmacros.sed' 43which will attempt to edit a file of macros so that it can be used 44with groff without the -C flag. 45 46---------------------------------------------------------------------- 47 48* gtroff doesn't understand lines like `.ce99' with no space between 49 the name of the request or macro and the arguments. 50 51gtroff requires a space between macro or request and its arguments 52because it allows the use of long names for macros and requests. You 53can use the -C option or the `cp' request to put gtroff into a 54compatibility mode in which it is not possible to use long names for 55macros but in which no space is required between macros and their 56arguments. The use of compatibility mode is strongly discouraged. 57 58---------------------------------------------------------------------- 59 60* groff -Tdvi produces dvi files that use fonts at weird 61 magnifications. 62 63Yes, it does. You may need to compile fonts with Metafont at these 64magnifications. The CompileFonts script in the devdvi/generate 65directory may help you to do this. (It will take a *long* time on 66slow computers.) 67 68---------------------------------------------------------------------- 69 70* Groff doesn't use the font names I'm used to. 71 72Use the `ftr' request. See (g)troff(1). 73 74---------------------------------------------------------------------- 75 76* pic output is not centered horizontally; pictures sometimes run off 77 the bottom of the page. 78 79The macro package you are using is not supplying appropriate 80definitions of PS and PE. Give groff a -mpic option. 81 82---------------------------------------------------------------------- 83 84* gpic doesn't accept the syntax `chop N M' for chopping both ends of 85 a line. 86 87The correct syntax is `chop N chop M'. 88 89---------------------------------------------------------------------- 90 91* With gpic -t, when I print `line ->; box' using a dvi to ps program, 92 the arrow head sticks through into the inside of the box. 93 94The dvi to ps program should be modified to set the line cap and line 95join parameters to 1 while printing tpic specials. 96 97---------------------------------------------------------------------- 98 99* gtroff gives warnings about lines like 100 .ev \" a comment 101 (with a tab after the .ev). 102 103A tab character cannot be used as a substitute for a space character 104(except in one case: between a control character at the beginning of a 105line and the name of a macro or request). For example, in Unix troff 106 107 .ps \" restore the previous point size 108 109(with a tab after the .ps) will NOT restore the previous point-size; 110instead it will be silently ignored. Since this is very likely to be 111an error, gtroff can give a warning about it. If you want to align 112comments, you can do it like this: 113 114 .ev\" \" a comment 115 116---------------------------------------------------------------------- 117 118* I don't like the page headers and footers produced by groff -man. 119 120There seem to be many different styles of page header and footer 121produced by different versions of the -man macros. You will need to 122modify tmac/an-old.tmac to suit your personal taste. For example, if 123you want the center of the page header to say 124 125 System Programmer's Manual 126 127you will need to change the line 128 129 .el .ds an-extra3 \"System Programmer's Manual 130 131to 132 133 .el .ds an-extra3 System Programmer's Manual 134 135---------------------------------------------------------------------- 136 137* Where can I get grap? 138 139Ted Faber <faber@lunabase.org> has written a freely available grap: 140 141 http://www.lunabase.org/~faber/Vault/software/grap/ 142 143---------------------------------------------------------------------- 144 145* The \n(st and \n(sb registers don't seem to work. I thought \w set 146 them to the height and depth of its argument, but the registers 147 always seem to be 0. 148 149\n(st and \n(sb aren't supposed to give the height and depth of the 150string rather they give the minimum and maximum vertical displacement 151of the baseline. For example for \v'2u'\v'-3u', \n(st will be 1 and 152\n(sb will be -2. The height and depth of the string is available in 153the \n[rst] and \n[rsb] registers: these are groff extensions. 154 155---------------------------------------------------------------------- 156 157* While formatting a manual page, groff complains about not being able 158 to break lines. The problem seems to be caused by a line like: 159 .TP \w'label'+2 160 161The -man documentation says that the default scale indicator for TP 162macro is `n'. The groff -man macros implement this correctly, so that 163the argument will be evaluated as if it were 164 165 \w'label'n+2n 166 167The Unix -man macros don't implement this correctly (probably because 168it's hard to do in Unix troff); they just append `n' to the entire 169argument, so that it will be evaluated as if it were 170 171 \w'label'u+2n 172 173The solution is to fix the manual page: 174 175 .TP \w'label'u+2 176 177---------------------------------------------------------------------- 178 179* I'm having problems formatting man pages produced by the perl 180 wrapman script. 181 182Some versions of wrapman have a superfluous blank line before the .TH 183line. This must be deleted. Then either use groff -C, or apply the 184following patch: 185 186*** wrapman.~2~ Sun Jan 19 12:10:24 1992 187--- wrapman Tue Aug 10 02:06:41 1993 188*************** 189*** 35,41 **** 190 $line1 .= <IN> if $line1 =~ /eval/; 191 $line1 .= <IN> if $line1 =~ /argv/; 192 $line2 = <IN>; 193! next if $line2 eq "'di';\n"; 194 195 # Pull the old switcheroo. 196 197--- 35,41 ---- 198 $line1 .= <IN> if $line1 =~ /eval/; 199 $line1 .= <IN> if $line1 =~ /argv/; 200 $line2 = <IN>; 201! next if $line2 eq "'di ';\n" || $line2 eq "'di';\n"; 202 203 # Pull the old switcheroo. 204 205*************** 206*** 49,56 **** 207 208 print OUT $line1; 209 print OUT <<EOF; 210! 'di'; 211! 'ig00'; 212 # 213 # $header 214 # 215--- 49,58 ---- 216 217 print OUT $line1; 218 print OUT <<EOF; 219! 'di '; 220! 'ds 00 \\"'; 221! 'eo '; 222! 'ig 00 '; 223 # 224 # $header 225 # 226*************** 227*** 72,85 **** 228 229 # These next few lines are legal in both Perl and nroff. 230 231! $null.00; # finish .ig 232 233 'di \\" finish diversion--previous line must be blank 234 .nr nl 0-1 \\" fake up transition to first page again 235 .nr % 0 \\" start at page 1 236! '; __END__ ##### From here on it's a standard manual page ##### 237 .TH $PROG 1 "$month $mday, 19$year" 238- .AT 3 239 .SH NAME 240 $prog \\- whatever 241 .SH SYNOPSIS 242--- 74,87 ---- 243 244 # These next few lines are legal in both Perl and nroff. 245 246! $null.00 ; # finish .ig 247! 'ec \\'; 248 249 'di \\" finish diversion--previous line must be blank 250 .nr nl 0-1 \\" fake up transition to first page again 251 .nr % 0 \\" start at page 1 252! .\\"'; __END__ ##### From here on it's a standard manual page ##### 253 .TH $PROG 1 "$month $mday, 19$year" 254 .SH NAME 255 $prog \\- whatever 256 .SH SYNOPSIS 257 258---------------------------------------------------------------------- 259 260* groff uses up an enormous amount of memory processing large files. 261 I'm using 386BSD 0.1. 262 263386BSD includes an old version of g++, 1.39, which has a bug that 264causes a major memory leak in gtroff. Apply the following fix to g++ 265and recompile groff: 266 267*** cplus-decl.c.~1~ Mon Aug 6 05:28:59 1990 268--- cplus-decl.c Wed Jun 5 08:55:04 1991 269*************** 270*** 7951,7961 **** 271 272 /* At the end, call delete if that's what's requested. */ 273 if (TREE_GETS_DELETE (current_class_type)) 274 exprstmt = build_method_call (build1 (NOP_EXPR, TYPE_POINTER_TO (current_class_type), error_mark_node), 275 get_identifier (OPERATOR_DELETE_FORMAT), 276! build_tree_list (NULL_TREE, integer_zero_node), 277 NULL_TREE, LOOKUP_NORMAL); 278 else if (TYPE_USES_VIRTUAL_BASECLASSES (current_class_type)) 279 exprstmt = build_x_delete (ptr_type_node, current_class_decl, 0); 280 else 281 exprstmt = 0; 282--- 7951,7961 ---- 283 284 /* At the end, call delete if that's what's requested. */ 285 if (TREE_GETS_DELETE (current_class_type)) 286 exprstmt = build_method_call (build1 (NOP_EXPR, TYPE_POINTER_TO (current_class_type), error_mark_node), 287 get_identifier (OPERATOR_DELETE_FORMAT), 288! build_tree_list (NULL_TREE, current_class_decl), 289 NULL_TREE, LOOKUP_NORMAL); 290 else if (TYPE_USES_VIRTUAL_BASECLASSES (current_class_type)) 291 exprstmt = build_x_delete (ptr_type_node, current_class_decl, 0); 292 else 293 exprstmt = 0; 294 295 296 297Printing and Display Problems 298============================= 299 300 301 302* I'm having problems including PostScript illustrations (EPS) using 303 the PSPIC macro and/or \X'ps: import ...'. 304 305A PostScript document must meet three requirements in order to be 306included with the PSPIC macro: it must comply with the Adobe Document 307Structuring Conventions; it must contain a BoundingBox line; it must 308be ``well-behaved''. The BoundingBox line should be of the form: 309 310 %%BoundingBox: llx lly urx ury 311 312where llx, lly, urx, ury are the coordinates of the lower left x, 313lower left y, upper right x, upper right y of the bounding box of 314marks on the page expressed as integers in the default PostScript 315coordinate system (72 units per inch, origin at bottom left corner). 316 317The most convenient program to get the bounding box of a document is 318the `ps2epsi' script coming with GhostScript. 319 320If you can't use this program, another useful tactic is to print out 321the illustration by itself (you may need to add a `showpage' at the 322end), and physically measure the bounding box. For more detail on 323these requirements, read the specification of Encapsulated PostScript 324format. (This is available from the Adobe file server; send a message 325with a body of `help' to ps-file-server@adobe.com.) 326 327If an EPS file to be included via \X'ps: import' does not start with 328%!PS-Adobe-...', gtroff will still include the file, but grops will 329not add any fonts to the generated output file that are listed in the 330EPS file, even though the files are listed in the `download' file and 331are available in the devps directory. 332 333---------------------------------------------------------------------- 334 335* I've configured groff for A4 paper, but gtroff still seems to think 336 that the length of a page (as returned by `\n(.p') is 11 inches. 337 338This is intentional. The PAGE option is used only by grops. For 339compatibility with ditroff, the default page length in gtroff is 340always 11 inches. The page length can be changed with the `pl' 341request. 342 343---------------------------------------------------------------------- 344 345* When I print the output groff -Tps, the output is always shifted up 346 by about 0.7 inches; I'm using 8.5x11 inch paper. 347 348Make sure that PAGE is defined to be `letter' in the top-level 349Makefile. 350 351---------------------------------------------------------------------- 352 353* When I try to run gxditview, I get the error: 354 Error: Widget viewport has zero width and/or height 355 356This error means you haven't correctly installed the application 357defaults file, GXditview.ad; ``make install'' does this for you 358automatically, so either you didn't do ``make install'', or you don't 359have imake configured correctly. 360 361---------------------------------------------------------------------- 362 363* When I preview documents using -TX75 or -TX100, the layout is not 364 the same as when I print the document with -Tps: the line and page 365 breaks come in different places. 366 367Use groff -X -Tps. 368 369---------------------------------------------------------------------- 370 371* When I try to print the output of groff -Tps, I get no output at all 372 from the printer, and the log file shows the error 373 %%[ error: undefined; offendingcommand: BP ]%% 374 I'm using TranScript spooling software. 375 376This is a bug in the page reversal filter in early versions of 377TranScript. Change the `broken' parameter in 378/usr/local/lib/groff/font/devps/DESC to 7. 379 380---------------------------------------------------------------------- 381 382* When I preview groff -Tps output using the Sun OpenWindows 2.0 383 pageview program, all the pages are displayed on top of each other. 384 385This is a defect in pageview. Change the `broken' parameter in 386/usr/local/lib/groff/font/devps/DESC to 2. 387 388---------------------------------------------------------------------- 389 390* With groff -TX75, -TX100 or -X, I can only view the first page. 391 392The left mouse button brings up a menu that allows you to view other 393pages. 394 395---------------------------------------------------------------------- 396 397* When I print the output of groff -Tdvi, I just get a black dot in 398 upper left corner. 399 400Some dvi drivers (notably early versions of xtex) do not correctly 401handle dvi files that use a resolution different from that used by dvi 402files produced by TeX. Try getting a more up to date driver. 403 404---------------------------------------------------------------------- 405 406* How can I use groff with an old LaserJet printer that doesn't work 407 with groff -Tlj4? 408 409You have at least 3 options: 410 411- use groff -Tps with GNU Ghostscript; 412 413- use groff -Tdvi with a TeX .dvi to Laserjet driver; 414 415- use groff with the LaserJet driver in Chris Lewis' psroff package 416 (available for ftp from: 417 ftp.uunet.ca:/distrib/chris_lewis/psroff3.0pl17). 418 419---------------------------------------------------------------------- 420 421* Groff seems to generate level 3 Postscript, but my printer is only a 422 level 1 or 2 PostScript printer. 423 424In fact groff generates only level 1 PostScript. The `%!PS-Adobe-3.0' 425comment at the beginning of PostScript output generated by groff 426indicates that the file conforms to version 3.0 of the Adobe Document 427Structuring Conventions. The output generated by groff should be 428printable on any PostScript printer. Problems with groff output's not 429printing are most often caused by the spooling system. 430 431 432 433Platform-Dependent Macro Problems 434================================= 435 436 437 438* I get lots of errors when I use groff with the AT&T -mm macros. 439 440Use the groff -mm macros. 441 442---------------------------------------------------------------------- 443 444* groff produces wrapper macros for `ms' and friends which call the 445 system's original macros. Then, to get groff's ms macro package I 446 have to use `-mgs' instead `-ms'. Can I avoid this? 447 448Yes. Configure and compile groff as usual, but install it with 449 450 make install tmac_wrap="" 451 452Then no wrapper files are produced, and `-ms' will use groff's `ms' 453macros. 454 455---------------------------------------------------------------------- 456 457* I'm having problems formatting HP-UX 9.0 man pages with groff -man. 458 459Copy HP's tmac.an into /usr/local/share/groff/site-tmac/an.tmac, and 460either put `.cp 1' at the beginning or filter it (and any files it 461.so's) through tmac/fixmacros.sed. 462 463---------------------------------------------------------------------- 464 465* I get errors using the Unix -ms macros with groff -e -C. 466 467Apply this change: 468 469*** /usr/lib/ms/ms.eqn Tue Apr 25 02:14:28 1989 470--- ms.eqn Sun Nov 11 10:33:59 1990 471*************** 472*** 22,29 **** 473 .. 474 . \" EN - end of a displayed equation 475 .de EN 476! .if !\\*(10 .br 477 .di 478 .rm EZ 479 .nr ZN \\n(dn 480 .if \\n(ZN>0 .if \\n(YE=0 .LP 481--- 22,30 ---- 482 .. 483 . \" EN - end of a displayed equation 484 .de EN 485! .if \\n(.k>0 .br 486 .di 487+ .ds 10 \\*(EZ\\ 488 .rm EZ 489 .nr ZN \\n(dn 490 .if \\n(ZN>0 .if \\n(YE=0 .LP 491 492---------------------------------------------------------------------- 493 494* I'm having problems formatting Ultrix man pages with groff -man. 495 496The Ultrix man pages use a number of non-standard extensions to the 497Unix man macros. One solution is to use the Ultrix -man macros with 498groff. Copy /usr/lib/tmac/tmac.an to 499/usr/local/share/groff/site-tmac/an.tmac and apply the following patch 500(from Frank Wortner): 501 502*** /usr/local/lib/groff/tmac/tmac.an Wed Sep 9 12:29:28 1992 503--- /usr/lib/tmac/tmac.an Fri Jul 24 19:58:19 1992 504*************** 505*** 489,495 **** 506 . \" make special case of shift out of italic 507 .de }S 508 .ds ]F 509! .if \\$12 .if !\\$5 .ds ]F \^ 510 .ie !\\$4 .}S \\$2 \\$1 "\\$3\f\\$1\\$4\\*(]F" "\\$5" "\\$6" "\\$7" "\\$8" "\\$9" 511 .el \\$3 512 .}f 513--- 489,495 ---- 514 . \" make special case of shift out of italic 515 .de }S 516 .ds ]F 517! .if \\$12 .if !\\$5 .ds ]F\^ 518 .ie !\\$4 .}S \\$2 \\$1 "\\$3\f\\$1\\$4\\*(]F" "\\$5" "\\$6" "\\$7" "\\$8" "\\$9" 519 .el \\$3 520 .}f 521 522Another possible solution is to install tmac/man.ultrix as 523/usr/local/share/groff/site-tmac/man.local. 524 525---------------------------------------------------------------------- 526 527* On an SGI system, how can I make the man command use groff? 528 529From David Hinds <dhinds@allegro.stanford.edu> (some of these steps 530are unnecessary if you install with the `g' Makefile variable defined 531as empty): 532 533Create a script called 'eqn': 534 535 > #!/bin/sh 536 > if [ ${1:-""} = /usr/pub/eqnchar ] ; then shift ; fi 537 > geqn $* 538 539and a script called 'neqn': 540 541 > #!/bin/sh 542 > if [ ${1:-""} = /usr/pub/eqnchar ] ; then shift ; fi 543 > geqn -Tascii $* 544 545and do: 546 547 > ln -s gnroff nroff 548 549and edit the end of the gnroff script to be: 550 551 > rest=`echo ${1+"$@"} | sed -e 's+/usr/lib/tmac+/usr/local/lib/groff/tmac+'` 552 > exec groff -Wall -mtty-char $T $opts $rest 553 554To get PostScript output from 'man -t', you also need to create a 555'psroff' script similar to 'nroff'. Here are the context diffs: 556 557*** /usr/local/bin/nroff Sat Feb 13 15:51:09 1993 558--- /usr/local/bin/psroff Sat Feb 13 17:45:46 1993 559*************** 560*** 1,8 **** 561 #!/bin/sh 562! # Emulate nroff with groff. 563 564 prog="$0" 565! T=-Tascii 566 opts= 567 568 for i 569--- 1,8 ---- 570 #!/bin/sh 571! # Emulate psroff with groff. 572 573 prog="$0" 574! T=-Tps 575 opts= 576 577 for i 578*************** 579*** 25,30 **** 580--- 25,33 ---- 581 -Tascii|-Tlatin1) 582 T=$1 583 ;; 584+ -t) 585+ # ignore -- default is send to stdout 586+ ;; 587 -T*) 588 # ignore other devices 589 ;; 590*************** 591*** 49,53 **** 592 rest=`echo ${1+"$@"} | sed -e 's+/usr/lib/tmac+/usr/local/lib/groff/tmac+'` 593 594 # This shell script is intended for use with man, so warnings are 595 # probably not wanted. Also load nroff-style character definitions. 596! exec groff -Wall -mtty-char $T $opts $rest 597--- 52,56 ---- 598 rest=`echo ${1+"$@"} | sed -e 's+/usr/lib/tmac+/usr/local/lib/groff/tmac+'` 599 600 # This shell script is intended for use with man, so warnings are 601! # probably not wanted. 602! exec groff -Wall $T $opts $rest 603 604 605 606Compilation Problems 607==================== 608 609 610 611* Compilation dies with 612 613 y.tab.c: In function `int yyparse()': 614 y.tab.c: `size_t' undeclared in namespace `std' 615 616This is a bug in bison 1.32. Don't use this version. 1.28 or 1.33 works 617fine. Alternatively, use yacc or byacc. 618 619---------------------------------------------------------------------- 620 621* There are many empty `Makefile.dep' files. Is this a bug? 622 623No. Real dependency files are created with a `make depend' call. 624 625---------------------------------------------------------------------- 626 627* On HP-UX, the compiler complains about missing symbol `alloca'. 628 629Say 630 631 export LDFLAGS=-lPW 632 633before starting the configure script. 634 635---------------------------------------------------------------------- 636 637* The configure script fails on OS/390 (z/OS) Unix. 638 639[This has been fixed in z/OS V1R3 (aka OS/390 R13).] 640 641There is a bug in the Language Environment (LE) whereby the test 642program for static destructors fails. You will see the message 643`configure: error: a working C++ compiler is required' 644 645Applying PTF UQ42006 is supposed to fix this, but the test program is 646still returning the wrong value (1). To work around this problem, you 647can comment out the following in the configure script (near line 2029). 648This will effectively bypass the test (static constructors and 649destructors do actually work properly): 650 651#if { (eval echo "$as_me:2029: \"$ac_link\"") >&5 652# (eval $ac_link) 2>&5 653# ac_status=$? 654# echo "$as_me:2032: \$? = $ac_status" >&5 655# (exit $ac_status); } && { ac_try='./conftest$ac_exeext' 656# { (eval echo "$as_me:2034: \"$ac_try\"") >&5 657# (eval $ac_try) 2>&5 658# ac_status=$? 659# echo "$as_me:2037: \$? = $ac_status" >&5 660# (exit $ac_status); }; }; then 661# echo "$as_me:2039: result: yes" >&5 662#echo "${ECHO_T}yes" >&6 663#else 664# echo "$as_me: program exited with status $ac_status" >&5 665#echo "$as_me: failed program was:" >&5 666#cat conftest.$ac_ext >&5 667#echo "$as_me:2045: result: no" >&5 668#echo "${ECHO_T}no" >&6;{ { echo "$as_me:2046: error: a working C++ compiler is required" >&5 669#echo "$as_me: error: a working C++ compiler is required" >&2;} 670# { (exit 1); exit 1; }; } 671#fi 672 673---------------------------------------------------------------------- 674 675* I get errors when I try to compile groff with DEC C++. 676 677Fix the declaration of write() in <unistd.h> so that the second 678argument is a const char *. Fix the declaration of open() in 679<sys/file.h> so that the first argument is a const char *. 680 681---------------------------------------------------------------------- 682 683* On a host using Unix make (e.g. Solaris), if you are compiling for 684 multiple architectures by building in a subdirectory, the make stops 685 with a message like this: 686 687 make: Fatal error: Don't know how to make target `assert.o' 688 689 or like this: 690 691 make: Fatal error: Can't find /u/src/groff/src/include/Makefile.sub': No such file or directory 692 693This occurs because GNU make and Unix make handle VPATH differently, 694and the groff build relies on GNU make's VPATH handling. 695 696Use GNU make to work around the problem. In Solaris 8, GNU make is 697on the Software Companion CD and is installed as /opt/sfw/bin/gmake. 698 699---------------------------------------------------------------------- 700 701* On Ultrix, the make stops with the message 702 703 *** Error code 1 704 705 Stop. 706 707 for no apparent reason. 708 709Use GNU make. 710 711---------------------------------------------------------------------- 712 713* I'm having problems compiling groff on 386BSD 0.1. 714 715If you're using ash as /bin/sh, you'll need the following patch. 716 717*** gendef.sh.org Sun Jun 30 13:30:36 1991 718--- gendef.sh Sun Feb 28 10:23:49 1993 719*************** 720*** 3,9 **** 721 file=$1 722 shift 723 724! defs="#define $1" 725 shift 726 for def 727 do 728--- 3,10 ---- 729 file=$1 730 shift 731 732! x=$1 733! defs="#define $x" 734 shift 735 for def 736 do 737 738You'll also need to change dirnamemax.c so that it doesn't use 739pathconf(). 740 741---------------------------------------------------------------------- 742 743* While compiling on Xenix, ranlib libgroff.a fails. 744 745The system ranlib can't handle externals longer than 40 characters. 746Use the ranlib included in demon.co.uk:/pub/xenix/g++-1.40.3a.v1 747instead. 748 749---------------------------------------------------------------------- 750 751* I get errors when I try to compile groff with Sun C++ version 3 or 752 earlier. 753 754Groff requires header files that are moderately compatible with AT&T 755C++ and ANSI C. With some versions of Sun C++, the supplied header 756files need some of the following changes to meet this requirement: 757<string.h> must declare the mem* functions, (just add `#include 758<memory.h>' to <string.h>); the first argument to fopen and freopen 759should be declared as `const char *'; the first argument to fread 760should be declared as `void *'; the first argument to fwrite should be 761declared as `const void *'; malloc should be declared to return 762`void *'; in <alloca.h>, the declaration `extern "C" { void 763*__builtin_alloca(int); }' should be added; in <sys/signal.h> the 764return type and the second argument type of signal() should be changed 765to be `void (*)(int)'. 766 767You can either change them in place, or copy them to some other 768directory and include that directory with a -I option. 769 770---------------------------------------------------------------------- 771 772* I get errors when I try to compile groff with Sun C++ version 5.0 773 or 5.1. 774 775This is a known problem; see Sun bug #4301919. As of this writing, no 776patch is available. Use GCC 2.95.2 or later instead. 777 778---------------------------------------------------------------------- 779 780* I get lots of `numeric overflow' error messages whenever I run 781 groff; I compiled groff with AT&T C++ 2.0 with an ANSI C compiler. 782 783Make sure -DCFRONT_ANSI_BUG is included in DEFINES in the top-level 784Makefile. If that doesn't solve the problem, define INT_MIN as 785-INT_MAX in libgroff/lib.h. 786