head	1.1;
branch	1.1.1;
access;
symbols
	RELENG_8_4:1.1.1.8.0.30
	RELENG_9_1_0_RELEASE:1.1.1.8
	RELENG_9_1:1.1.1.8.0.28
	RELENG_9_1_BP:1.1.1.8
	RELENG_8_3_0_RELEASE:1.1.1.8
	RELENG_8_3:1.1.1.8.0.26
	RELENG_8_3_BP:1.1.1.8
	RELENG_9_0_0_RELEASE:1.1.1.8
	RELENG_9_0:1.1.1.8.0.24
	RELENG_9_0_BP:1.1.1.8
	RELENG_9:1.1.1.8.0.22
	RELENG_9_BP:1.1.1.8
	RELENG_7_4_0_RELEASE:1.1.1.8
	RELENG_8_2_0_RELEASE:1.1.1.8
	RELENG_7_4:1.1.1.8.0.20
	RELENG_7_4_BP:1.1.1.8
	RELENG_8_2:1.1.1.8.0.18
	RELENG_8_2_BP:1.1.1.8
	RELENG_8_1_0_RELEASE:1.1.1.8
	RELENG_8_1:1.1.1.8.0.16
	RELENG_8_1_BP:1.1.1.8
	RELENG_7_3_0_RELEASE:1.1.1.8
	RELENG_7_3:1.1.1.8.0.14
	RELENG_7_3_BP:1.1.1.8
	RELENG_8_0_0_RELEASE:1.1.1.8
	RELENG_8_0:1.1.1.8.0.12
	RELENG_8_0_BP:1.1.1.8
	RELENG_8:1.1.1.8.0.10
	RELENG_8_BP:1.1.1.8
	RELENG_7_2_0_RELEASE:1.1.1.8
	RELENG_7_2:1.1.1.8.0.8
	RELENG_7_2_BP:1.1.1.8
	RELENG_7_1_0_RELEASE:1.1.1.8
	RELENG_6_4_0_RELEASE:1.1.1.7.12.1
	RELENG_7_1:1.1.1.8.0.6
	RELENG_7_1_BP:1.1.1.8
	RELENG_6_4:1.1.1.7.12.1.0.8
	RELENG_6_4_BP:1.1.1.7.12.1
	RELENG_7_0_0_RELEASE:1.1.1.8
	RELENG_6_3_0_RELEASE:1.1.1.7.12.1
	RELENG_7_0:1.1.1.8.0.4
	RELENG_7_0_BP:1.1.1.8
	RELENG_6_3:1.1.1.7.12.1.0.6
	RELENG_6_3_BP:1.1.1.7.12.1
	RELENG_7:1.1.1.8.0.2
	RELENG_7_BP:1.1.1.8
	RELENG_6_2_0_RELEASE:1.1.1.7.12.1
	RELENG_6_2:1.1.1.7.12.1.0.4
	RELENG_6_2_BP:1.1.1.7.12.1
	RELENG_5_5_0_RELEASE:1.1.1.7
	RELENG_5_5:1.1.1.7.0.16
	RELENG_5_5_BP:1.1.1.7
	RELENG_6_1_0_RELEASE:1.1.1.7.12.1
	RELENG_6_1:1.1.1.7.12.1.0.2
	RELENG_6_1_BP:1.1.1.7.12.1
	RELENG_6_0_0_RELEASE:1.1.1.7
	v1_19_2:1.1.1.8
	RELENG_6_0:1.1.1.7.0.14
	RELENG_6_0_BP:1.1.1.7
	RELENG_6:1.1.1.7.0.12
	RELENG_6_BP:1.1.1.7
	RELENG_5_4_0_RELEASE:1.1.1.7
	RELENG_5_4:1.1.1.7.0.10
	RELENG_5_4_BP:1.1.1.7
	RELENG_4_11_0_RELEASE:1.1.1.3.2.4
	RELENG_4_11:1.1.1.3.2.4.0.6
	RELENG_4_11_BP:1.1.1.3.2.4
	RELENG_5_3_0_RELEASE:1.1.1.7
	RELENG_5_3:1.1.1.7.0.8
	RELENG_5_3_BP:1.1.1.7
	RELENG_5:1.1.1.7.0.6
	RELENG_5_BP:1.1.1.7
	RELENG_4_10_0_RELEASE:1.1.1.3.2.4
	RELENG_4_10:1.1.1.3.2.4.0.4
	RELENG_4_10_BP:1.1.1.3.2.4
	RELENG_5_2_1_RELEASE:1.1.1.7
	RELENG_5_2_0_RELEASE:1.1.1.7
	RELENG_5_2:1.1.1.7.0.4
	RELENG_5_2_BP:1.1.1.7
	RELENG_4_9_0_RELEASE:1.1.1.3.2.4
	RELENG_4_9:1.1.1.3.2.4.0.2
	RELENG_4_9_BP:1.1.1.3.2.4
	RELENG_5_1_0_RELEASE:1.1.1.7
	RELENG_5_1:1.1.1.7.0.2
	RELENG_5_1_BP:1.1.1.7
	v1_19:1.1.1.7
	RELENG_4_8_0_RELEASE:1.1.1.3.2.3
	RELENG_4_8:1.1.1.3.2.3.0.2
	RELENG_4_8_BP:1.1.1.3.2.3
	RELENG_5_0_0_RELEASE:1.1.1.6
	RELENG_5_0:1.1.1.6.0.2
	RELENG_5_0_BP:1.1.1.6
	v1_18_1:1.1.1.6
	RELENG_4_7_0_RELEASE:1.1.1.3.2.2
	RELENG_4_7:1.1.1.3.2.2.0.8
	RELENG_4_7_BP:1.1.1.3.2.2
	RELENG_4_6_2_RELEASE:1.1.1.3.2.2
	RELENG_4_6_1_RELEASE:1.1.1.3.2.2
	RELENG_4_6_0_RELEASE:1.1.1.3.2.2
	RELENG_4_6:1.1.1.3.2.2.0.6
	RELENG_4_6_BP:1.1.1.3.2.2
	RELENG_4_5_0_RELEASE:1.1.1.3.2.2
	RELENG_4_5:1.1.1.3.2.2.0.4
	RELENG_4_5_BP:1.1.1.3.2.2
	RELENG_4_4_0_RELEASE:1.1.1.3.2.2
	RELENG_4_4:1.1.1.3.2.2.0.2
	RELENG_4_4_BP:1.1.1.3.2.2
	v1_17_2:1.1.1.5
	RELENG_4_3_0_RELEASE:1.1.1.3.2.1
	RELENG_4_3:1.1.1.3.2.1.0.2
	RELENG_4_3_BP:1.1.1.3.2.1
	v1_17:1.1.1.5
	v1_16_1:1.1.1.4
	RELENG_4_2_0_RELEASE:1.1.1.3
	RELENG_4_1_1_RELEASE:1.1.1.3
	PRE_SMPNG:1.1.1.3
	RELENG_4_1_0_RELEASE:1.1.1.3
	RELENG_3_5_0_RELEASE:1.1.1.1.4.2
	RELENG_4_0_0_RELEASE:1.1.1.3
	RELENG_4:1.1.1.3.0.2
	RELENG_4_BP:1.1.1.3
	v1_15:1.1.1.3
	RELENG_3_4_0_RELEASE:1.1.1.1.4.1
	RELENG_3_3_0_RELEASE:1.1.1.1.4.1
	RELENG_3_2_PAO:1.1.1.1.4.1.0.2
	RELENG_3_2_PAO_BP:1.1.1.1.4.1
	RELENG_3_2_0_RELEASE:1.1.1.1.4.1
	v1_11:1.1.1.2
	RELENG_3_1_0_RELEASE:1.1.1.1
	RELENG_3:1.1.1.1.0.4
	RELENG_3_BP:1.1.1.1
	RELENG_2_2_8_RELEASE:1.1.1.1
	RELENG_3_0_0_RELEASE:1.1.1.1
	RELENG_2_2_7_RELEASE:1.1.1.1
	RELENG_2_2_6_RELEASE:1.1.1.1
	RELENG_2_2_5_RELEASE:1.1.1.1
	RELENG_2_2_2_RELEASE:1.1.1.1
	RELENG_2_2_1_RELEASE:1.1.1.1
	RELENG_2_2_0_RELEASE:1.1.1.1
	RELENG_2_2:1.1.1.1.0.2
	RELENG_2_2_BP:1.1.1.1
	v1_10:1.1.1.1
	FSF:1.1.1;
locks; strict;
comment	@# @;


1.1
date	96.09.07.16.17.57;	author pst;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	96.09.07.16.17.57;	author pst;	state Exp;
branches
	1.1.1.1.4.1;
next	1.1.1.2;

1.1.1.2
date	99.03.15.08.35.22;	author obrien;	state Exp;
branches;
next	1.1.1.3;

1.1.1.3
date	2000.01.12.09.48.06;	author asmodai;	state Exp;
branches
	1.1.1.3.2.1;
next	1.1.1.4;

1.1.1.4
date	2000.12.05.18.49.20;	author ru;	state Exp;
branches;
next	1.1.1.5;

1.1.1.5
date	2001.04.17.12.11.28;	author ru;	state Exp;
branches;
next	1.1.1.6;

1.1.1.6
date	2002.10.11.08.52.00;	author ru;	state Exp;
branches;
next	1.1.1.7;

1.1.1.7
date	2003.05.01.13.09.48;	author ru;	state Exp;
branches
	1.1.1.7.12.1;
next	1.1.1.8;

1.1.1.8
date	2005.10.20.10.45.16;	author ru;	state Exp;
branches
	1.1.1.8.30.1;
next	;

1.1.1.1.4.1
date	99.03.18.00.03.49;	author obrien;	state Exp;
branches;
next	1.1.1.1.4.2;

1.1.1.1.4.2
date	2000.03.09.20.06.01;	author asmodai;	state Exp;
branches;
next	;

1.1.1.3.2.1
date	2000.12.07.09.48.11;	author ru;	state Exp;
branches;
next	1.1.1.3.2.2;

1.1.1.3.2.2
date	2001.04.26.17.32.38;	author ru;	state Exp;
branches;
next	1.1.1.3.2.3;

1.1.1.3.2.3
date	2003.02.14.15.21.44;	author ru;	state Exp;
branches;
next	1.1.1.3.2.4;

1.1.1.3.2.4
date	2003.06.26.13.13.12;	author ru;	state Exp;
branches;
next	;

1.1.1.7.12.1
date	2005.11.15.22.06.18;	author ru;	state Exp;
branches;
next	;

1.1.1.8.30.1
date	2005.10.20.10.45.16;	author svnexp;	state dead;
branches;
next	1.1.1.8.30.2;

1.1.1.8.30.2
date	2013.03.28.13.01.12;	author svnexp;	state Exp;
branches;
next	;


desc
@@


1.1
log
@Initial revision
@
text
@To install groff, follow the instructions in the file INSTALL.gen.

This file contains information that supplements those instructions.

groff is written in C++, so you will need a C++ compiler.  The C++
source files use a suffix of `.cc', so your C++ compiler must be able
to handle this.  If you don't already have a C++ compiler, I suggest
gcc 2.7.1 or later (gcc version 2 includes GNU C++ as well as GNU C).
From gcc 2.5, it is no longer necessary to install libg++: the C++
header files needed by groff are created by the gcc installation
process.  To override configure's choice of C++ compiler, you can set
the CXX environment variable.

If you have a library that provides a faster malloc than your system's
usual malloc, it is good idea to include it in LIBS.  For example,
using the malloc that comes with GNU Emacs version 18 can give a
worthwhile (and sometimes spectacular) performance improvement.

When you have build groff, you can use the test-groff script to try
groff out on one of the man pages.  (Use the .n files not the .man
files.)  The test-groff script sets up environment variables to allow
groff to run without being installed.  The current directory must be
the build directory when the script is run.  For example, you could do

  ./test-groff -man -Tascii groff/groff.n | less

If you want to install gxditview (an X11 previewer), follow the
instructions in the INSTALL file in the xditview directory.

If you have problems, read the PROBLEMS file.  If this doesn't help
send a bug report using the form in the file BUG-REPORT.
@


1.1.1.1
log
@Virgin import of FSF groff v1.10
@
text
@@


1.1.1.1.4.1
log
@MFC: upgrade to ver 1.11.
@
text
@d19 1
a19 1
When you have built groff, you can use the test-groff script to try
@


1.1.1.1.4.2
log
@MFC: groff 1.15
@
text
@d16 1
a16 1
using the malloc that comes with GNU Emacs version 20 can give a
a28 4

To get PostScript versions of the documentation resp. reference files for
the `me' macros and the `pic' preprocessor, simply say `make' in the
`doc' subdirectory.
@


1.1.1.2
log
@Virgin import of FSF groff v1.11
@
text
@d19 1
a19 1
When you have built groff, you can use the test-groff script to try
@


1.1.1.3
log
@Virgin import of FSF groff v1.15
@
text
@d16 1
a16 1
using the malloc that comes with GNU Emacs version 20 can give a
a28 4

To get PostScript versions of the documentation resp. reference files for
the `me' macros and the `pic' preprocessor, simply say `make' in the
`doc' subdirectory.
@


1.1.1.3.2.1
log
@MFC: Upgrade to Groff 1.16.1.
@
text
@a4 3
(For instructions how to build groff with DJGPP tools for MS-DOS and
MS-Windows, see the file arch/djgpp/README.)

d25 1
a25 1
  ./test-groff -man -Tascii src/roff/groff/groff.n | less
d27 2
a28 3
If you want to compile and install gxditview (an X11 previewer),
follow the instructions in the INSTALL file in the src/xditview
subdirectory.
d30 3
a32 3
To get PostScript versions of the documentation resp. reference files
for the `me' macros and the `pic' preprocessor, simply say `make' in
the `doc' subdirectory.
@


1.1.1.3.2.2
log
@MFC: Upgrade to Groff 1.17.
@
text
@a21 10
If you want A4 or letter paper format and the configure script produces
an incorrect guess, say

  PAGE=xxx ./configure

where `xxx' should be either `A4' or `letter'.  Note that this will only
affect the paper selection for grops.  For compatibility with ditroff,
the default page length in gtroff is always 11 inches.  The page length
can be changed with the `pl' request.

@


1.1.1.3.2.3
log
@MFC: Groff 1.18.1.
@
text
@d44 3
a46 4
To get a DVI, PDF, or HTML version of the groff texinfo manual, say `make
groff.dvi', `make groff.pdf', or `make groff.html', respectively, in the
`doc' subdirectory (after compiling the groff package).  Note that you
need texinfo version 4.2 or newer as a prerequisite.
@


1.1.1.3.2.4
log
@MFC: GNU Groff 1.19.
@
text
@d9 1
a9 1
source files use a suffix of `.cpp', so your C++ compiler must be able
d47 1
a47 1
need texinfo version 4.3 or newer as a prerequisite.
@


1.1.1.4
log
@Virgin import of FSF groff v1.16.1
@
text
@a4 3
(For instructions how to build groff with DJGPP tools for MS-DOS and
MS-Windows, see the file arch/djgpp/README.)

d25 1
a25 1
  ./test-groff -man -Tascii src/roff/groff/groff.n | less
d27 2
a28 3
If you want to compile and install gxditview (an X11 previewer),
follow the instructions in the INSTALL file in the src/xditview
subdirectory.
d30 3
a32 3
To get PostScript versions of the documentation resp. reference files
for the `me' macros and the `pic' preprocessor, simply say `make' in
the `doc' subdirectory.
@


1.1.1.5
log
@Virgin import of FSF groff v1.17
@
text
@a21 10
If you want A4 or letter paper format and the configure script produces
an incorrect guess, say

  PAGE=xxx ./configure

where `xxx' should be either `A4' or `letter'.  Note that this will only
affect the paper selection for grops.  For compatibility with ditroff,
the default page length in gtroff is always 11 inches.  The page length
can be changed with the `pl' request.

@


1.1.1.6
log
@Virgin import of FSF groff v1.18.1
@
text
@d44 3
a46 4
To get a DVI, PDF, or HTML version of the groff texinfo manual, say `make
groff.dvi', `make groff.pdf', or `make groff.html', respectively, in the
`doc' subdirectory (after compiling the groff package).  Note that you
need texinfo version 4.2 or newer as a prerequisite.
@


1.1.1.7
log
@Virgin import of FSF groff v1.19
@
text
@d9 1
a9 1
source files use a suffix of `.cpp', so your C++ compiler must be able
d47 1
a47 1
need texinfo version 4.3 or newer as a prerequisite.
@


1.1.1.7.12.1
log
@MFC: Groff 1.19.2.
@
text
@a7 3
(For instructions how to build groff with the MinGW tools for
MS-Windows, see the file README.MinGW.)

d28 3
a30 4
affect the paper selection of some device drivers like grops (which can
be still overridden on the command line).  For compatibility with
ditroff, the default page length in gtroff is always 11 inches.  The
page length can be changed with the `pl' request.
d35 2
a36 1
groff to run without being installed.  For example, you could do
d40 4
d46 2
a47 3
`doc' subdirectory (after configuring the groff package).  Note that you
need texinfo version 4.6 as a prerequisite.  Neither older versions nor
texinfo 4.7 (due to a bug) will work.
@


1.1.1.8
log
@Virgin import of FSF groff v1.19.2
@
text
@a7 3
(For instructions how to build groff with the MinGW tools for
MS-Windows, see the file README.MinGW.)

d28 3
a30 4
affect the paper selection of some device drivers like grops (which can
be still overridden on the command line).  For compatibility with
ditroff, the default page length in gtroff is always 11 inches.  The
page length can be changed with the `pl' request.
d35 2
a36 1
groff to run without being installed.  For example, you could do
d40 4
d46 2
a47 3
`doc' subdirectory (after configuring the groff package).  Note that you
need texinfo version 4.6 as a prerequisite.  Neither older versions nor
texinfo 4.7 (due to a bug) will work.
@


1.1.1.8.30.1
log
@file INSTALL was added on branch RELENG_8_4 on 2013-03-28 13:01:12 +0000
@
text
@d1 50
@


1.1.1.8.30.2
log
@## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/248810
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
@
text
@a0 50
To install groff, follow the instructions in the file INSTALL.gen.

This file contains information that supplements those instructions.

(For instructions how to build groff with DJGPP tools for MS-DOS and
MS-Windows, see the file arch/djgpp/README.)

(For instructions how to build groff with the MinGW tools for
MS-Windows, see the file README.MinGW.)

groff is written in C++, so you will need a C++ compiler.  The C++
source files use a suffix of `.cpp', so your C++ compiler must be able
to handle this.  If you don't already have a C++ compiler, I suggest
gcc 2.7.1 or later (gcc version 2 includes GNU C++ as well as GNU C).
From gcc 2.5, it is no longer necessary to install libg++: the C++
header files needed by groff are created by the gcc installation
process.  To override configure's choice of C++ compiler, you can set
the CXX environment variable.

If you have a library that provides a faster malloc than your system's
usual malloc, it is good idea to include it in LIBS.  For example,
using the malloc that comes with GNU Emacs version 20 can give a
worthwhile (and sometimes spectacular) performance improvement.

If you want A4 or letter paper format and the configure script produces
an incorrect guess, say

  PAGE=xxx ./configure

where `xxx' should be either `A4' or `letter'.  Note that this will only
affect the paper selection of some device drivers like grops (which can
be still overridden on the command line).  For compatibility with
ditroff, the default page length in gtroff is always 11 inches.  The
page length can be changed with the `pl' request.

When you have built groff, you can use the test-groff script to try
groff out on one of the man pages.  (Use the .n files not the .man
files.)  The test-groff script sets up environment variables to allow
groff to run without being installed.  For example, you could do

  ./test-groff -man -Tascii src/roff/groff/groff.n | less

To get a DVI, PDF, or HTML version of the groff texinfo manual, say `make
groff.dvi', `make groff.pdf', or `make groff.html', respectively, in the
`doc' subdirectory (after configuring the groff package).  Note that you
need texinfo version 4.6 as a prerequisite.  Neither older versions nor
texinfo 4.7 (due to a bug) will work.

If you have problems, read the PROBLEMS file.  If this doesn't help
send a bug report using the form in the file BUG-REPORT.
@


