1 Copyright 1989-2014 Free Software Foundation, Inc.
3 Copying and distribution of this file, with or without modification,
4 are permitted in any medium without royalty provided the copyright
5 notice and this notice are preserved.
7 This file describes various problems that have been encountered in
8 compiling, installing and running groff. Suggestions for additions or
9 other improvements to this file are welcome.
11 ----------------------------------------------------------------------
20 * Displaying a man page on a terminal with/without my favourite pager
23 groff by default now uses SGR escape sequences (`ANSI color') to
24 control the display attributes (bold, underlined, colour) on TTYs.
25 Some terminals (e.g. `kterm') don't understand SGR, and some pagers
26 (e.g. older versions of `less' or `less' without the -R option) don't
27 understand SGR either. There are three solutions to fix this, in
28 order of preference; please read the grotty man page for more details.
30 The fourth and probably best option is to update your terminal program
31 and pager to versions which can handle SGR.
33 1. Set the GROFF_NO_SGR environment variable.
35 2. Pass option `-c' to grotty (this is, add `-P-c' to groff's
36 command line options).
38 3. Append the following fragment to the `troffrc' file:
46 . \" The following code sets a top-of-page trap to disable grotty's TTY
47 . \" mode. Since neither \X nor .output can be used before the first
48 . \" page has started, we must use a trap. To make it work with troff's
49 . \" -o option, we wait until the first printed page.
56 . \" The stand-alone version. If no other trap is set, we can safely
57 . \" insert the truncated vertical space caused by the trap (if any).
58 . \" Otherwise we assume that the document's main macro package takes
59 . \" care of that. As soon as the trap has been executed, it is removed.
62 . if (\\n[.t] == \\n[.p]) \{\
74 . \" The piggyback version to be appended to macros planted with the
75 . \" modified `wh' request.
85 . \" We redefine the `wh' request so that `no@sgr1' is appended to
98 ----------------------------------------------------------------------
100 * The UTF-8 output of grotty has strange characters for the minus, the
101 hyphen, and the right quote. Why?
103 The used Unicode characters (U+2212 for the minus sign and U+2010 for
104 the hyphen) are the correct ones, but many programs can't search them
105 properly. The same is true for the right quote (U+201D). To map
106 those characters back to the ASCII characters, insert the following
107 code snippet into the `troffrc' configuration file:
109 .if '\*[.T]'utf8' \{\
115 ----------------------------------------------------------------------
117 * Processing mdoc man pages like `groff_mdoc.n' fails if I use
120 The mdoc package works only after installation, not with test-groff.
121 Reason is that the macro files of mdoc get stripped off the `doc-'
122 prefix before they are copied to the final destination.
124 ----------------------------------------------------------------------
126 * My document says that the current year is 19100, not 2000.
128 In groff, as in traditional troff, the yr number register yields the
129 year minus 1900. Unfortunately, there is a longstanding bug in the
130 Troff User's Manual <http://cm.bell-labs.com/cm/cs/cstr/54.ps.gz>,
131 which incorrectly claims that yr is the last two digits of the year.
132 This claim was never true of either Unix troff or of groff.
134 If your text looks like this:
137 This document was formatted in 19\n(yr.
139 you can correct it as follows:
141 This document was formatted in \n[year].
143 or, if you want to be portable to older troff versions, as follows:
146 This document was formatted in \n(y4.
148 ----------------------------------------------------------------------
150 * groff can't handle my troff document. It works fine with AT&T
153 Read the section on incompatibilities in groff_diff(7). Try using the
154 -C option. Alternatively there's the sed script `tmac/fixmacros.sed'
155 which attempts to edit a file of macros so that it can be used with
156 groff without the -C flag.
158 ----------------------------------------------------------------------
160 * gtroff doesn't understand lines like `.ce99' with no space between
161 the name of the request or macro and the arguments.
163 gtroff requires a space between macro or request and its arguments
164 because it allows the use of long names for macros and requests. You
165 can use the -C option or the `cp' request to put gtroff into a
166 compatibility mode in which it is not possible to use long names for
167 macros but in which no space is required between macros and their
168 arguments. The use of compatibility mode is strongly discouraged.
170 ----------------------------------------------------------------------
172 * groff -Tdvi produces dvi files that use fonts at weird
175 Yes, it does. You may need to compile fonts with Metafont at these
176 magnifications. The CompileFonts script in the devdvi/generate
177 directory may help you to do this. (It takes a *long* time on slow
180 ----------------------------------------------------------------------
182 * Groff doesn't use the font names I'm used to.
184 Use the `ftr' request. See groff_diff(7).
186 ----------------------------------------------------------------------
188 * gpic output is not centered horizontally; pictures sometimes run off
189 the bottom of the page.
191 The macro package you are using is not supplying appropriate
192 definitions of PS and PE. Give groff a -mpic option.
194 ----------------------------------------------------------------------
196 * gpic doesn't accept the syntax `chop N M' for chopping both ends of
199 The correct syntax is `chop N chop M'.
201 ----------------------------------------------------------------------
203 * With gpic -t, when I print `line ->; box' using a dvi to ps program,
204 the arrow head sticks through into the inside of the box.
206 The dvi to ps program should be modified to set the line cap and line
207 join parameters to 1 while printing tpic specials.
209 ----------------------------------------------------------------------
211 * gtroff gives warnings about lines like
213 (with a tab after the .ev).
215 A tab character cannot be used as a substitute for a space character
216 (except in one case: between a control character at the beginning of a
217 line and the name of a macro or request). For example, in Unix troff
219 .ps \" restore the previous point size
221 (with a tab after the .ps) does NOT restore the previous point-size;
222 instead it is silently ignored. Since this is very likely to be an
223 error, gtroff can give a warning about it. If you want to align
224 comments, you can do it like this:
228 ----------------------------------------------------------------------
230 * I don't like the page headers and footers produced by groff -man.
232 There seem to be many different styles of page header and footer
233 produced by different versions of the -man macros. You need to put
234 modified macros from tmac/an-old.tmac into man.local. More
235 information is available in groff_man(7).
237 ----------------------------------------------------------------------
239 * Where can I get grap?
241 Ted Faber <faber@lunabase.org> has written a freely available grap:
243 http://www.lunabase.org/~faber/Vault/software/grap/
245 You need version 1.42 or newer.
247 ----------------------------------------------------------------------
249 * The \n(st and \n(sb registers don't seem to work. I thought \w set
250 them to the height and depth of its argument, but the registers
253 \n(st and \n(sb aren't supposed to give the height and depth of the
254 string rather they give the minimum and maximum vertical displacement
255 of the baseline. For example for \v'2u'\v'-3u', \n(st is 1 and \n(sb
256 is -2. The height and depth of the string is available in the \n[rst]
257 and \n[rsb] registers: these are groff extensions.
259 ----------------------------------------------------------------------
261 * While formatting a manual page, groff complains about not being able
262 to break lines. The problem seems to be caused by a line like:
265 The -man documentation says that the default scale indicator for TP
266 macro is `n'. The groff -man macros implement this correctly, so that
267 the argument is evaluated as if it were
271 The Unix -man macros don't implement this correctly (probably because
272 it's hard to do in Unix troff); they just append `n' to the entire
273 argument, so that it is evaluated as if it were
277 The solution is to fix the manual page:
281 ----------------------------------------------------------------------
283 * I'm having problems formatting man pages produced by the perl
286 Some versions of wrapman have a superfluous blank line before the .TH
287 line. This must be deleted. Then either use groff -C, or apply the
290 *** wrapman.~2~ Sun Jan 19 12:10:24 1992
291 --- wrapman Tue Aug 10 02:06:41 1993
294 $line1 .= <IN> if $line1 =~ /eval/;
295 $line1 .= <IN> if $line1 =~ /argv/;
297 ! next if $line2 eq "'di';\n";
299 # Pull the old switcheroo.
302 $line1 .= <IN> if $line1 =~ /eval/;
303 $line1 .= <IN> if $line1 =~ /argv/;
305 ! next if $line2 eq "'di ';\n" || $line2 eq "'di';\n";
307 # Pull the old switcheroo.
333 # These next few lines are legal in both Perl and nroff.
335 ! $null.00; # finish .ig
337 'di \\" finish diversion--previous line must be blank
338 .nr nl 0-1 \\" fake up transition to first page again
339 .nr % 0 \\" start at page 1
340 ! '; __END__ ##### From here on it's a standard manual page #####
341 .TH $PROG 1 "$month $mday, 19$year"
348 # These next few lines are legal in both Perl and nroff.
350 ! $null.00 ; # finish .ig
353 'di \\" finish diversion--previous line must be blank
354 .nr nl 0-1 \\" fake up transition to first page again
355 .nr % 0 \\" start at page 1
356 ! .\\"'; __END__ ##### From here on it's a standard manual page #####
357 .TH $PROG 1 "$month $mday, 19$year"
362 ----------------------------------------------------------------------
364 * groff uses up an enormous amount of memory processing large files.
365 I'm using 386BSD 0.1.
367 386BSD includes an old version of g++, 1.39, which has a bug that
368 causes a major memory leak in gtroff. Apply the following fix to g++
371 *** cplus-decl.c.~1~ Mon Aug 6 05:28:59 1990
372 --- cplus-decl.c Wed Jun 5 08:55:04 1991
376 /* At the end, call delete if that's what's requested. */
377 if (TREE_GETS_DELETE (current_class_type))
378 exprstmt = build_method_call (build1 (NOP_EXPR, TYPE_POINTER_TO (current_class_type), error_mark_node),
379 get_identifier (OPERATOR_DELETE_FORMAT),
380 ! build_tree_list (NULL_TREE, integer_zero_node),
381 NULL_TREE, LOOKUP_NORMAL);
382 else if (TYPE_USES_VIRTUAL_BASECLASSES (current_class_type))
383 exprstmt = build_x_delete (ptr_type_node, current_class_decl, 0);
388 /* At the end, call delete if that's what's requested. */
389 if (TREE_GETS_DELETE (current_class_type))
390 exprstmt = build_method_call (build1 (NOP_EXPR, TYPE_POINTER_TO (current_class_type), error_mark_node),
391 get_identifier (OPERATOR_DELETE_FORMAT),
392 ! build_tree_list (NULL_TREE, current_class_decl),
393 NULL_TREE, LOOKUP_NORMAL);
394 else if (TYPE_USES_VIRTUAL_BASECLASSES (current_class_type))
395 exprstmt = build_x_delete (ptr_type_node, current_class_decl, 0);
401 Printing and Display Problems
402 =============================
406 * I'm having problems including PostScript illustrations (EPS) using
407 the PSPIC macro and/or \X'ps: import ...'.
409 A PostScript document must meet three requirements in order to be
410 included with the PSPIC macro: it must comply with the Adobe Document
411 Structuring Conventions; it must contain a BoundingBox line; it must
412 be `well-behaved'. The BoundingBox line should be of the form:
414 %%BoundingBox: llx lly urx ury
416 where llx, lly, urx, ury are the coordinates of the lower left x,
417 lower left y, upper right x, upper right y of the bounding box of
418 marks on the page expressed as integers in the default PostScript
419 coordinate system (72 units per inch, origin at bottom left corner).
421 The most convenient program to get the bounding box of a document is
422 the `ps2epsi' script coming with GhostScript.
424 If you can't use this program, another useful tactic is to print out
425 the illustration by itself (you may need to add a `showpage' at the
426 end), and physically measure the bounding box. For more detail on
427 these requirements, read the specification of Encapsulated PostScript
428 format. (This is available from the Adobe file server; send a message
429 with a body of `help' to ps-file-server@adobe.com.)
431 If an EPS file to be included via \X'ps: import' does not start with
432 `%!PS-Adobe-...', gtroff still includes the file, but grops does not
433 add any fonts to the generated output file that are listed in the EPS
434 file, even though the files are listed in the `download' file and are
435 available in the devps directory.
437 ----------------------------------------------------------------------
439 * I've configured groff for A4 paper, but gtroff still seems to think
440 that the length of a page (as returned by `\n(.p') is 11 inches.
442 This is intentional. The PAGE option during configuration is used
443 only by grops. For compatibility with ditroff, the default page
444 length in gtroff is always 11 inches. The page length can be changed
445 with the `pl' request.
447 A convenient way to set paper dimensions is to use the -dpaper option
448 of groff, together with proper -P options for the postprocessor
449 (overriding the default). For example, use the following for PS
450 output on A4 paper in landscape orientation:
452 groff -Tps -dpaper=a4l -P-pa4 -P-l -ms foo.ms > foo.ps
454 See groff_tmac(5) for more information.
456 ----------------------------------------------------------------------
458 * When I print the output of groff -Tps, the output is always shifted
459 up by about 0.7 inches; I'm using 8.5x11 inch paper.
461 Make sure that the paper size is `letter'. See groff_tmac(5).
463 ----------------------------------------------------------------------
465 * When I try to run gxditview, I get the error:
466 Error: Widget viewport has zero width and/or height
468 This error means you haven't correctly installed the application
469 defaults file, GXditview.ad; `make install' does this for you
470 automatically, so either you didn't do `make install', or you haven't
471 passed a good `--appresdir=<DIR>' argument to groff's configure
474 See the X(7) man page for information how and where application
475 resource files have to be located. Look for the XAPPLRESDIR and
476 XUSERFILESEARCHPATH environment variables.
478 ----------------------------------------------------------------------
480 * When I preview documents using -TX75 or -TX100, the layout is not
481 the same as when I print the document with -Tps: the line and page
482 breaks come in different places.
486 ----------------------------------------------------------------------
488 * When I try to print the output of groff -Tps, I get no output at all
489 from the printer, and the log file shows the error
490 %%[ error: undefined; offendingcommand: BP ]%%
491 I'm using TranScript spooling software.
493 This is a bug in the page reversal filter in early versions of
494 TranScript. Change the `broken' parameter in
495 /usr/local/lib/groff/font/devps/DESC to 7.
497 ----------------------------------------------------------------------
499 * When I preview groff -Tps output using the Sun OpenWindows 2.0
500 pageview program, all the pages are displayed on top of each other.
502 This is a defect in pageview. Change the `broken' parameter in
503 /usr/local/lib/groff/font/devps/DESC to 2.
505 ----------------------------------------------------------------------
507 * With groff -TX75, -TX100 or -X, I can only view the first page.
509 The left mouse button brings up a menu that allows you to view other
512 ----------------------------------------------------------------------
514 * When I print the output of groff -Tdvi, I just get a black dot in
517 Some dvi drivers (notably early versions of xtex) do not correctly
518 handle dvi files that use a resolution different from that used by dvi
519 files produced by TeX. Try getting a more up to date driver.
521 ----------------------------------------------------------------------
523 * How can I use groff with an old LaserJet printer that doesn't work
526 You have at least 3 options:
528 - use groff -Tps with GNU Ghostscript;
530 - use groff -Tdvi with a TeX .dvi to Laserjet driver;
532 - use groff with the LaserJet driver in Chris Lewis' psroff package
533 (available for ftp from:
534 ftp.uunet.ca:/distrib/chris_lewis/psroff3.0pl17).
536 ----------------------------------------------------------------------
538 * Groff seems to generate level 3 Postscript, but my printer is only a
539 level 1 or 2 PostScript printer.
541 In fact groff generates only level 2 PostScript (or rather level 1
542 with some extensions; see grops(1) for more information how to disable
543 them). The `%!PS-Adobe-3.0' comment at the beginning of PostScript
544 output generated by groff indicates that the file conforms to version
545 3.0 of the Adobe Document Structuring Conventions. The output
546 generated by groff should be printable on any PostScript printer.
547 Problems with groff output's not printing are most often caused by the
552 Platform-Dependent Macro Problems
553 =================================
557 * I get lots of errors when I use groff with the AT&T -mm macros.
559 Use the groff -mm macros.
561 ----------------------------------------------------------------------
563 * groff produces wrapper macros for `ms' and friends which call the
564 system's original macros. Then, to get groff's ms macro package I
565 have to use `-mgs' instead `-ms'. Can I avoid this?
567 Yes. Configure and compile groff as usual, but install it with
569 make install tmac_wrap=""
571 Then no wrapper files are produced, and `-ms' uses groff's `ms'
574 ----------------------------------------------------------------------
576 * I'm having problems formatting HP-UX 9.0 man pages with groff -man.
578 Copy HP's tmac.an into /usr/local/share/groff/site-tmac/an.tmac, and
579 either put `.cp 1' at the beginning or filter it (and any files it
580 .so's) through tmac/fixmacros.sed.
582 ----------------------------------------------------------------------
584 * I get errors using the Unix -ms macros with groff -e -C.
588 *** /usr/lib/ms/ms.eqn Tue Apr 25 02:14:28 1989
589 --- ms.eqn Sun Nov 11 10:33:59 1990
593 . \" EN - end of a displayed equation
595 ! .if !
\a\\*(10
\a\a .br
599 .if \\n(ZN>0 .if \\n(YE=0 .LP
602 . \" EN - end of a displayed equation
609 .if \\n(ZN>0 .if \\n(YE=0 .LP
611 ----------------------------------------------------------------------
613 * I'm having problems formatting Ultrix man pages with groff -man.
615 The Ultrix man pages use a number of non-standard extensions to the
616 Unix man macros. One solution is to use the Ultrix -man macros with
617 groff. Copy /usr/lib/tmac/tmac.an to
618 /usr/local/share/groff/site-tmac/an.tmac and apply the following patch
619 (from Frank Wortner):
621 *** /usr/local/lib/groff/tmac/tmac.an Wed Sep 9 12:29:28 1992
622 --- /usr/lib/tmac/tmac.an Fri Jul 24 19:58:19 1992
625 . \" make special case of shift out of italic
628 ! .if \\$12 .if !\\$5 .ds ]F \^
629 .ie !\\$4 .}S \\$2 \\$1 "\\$3\f\\$1\\$4\\*(]F" "\\$5" "\\$6" "\\$7" "\\$8" "\\$9"
633 . \" make special case of shift out of italic
636 ! .if \\$12 .if !\\$5 .ds ]F\^
637 .ie !\\$4 .}S \\$2 \\$1 "\\$3\f\\$1\\$4\\*(]F" "\\$5" "\\$6" "\\$7" "\\$8" "\\$9"
641 Another possible solution is to install tmac/man.ultrix as
642 /usr/local/share/groff/site-tmac/man.local.
644 ----------------------------------------------------------------------
646 * On an SGI system, how can I make the man command use groff?
648 From David Hinds <dhinds@allegro.stanford.edu> (some of these steps
649 are unnecessary if you install with the `g' Makefile variable defined
652 Create a script called `eqn':
655 > if [ ${1:-""} = /usr/pub/eqnchar ] ; then shift ; fi
658 and a script called `neqn':
661 > if [ ${1:-""} = /usr/pub/eqnchar ] ; then shift ; fi
668 and edit the end of the gnroff script to be:
670 > rest=`echo ${1+"$@"} | sed -e 's+/usr/lib/tmac+/usr/local/lib/groff/tmac+'`
671 > exec groff -Wall -mtty-char $T $opts $rest
673 To get PostScript output from `man -t', you also need to create a
674 `psroff' script similar to `nroff'. Here are the context diffs:
676 *** /usr/local/bin/nroff Sat Feb 13 15:51:09 1993
677 --- /usr/local/bin/psroff Sat Feb 13 17:45:46 1993
681 ! # Emulate nroff with groff.
690 ! # Emulate psroff with groff.
704 + # ignore -- default is send to stdout
707 # ignore other devices
711 rest=`echo ${1+"$@"} | sed -e 's+/usr/lib/tmac+/usr/local/lib/groff/tmac+'`
713 # This shell script is intended for use with man, so warnings are
714 # probably not wanted. Also load nroff-style character definitions.
715 ! exec groff -Wall -mtty-char $T $opts $rest
717 rest=`echo ${1+"$@"} | sed -e 's+/usr/lib/tmac+/usr/local/lib/groff/tmac+'`
719 # This shell script is intended for use with man, so warnings are
720 ! # probably not wanted.
721 ! exec groff -Wall $T $opts $rest
730 * Compilation dies with
732 y.tab.c: In function `int yyparse()':
733 y.tab.c: `size_t' undeclared in namespace `std'
735 * bison reports conflicts (either on stderr or in the `pic.output'
736 file) while processing `pic.y', and the produced pic binary doesn't
739 You need bison version 1.875b or greater. Alternatively, use yacc or
742 ----------------------------------------------------------------------
744 * There are many empty `Makefile.dep' files. Is this a bug?
746 No. Real dependency files are created with a `make depend' call.
748 ----------------------------------------------------------------------
750 * On HP-UX, the compiler complains about missing symbol `alloca'.
756 before starting the configure script.
758 ----------------------------------------------------------------------
760 * The configure script fails on OS/390 (z/OS) Unix.
762 [This has been fixed in z/OS V1R3 (aka OS/390 R13).]
764 There is a bug in the Language Environment (LE) whereby the test
765 program for static destructors fails. You see the message `configure:
766 error: a working C++ compiler is required'.
768 Applying PTF UQ42006 is supposed to fix this, but the test program is
769 still returning the wrong value (1). To work around this problem, you
770 can comment out the following in the configure script (near line
771 2029). This effectively bypasses the test (static constructors and
772 destructors do actually work properly):
774 #if { (eval echo "$as_me:2029: \"$ac_link\"") >&5
775 # (eval $ac_link) 2>&5
777 # echo "$as_me:2032: \$? = $ac_status" >&5
778 # (exit $ac_status); } && { ac_try='./conftest$ac_exeext'
779 # { (eval echo "$as_me:2034: \"$ac_try\"") >&5
780 # (eval $ac_try) 2>&5
782 # echo "$as_me:2037: \$? = $ac_status" >&5
783 # (exit $ac_status); }; }; then
784 # echo "$as_me:2039: result: yes" >&5
785 #echo "${ECHO_T}yes" >&6
787 # echo "$as_me: program exited with status $ac_status" >&5
788 #echo "$as_me: failed program was:" >&5
789 #cat conftest.$ac_ext >&5
790 #echo "$as_me:2045: result: no" >&5
791 #echo "${ECHO_T}no" >&6;{ { echo "$as_me:2046: error: a working C++ compiler is required" >&5
792 #echo "$as_me: error: a working C++ compiler is required" >&2;}
793 # { (exit 1); exit 1; }; }
796 ----------------------------------------------------------------------
798 * I get errors when I try to compile groff with DEC C++.
800 Fix the declaration of write() in <unistd.h> so that the second
801 argument is a const char *. Fix the declaration of open() in
802 <sys/file.h> so that the first argument is a const char *.
804 ----------------------------------------------------------------------
806 * On a host using Unix make (e.g. Solaris), if you are compiling for
807 multiple architectures by building in a subdirectory, the make stops
808 with a message like this:
810 make: Fatal error: Don't know how to make target `assert.o'
814 make: Fatal error: Can't find /u/src/groff/src/include/Makefile.sub': No such file or directory
816 This occurs because GNU make and Unix make handle VPATH differently,
817 and the groff build relies on GNU make's VPATH handling.
819 Use GNU make <http://www.gnu.org/software/make/> to work around this.
820 In Solaris 8 and 9, GNU make is on the Software Companion CD in
821 package SFWgmake and is installed as /opt/sfw/bin/gmake. Prebuilt
822 versions of GNU make for Solaris are also available from
825 ----------------------------------------------------------------------
827 * On Ultrix, the make program stops with the message
833 for no apparent reason.
837 ----------------------------------------------------------------------
839 * I'm having problems compiling groff on 386BSD 0.1.
841 If you're using ash as /bin/sh, you'll need the following patch.
843 *** gendef.sh.org Sun Jun 30 13:30:36 1991
844 --- gendef.sh Sun Feb 28 10:23:49 1993
864 You'll also need to change dirnamemax.c so that it doesn't use
867 ----------------------------------------------------------------------
869 * While compiling on Xenix, ranlib libgroff.a fails.
871 The system ranlib can't handle externals longer than 40 characters.
872 Use the ranlib included in demon.co.uk:/pub/xenix/g++-1.40.3a.v1
875 ----------------------------------------------------------------------
877 * I get errors when I try to compile groff with Sun C++ version 3 or
880 Groff requires header files that are moderately compatible with AT&T
881 C++ and ANSI C. With some versions of Sun C++, the supplied header
882 files need some of the following changes to meet this requirement:
883 <string.h> must declare the mem* functions, (just add `#include
884 <memory.h>' to <string.h>); the first argument to fopen and freopen
885 should be declared as `const char *'; the first argument to fread
886 should be declared as `void *'; the first argument to fwrite should be
887 declared as `const void *'; malloc should be declared to return
888 `void *'; in <alloca.h>, the declaration `extern "C" { void
889 *__builtin_alloca(int); }' should be added; in <sys/signal.h> the
890 return type and the second argument type of signal() should be changed
891 to be `void (*)(int)'.
893 You can either change them in place, or copy them to some other
894 directory and include that directory with a -I option.
896 ----------------------------------------------------------------------
898 * I get errors when I try to compile groff with Forte Development 6
899 or 6u1, or Sun C++ version 5.0 through 5.2.
901 This is a known problem; see Sun bug #4301919. See Sun patches
902 109482, 109490, 109508, and 109509 for fixes.
904 ----------------------------------------------------------------------
906 * I get warnings from the Sun linker while using gcc 3.4.0:
908 ld: warning: relocation error: R_SPARC_UA32:
909 file groff/src/libs/libgroff/libgroff.a(getopt.o): symbol optarg:
910 external symbolic relocation against non-allocatable
911 section .debug_info; cannot be processed at runtime:
914 This seems to be a known problem (Sun bugs #4910101 and #4910810,
915 filed in September 2003; gcc bug #15599, filed May 2004) without a
916 public fix as of this writing. A work-around is to use option
917 `-gstabs+' instead of `-g' (and a high probability that the output is
918 only debuggable with gdb but not with Sun's debuggers).
920 ----------------------------------------------------------------------
922 * I get lots of `numeric overflow' error messages whenever I run
923 groff; I compiled groff with AT&T C++ 2.0 with an ANSI C compiler.
925 Make sure -DCFRONT_ANSI_BUG is included in DEFINES in the top-level
926 Makefile. If that doesn't solve the problem, define INT_MIN as
927 -INT_MAX in libgroff/lib.h.
929 ----------------------------------------------------------------------
931 * In MacOS X, I want to completely replace the groff that came with
936 ./configure --prefix=/usr --mandir=/usr/share/man
943 Note that subsequent system updates may replace your groff.
945 ----------------------------------------------------------------------
947 * When compiling on MacOS X 10.2, groff compiles but does not run
948 well, especially `eqn', causing many `can't break line' messages.
960 ----------------------------------------------------------------------
962 * Configuration on MacOS X 10.6 doesn't succeed.
966 ./configure CXX=g++-4.2