PROBLEMS revision 114402
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 groff_diff(7). Try using 42the -C option. Alternatively there's the sed script 43`tmac/fixmacros.sed' which will attempt to edit a file of macros so 44that it can be used with 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 groff_diff(7). 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 122put modified macros from tmac/an-old.tmac into man.local. More 123information is available in groff_man(7). 124 125---------------------------------------------------------------------- 126 127* Where can I get grap? 128 129Ted Faber <faber@lunabase.org> has written a freely available grap: 130 131 http://www.lunabase.org/~faber/Vault/software/grap/ 132 133---------------------------------------------------------------------- 134 135* The \n(st and \n(sb registers don't seem to work. I thought \w set 136 them to the height and depth of its argument, but the registers 137 always seem to be 0. 138 139\n(st and \n(sb aren't supposed to give the height and depth of the 140string rather they give the minimum and maximum vertical displacement 141of the baseline. For example for \v'2u'\v'-3u', \n(st will be 1 and 142\n(sb will be -2. The height and depth of the string is available in 143the \n[rst] and \n[rsb] registers: these are groff extensions. 144 145---------------------------------------------------------------------- 146 147* While formatting a manual page, groff complains about not being able 148 to break lines. The problem seems to be caused by a line like: 149 .TP \w'label'+2 150 151The -man documentation says that the default scale indicator for TP 152macro is `n'. The groff -man macros implement this correctly, so that 153the argument will be evaluated as if it were 154 155 \w'label'n+2n 156 157The Unix -man macros don't implement this correctly (probably because 158it's hard to do in Unix troff); they just append `n' to the entire 159argument, so that it will be evaluated as if it were 160 161 \w'label'u+2n 162 163The solution is to fix the manual page: 164 165 .TP \w'label'u+2 166 167---------------------------------------------------------------------- 168 169* I'm having problems formatting man pages produced by the perl 170 wrapman script. 171 172Some versions of wrapman have a superfluous blank line before the .TH 173line. This must be deleted. Then either use groff -C, or apply the 174following patch: 175 176*** wrapman.~2~ Sun Jan 19 12:10:24 1992 177--- wrapman Tue Aug 10 02:06:41 1993 178*************** 179*** 35,41 **** 180 $line1 .= <IN> if $line1 =~ /eval/; 181 $line1 .= <IN> if $line1 =~ /argv/; 182 $line2 = <IN>; 183! next if $line2 eq "'di';\n"; 184 185 # Pull the old switcheroo. 186 187--- 35,41 ---- 188 $line1 .= <IN> if $line1 =~ /eval/; 189 $line1 .= <IN> if $line1 =~ /argv/; 190 $line2 = <IN>; 191! next if $line2 eq "'di ';\n" || $line2 eq "'di';\n"; 192 193 # Pull the old switcheroo. 194 195*************** 196*** 49,56 **** 197 198 print OUT $line1; 199 print OUT <<EOF; 200! 'di'; 201! 'ig00'; 202 # 203 # $header 204 # 205--- 49,58 ---- 206 207 print OUT $line1; 208 print OUT <<EOF; 209! 'di '; 210! 'ds 00 \\"'; 211! 'eo '; 212! 'ig 00 '; 213 # 214 # $header 215 # 216*************** 217*** 72,85 **** 218 219 # These next few lines are legal in both Perl and nroff. 220 221! $null.00; # finish .ig 222 223 'di \\" finish diversion--previous line must be blank 224 .nr nl 0-1 \\" fake up transition to first page again 225 .nr % 0 \\" start at page 1 226! '; __END__ ##### From here on it's a standard manual page ##### 227 .TH $PROG 1 "$month $mday, 19$year" 228- .AT 3 229 .SH NAME 230 $prog \\- whatever 231 .SH SYNOPSIS 232--- 74,87 ---- 233 234 # These next few lines are legal in both Perl and nroff. 235 236! $null.00 ; # finish .ig 237! 'ec \\'; 238 239 'di \\" finish diversion--previous line must be blank 240 .nr nl 0-1 \\" fake up transition to first page again 241 .nr % 0 \\" start at page 1 242! .\\"'; __END__ ##### From here on it's a standard manual page ##### 243 .TH $PROG 1 "$month $mday, 19$year" 244 .SH NAME 245 $prog \\- whatever 246 .SH SYNOPSIS 247 248---------------------------------------------------------------------- 249 250* groff uses up an enormous amount of memory processing large files. 251 I'm using 386BSD 0.1. 252 253386BSD includes an old version of g++, 1.39, which has a bug that 254causes a major memory leak in gtroff. Apply the following fix to g++ 255and recompile groff: 256 257*** cplus-decl.c.~1~ Mon Aug 6 05:28:59 1990 258--- cplus-decl.c Wed Jun 5 08:55:04 1991 259*************** 260*** 7951,7961 **** 261 262 /* At the end, call delete if that's what's requested. */ 263 if (TREE_GETS_DELETE (current_class_type)) 264 exprstmt = build_method_call (build1 (NOP_EXPR, TYPE_POINTER_TO (current_class_type), error_mark_node), 265 get_identifier (OPERATOR_DELETE_FORMAT), 266! build_tree_list (NULL_TREE, integer_zero_node), 267 NULL_TREE, LOOKUP_NORMAL); 268 else if (TYPE_USES_VIRTUAL_BASECLASSES (current_class_type)) 269 exprstmt = build_x_delete (ptr_type_node, current_class_decl, 0); 270 else 271 exprstmt = 0; 272--- 7951,7961 ---- 273 274 /* At the end, call delete if that's what's requested. */ 275 if (TREE_GETS_DELETE (current_class_type)) 276 exprstmt = build_method_call (build1 (NOP_EXPR, TYPE_POINTER_TO (current_class_type), error_mark_node), 277 get_identifier (OPERATOR_DELETE_FORMAT), 278! build_tree_list (NULL_TREE, current_class_decl), 279 NULL_TREE, LOOKUP_NORMAL); 280 else if (TYPE_USES_VIRTUAL_BASECLASSES (current_class_type)) 281 exprstmt = build_x_delete (ptr_type_node, current_class_decl, 0); 282 else 283 exprstmt = 0; 284 285 286 287Printing and Display Problems 288============================= 289 290 291 292* I'm having problems including PostScript illustrations (EPS) using 293 the PSPIC macro and/or \X'ps: import ...'. 294 295A PostScript document must meet three requirements in order to be 296included with the PSPIC macro: it must comply with the Adobe Document 297Structuring Conventions; it must contain a BoundingBox line; it must 298be ``well-behaved''. The BoundingBox line should be of the form: 299 300 %%BoundingBox: llx lly urx ury 301 302where llx, lly, urx, ury are the coordinates of the lower left x, 303lower left y, upper right x, upper right y of the bounding box of 304marks on the page expressed as integers in the default PostScript 305coordinate system (72 units per inch, origin at bottom left corner). 306 307The most convenient program to get the bounding box of a document is 308the `ps2epsi' script coming with GhostScript. 309 310If you can't use this program, another useful tactic is to print out 311the illustration by itself (you may need to add a `showpage' at the 312end), and physically measure the bounding box. For more detail on 313these requirements, read the specification of Encapsulated PostScript 314format. (This is available from the Adobe file server; send a message 315with a body of `help' to ps-file-server@adobe.com.) 316 317If an EPS file to be included via \X'ps: import' does not start with 318%!PS-Adobe-...', gtroff will still include the file, but grops will 319not add any fonts to the generated output file that are listed in the 320EPS file, even though the files are listed in the `download' file and 321are available in the devps directory. 322 323---------------------------------------------------------------------- 324 325* I've configured groff for A4 paper, but gtroff still seems to think 326 that the length of a page (as returned by `\n(.p') is 11 inches. 327 328This is intentional. The PAGE option during configuration is used 329only by grops. For compatibility with ditroff, the default page 330length in gtroff is always 11 inches. The page length can be changed 331with the `pl' request. 332 333A convenient way to set paper dimensions is to use the -dpaper option 334of groff, together with proper -P options for the postprocessor 335(overriding the default). For example, use the following for PS 336output on A4 paper in landscape orientation: 337 338 groff -Tps -dpaper=a4l -P-pa4 -P-l -ms foo.ms > foo.ps 339 340See groff_tmac(5) for more information. 341 342---------------------------------------------------------------------- 343 344* When I print the output of groff -Tps, the output is always shifted 345 up by about 0.7 inches; I'm using 8.5x11 inch paper. 346 347Make sure that the paper size is `letter'. See groff_tmac(5). 348 349---------------------------------------------------------------------- 350 351* When I try to run gxditview, I get the error: 352 Error: Widget viewport has zero width and/or height 353 354This error means you haven't correctly installed the application 355defaults file, GXditview.ad; ``make install'' does this for you 356automatically, so either you didn't do ``make install'', or you don't 357have imake configured correctly. 358 359---------------------------------------------------------------------- 360 361* When I preview documents using -TX75 or -TX100, the layout is not 362 the same as when I print the document with -Tps: the line and page 363 breaks come in different places. 364 365Use groff -X -Tps. 366 367---------------------------------------------------------------------- 368 369* When I try to print the output of groff -Tps, I get no output at all 370 from the printer, and the log file shows the error 371 %%[ error: undefined; offendingcommand: BP ]%% 372 I'm using TranScript spooling software. 373 374This is a bug in the page reversal filter in early versions of 375TranScript. Change the `broken' parameter in 376/usr/local/lib/groff/font/devps/DESC to 7. 377 378---------------------------------------------------------------------- 379 380* When I preview groff -Tps output using the Sun OpenWindows 2.0 381 pageview program, all the pages are displayed on top of each other. 382 383This is a defect in pageview. Change the `broken' parameter in 384/usr/local/lib/groff/font/devps/DESC to 2. 385 386---------------------------------------------------------------------- 387 388* With groff -TX75, -TX100 or -X, I can only view the first page. 389 390The left mouse button brings up a menu that allows you to view other 391pages. 392 393---------------------------------------------------------------------- 394 395* When I print the output of groff -Tdvi, I just get a black dot in 396 upper left corner. 397 398Some dvi drivers (notably early versions of xtex) do not correctly 399handle dvi files that use a resolution different from that used by dvi 400files produced by TeX. Try getting a more up to date driver. 401 402---------------------------------------------------------------------- 403 404* How can I use groff with an old LaserJet printer that doesn't work 405 with groff -Tlj4? 406 407You have at least 3 options: 408 409- use groff -Tps with GNU Ghostscript; 410 411- use groff -Tdvi with a TeX .dvi to Laserjet driver; 412 413- use groff with the LaserJet driver in Chris Lewis' psroff package 414 (available for ftp from: 415 ftp.uunet.ca:/distrib/chris_lewis/psroff3.0pl17). 416 417---------------------------------------------------------------------- 418 419* Groff seems to generate level 3 Postscript, but my printer is only a 420 level 1 or 2 PostScript printer. 421 422In fact groff generates only level 2 PostScript (or rather level 1 423with some extensions; see grops(1) for more information how to disable 424them). The `%!PS-Adobe-3.0' comment at the beginning of PostScript 425output generated by groff indicates that the file conforms to 426version 3.0 of the Adobe Document Structuring Conventions. The output 427generated by groff should be printable on any PostScript printer. 428Problems with groff output's not printing are most often caused by the 429spooling 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 616* bison reports conflicts (either on stderr or in the `pic.output' 617 file) while processing `pic.y', and the produced pic binary doesn't 618 work at all. 619 620You need bison version 1.875b or greater. Alternatively, use yacc or 621byacc. 622 623---------------------------------------------------------------------- 624 625* There are many empty `Makefile.dep' files. Is this a bug? 626 627No. Real dependency files are created with a `make depend' call. 628 629---------------------------------------------------------------------- 630 631* On HP-UX, the compiler complains about missing symbol `alloca'. 632 633Say 634 635 export LDFLAGS=-lPW 636 637before starting the configure script. 638 639---------------------------------------------------------------------- 640 641* The configure script fails on OS/390 (z/OS) Unix. 642 643[This has been fixed in z/OS V1R3 (aka OS/390 R13).] 644 645There is a bug in the Language Environment (LE) whereby the test 646program for static destructors fails. You will see the message 647`configure: error: a working C++ compiler is required' 648 649Applying PTF UQ42006 is supposed to fix this, but the test program is 650still returning the wrong value (1). To work around this problem, you 651can comment out the following in the configure script (near line 2029). 652This will effectively bypass the test (static constructors and 653destructors do actually work properly): 654 655#if { (eval echo "$as_me:2029: \"$ac_link\"") >&5 656# (eval $ac_link) 2>&5 657# ac_status=$? 658# echo "$as_me:2032: \$? = $ac_status" >&5 659# (exit $ac_status); } && { ac_try='./conftest$ac_exeext' 660# { (eval echo "$as_me:2034: \"$ac_try\"") >&5 661# (eval $ac_try) 2>&5 662# ac_status=$? 663# echo "$as_me:2037: \$? = $ac_status" >&5 664# (exit $ac_status); }; }; then 665# echo "$as_me:2039: result: yes" >&5 666#echo "${ECHO_T}yes" >&6 667#else 668# echo "$as_me: program exited with status $ac_status" >&5 669#echo "$as_me: failed program was:" >&5 670#cat conftest.$ac_ext >&5 671#echo "$as_me:2045: result: no" >&5 672#echo "${ECHO_T}no" >&6;{ { echo "$as_me:2046: error: a working C++ compiler is required" >&5 673#echo "$as_me: error: a working C++ compiler is required" >&2;} 674# { (exit 1); exit 1; }; } 675#fi 676 677---------------------------------------------------------------------- 678 679* I get errors when I try to compile groff with DEC C++. 680 681Fix the declaration of write() in <unistd.h> so that the second 682argument is a const char *. Fix the declaration of open() in 683<sys/file.h> so that the first argument is a const char *. 684 685---------------------------------------------------------------------- 686 687* On a host using Unix make (e.g. Solaris), if you are compiling for 688 multiple architectures by building in a subdirectory, the make stops 689 with a message like this: 690 691 make: Fatal error: Don't know how to make target `assert.o' 692 693 or like this: 694 695 make: Fatal error: Can't find /u/src/groff/src/include/Makefile.sub': No such file or directory 696 697This occurs because GNU make and Unix make handle VPATH differently, 698and the groff build relies on GNU make's VPATH handling. 699 700Use GNU make to work around the problem. In Solaris 8, GNU make is 701on the Software Companion CD and is installed as /opt/sfw/bin/gmake. 702 703---------------------------------------------------------------------- 704 705* On Ultrix, the make stops with the message 706 707 *** Error code 1 708 709 Stop. 710 711 for no apparent reason. 712 713Use GNU make. 714 715---------------------------------------------------------------------- 716 717* I'm having problems compiling groff on 386BSD 0.1. 718 719If you're using ash as /bin/sh, you'll need the following patch. 720 721*** gendef.sh.org Sun Jun 30 13:30:36 1991 722--- gendef.sh Sun Feb 28 10:23:49 1993 723*************** 724*** 3,9 **** 725 file=$1 726 shift 727 728! defs="#define $1" 729 shift 730 for def 731 do 732--- 3,10 ---- 733 file=$1 734 shift 735 736! x=$1 737! defs="#define $x" 738 shift 739 for def 740 do 741 742You'll also need to change dirnamemax.c so that it doesn't use 743pathconf(). 744 745---------------------------------------------------------------------- 746 747* While compiling on Xenix, ranlib libgroff.a fails. 748 749The system ranlib can't handle externals longer than 40 characters. 750Use the ranlib included in demon.co.uk:/pub/xenix/g++-1.40.3a.v1 751instead. 752 753---------------------------------------------------------------------- 754 755* I get errors when I try to compile groff with Sun C++ version 3 or 756 earlier. 757 758Groff requires header files that are moderately compatible with AT&T 759C++ and ANSI C. With some versions of Sun C++, the supplied header 760files need some of the following changes to meet this requirement: 761<string.h> must declare the mem* functions, (just add `#include 762<memory.h>' to <string.h>); the first argument to fopen and freopen 763should be declared as `const char *'; the first argument to fread 764should be declared as `void *'; the first argument to fwrite should be 765declared as `const void *'; malloc should be declared to return 766`void *'; in <alloca.h>, the declaration `extern "C" { void 767*__builtin_alloca(int); }' should be added; in <sys/signal.h> the 768return type and the second argument type of signal() should be changed 769to be `void (*)(int)'. 770 771You can either change them in place, or copy them to some other 772directory and include that directory with a -I option. 773 774---------------------------------------------------------------------- 775 776* I get errors when I try to compile groff with Sun C++ version 5.0 777 or 5.1. 778 779This is a known problem; see Sun bug #4301919. As of this writing, no 780patch is available. Use GCC 2.95.2 or later instead. 781 782---------------------------------------------------------------------- 783 784* I get lots of `numeric overflow' error messages whenever I run 785 groff; I compiled groff with AT&T C++ 2.0 with an ANSI C compiler. 786 787Make sure -DCFRONT_ANSI_BUG is included in DEFINES in the top-level 788Makefile. If that doesn't solve the problem, define INT_MIN as 789-INT_MAX in libgroff/lib.h. 790 791---------------------------------------------------------------------- 792 793* When compiling on MacOS X, groff compiles but does not run well. 794 795Use ./configure CXX=g++2 then make as usual. 796