head	1.1;
branch	1.1.1;
access;
symbols
	RELENG_8_4:1.1.1.4.0.42
	RELENG_9_1_0_RELEASE:1.1.1.4
	RELENG_9_1:1.1.1.4.0.40
	RELENG_9_1_BP:1.1.1.4
	RELENG_8_3_0_RELEASE:1.1.1.4
	RELENG_8_3:1.1.1.4.0.38
	RELENG_8_3_BP:1.1.1.4
	RELENG_9_0_0_RELEASE:1.1.1.4
	RELENG_9_0:1.1.1.4.0.36
	RELENG_9_0_BP:1.1.1.4
	RELENG_9:1.1.1.4.0.34
	RELENG_9_BP:1.1.1.4
	RELENG_7_4_0_RELEASE:1.1.1.4
	RELENG_8_2_0_RELEASE:1.1.1.4
	RELENG_7_4:1.1.1.4.0.32
	RELENG_7_4_BP:1.1.1.4
	RELENG_8_2:1.1.1.4.0.30
	RELENG_8_2_BP:1.1.1.4
	RELENG_8_1_0_RELEASE:1.1.1.4
	RELENG_8_1:1.1.1.4.0.28
	RELENG_8_1_BP:1.1.1.4
	RELENG_7_3_0_RELEASE:1.1.1.4
	RELENG_7_3:1.1.1.4.0.26
	RELENG_7_3_BP:1.1.1.4
	RELENG_8_0_0_RELEASE:1.1.1.4
	RELENG_8_0:1.1.1.4.0.24
	RELENG_8_0_BP:1.1.1.4
	RELENG_8:1.1.1.4.0.22
	RELENG_8_BP:1.1.1.4
	RELENG_7_2_0_RELEASE:1.1.1.4
	RELENG_7_2:1.1.1.4.0.20
	RELENG_7_2_BP:1.1.1.4
	RELENG_7_1_0_RELEASE:1.1.1.4
	RELENG_6_4_0_RELEASE:1.1.1.4
	RELENG_7_1:1.1.1.4.0.18
	RELENG_7_1_BP:1.1.1.4
	RELENG_6_4:1.1.1.4.0.16
	RELENG_6_4_BP:1.1.1.4
	RELENG_7_0_0_RELEASE:1.1.1.4
	RELENG_6_3_0_RELEASE:1.1.1.4
	RELENG_7_0:1.1.1.4.0.14
	RELENG_7_0_BP:1.1.1.4
	RELENG_6_3:1.1.1.4.0.12
	RELENG_6_3_BP:1.1.1.4
	RELENG_7:1.1.1.4.0.10
	RELENG_7_BP:1.1.1.4
	RELENG_6_2_0_RELEASE:1.1.1.4
	RELENG_6_2:1.1.1.4.0.8
	RELENG_6_2_BP:1.1.1.4
	RELENG_5_5_0_RELEASE:1.1.1.3
	RELENG_5_5:1.1.1.3.0.12
	RELENG_5_5_BP:1.1.1.3
	RELENG_6_1_0_RELEASE:1.1.1.4
	RELENG_6_1:1.1.1.4.0.6
	RELENG_6_1_BP:1.1.1.4
	RELENG_6_0_0_RELEASE:1.1.1.4
	RELENG_6_0:1.1.1.4.0.4
	RELENG_6_0_BP:1.1.1.4
	RELENG_6:1.1.1.4.0.2
	RELENG_6_BP:1.1.1.4
	v4_8:1.1.1.4
	RELENG_5_4_0_RELEASE:1.1.1.3
	RELENG_5_4:1.1.1.3.0.10
	RELENG_5_4_BP:1.1.1.3
	RELENG_4_11_0_RELEASE:1.1.1.1.8.2
	RELENG_4_11:1.1.1.1.8.2.0.6
	RELENG_4_11_BP:1.1.1.1.8.2
	RELENG_5_3_0_RELEASE:1.1.1.3
	RELENG_5_3:1.1.1.3.0.8
	RELENG_5_3_BP:1.1.1.3
	RELENG_5:1.1.1.3.0.6
	RELENG_5_BP:1.1.1.3
	RELENG_4_10_0_RELEASE:1.1.1.1.8.2
	RELENG_4_10:1.1.1.1.8.2.0.4
	RELENG_4_10_BP:1.1.1.1.8.2
	RELENG_5_2_1_RELEASE:1.1.1.3
	RELENG_5_2_0_RELEASE:1.1.1.3
	RELENG_5_2:1.1.1.3.0.4
	RELENG_5_2_BP:1.1.1.3
	RELENG_4_9_0_RELEASE:1.1.1.1.8.2
	RELENG_4_9:1.1.1.1.8.2.0.2
	RELENG_4_9_BP:1.1.1.1.8.2
	v4_6:1.1.1.3
	RELENG_5_1_0_RELEASE:1.1.1.3
	RELENG_5_1:1.1.1.3.0.2
	RELENG_5_1_BP:1.1.1.3
	v4_5:1.1.1.3
	RELENG_4_8_0_RELEASE:1.1.1.1.8.1
	RELENG_4_8:1.1.1.1.8.1.0.6
	RELENG_4_8_BP:1.1.1.1.8.1
	RELENG_5_0_0_RELEASE:1.1.1.2
	RELENG_5_0:1.1.1.2.0.2
	RELENG_5_0_BP:1.1.1.2
	RELENG_4_7_0_RELEASE:1.1.1.1.8.1
	RELENG_4_7:1.1.1.1.8.1.0.4
	RELENG_4_7_BP:1.1.1.1.8.1
	RELENG_4_6_2_RELEASE:1.1.1.1.8.1
	v4_2:1.1.1.2
	RELENG_4_6_1_RELEASE:1.1.1.1.8.1
	RELENG_4_6_0_RELEASE:1.1.1.1.8.1
	RELENG_4_6:1.1.1.1.8.1.0.2
	RELENG_4_6_BP:1.1.1.1.8.1
	v4_1:1.1.1.2
	RELENG_4_5_0_RELEASE:1.1.1.1
	RELENG_4_5:1.1.1.1.0.14
	RELENG_4_5_BP:1.1.1.1
	RELENG_4_4_0_RELEASE:1.1.1.1
	RELENG_4_4:1.1.1.1.0.12
	RELENG_4_4_BP:1.1.1.1
	RELENG_4_3_0_RELEASE:1.1.1.1
	RELENG_4_3:1.1.1.1.0.10
	RELENG_4_3_BP:1.1.1.1
	RELENG_4_2_0_RELEASE:1.1.1.1
	RELENG_4_1_1_RELEASE:1.1.1.1
	PRE_SMPNG:1.1.1.1
	RELENG_4_1_0_RELEASE:1.1.1.1
	RELENG_3_5_0_RELEASE:1.1.1.1
	RELENG_4_0_0_RELEASE:1.1.1.1
	RELENG_4:1.1.1.1.0.8
	RELENG_4_BP:1.1.1.1
	v4_0:1.1.1.1
	FSF:1.1.1
	RELENG_3_4_0_RELEASE:1.1.1.1
	RELENG_3_3_0_RELEASE:1.1.1.1
	RELENG_3_2_PAO:1.1.1.1.0.6
	RELENG_3_2_PAO_BP:1.1.1.1
	RELENG_3_2_0_RELEASE:1.1.1.1
	RELENG_3_1_0_RELEASE:1.1.1.1
	RELENG_3:1.1.1.1.0.4
	RELENG_3_BP:1.1.1.1
	gnu_texinfo_3_12: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.1.1.1.0.2
	gnu_texinfo_3_9:1.1.1.1
	KBERRY:1.1.1;
locks; strict;
comment	@# @;


1.1
date	97.01.11.02.12.30;	author jmacd;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	97.01.11.02.12.30;	author jmacd;	state Exp;
branches
	1.1.1.1.8.1;
next	1.1.1.2;

1.1.1.2
date	2002.03.25.13.08.28;	author ru;	state Exp;
branches;
next	1.1.1.3;

1.1.1.3
date	2003.05.02.00.48.41;	author ru;	state Exp;
branches;
next	1.1.1.4;

1.1.1.4
date	2005.05.23.10.46.22;	author ru;	state Exp;
branches
	1.1.1.4.42.1;
next	;

1.1.1.1.8.1
date	2002.03.30.17.09.08;	author ru;	state Exp;
branches;
next	1.1.1.1.8.2;

1.1.1.1.8.2
date	2003.06.26.09.05.48;	author ru;	state Exp;
branches;
next	;

1.1.1.4.42.1
date	2005.05.23.10.46.22;	author svnexp;	state dead;
branches;
next	1.1.1.4.42.2;

1.1.1.4.42.2
date	2013.03.28.13.02.08;	author svnexp;	state Exp;
branches;
next	;


desc
@@


1.1
log
@Initial revision
@
text
@Basic Installation
==================

   These are generic installation instructions.

   The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation.  It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions.  Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').

   If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release.  If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.

   The file `configure.in' is used to create `configure' by a program
called `autoconf'.  You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.

The simplest way to compile this package is:

  1. `cd' to the directory containing the package's source code and type
     `./configure' to configure the package for your system.  If you're
     using `csh' on an old version of System V, you might need to type
     `sh ./configure' instead to prevent `csh' from trying to execute
     `configure' itself.

     Running `configure' takes awhile.  While running, it prints some
     messages telling which features it is checking for.

  2. Type `make' to compile the package.

  3. Optionally, type `make check' to run any self-tests that come with
     the package.

  4. Type `make install' to install the programs and any data files and
     documentation.

  5. You can remove the program binaries and object files from the
     source code directory by typing `make clean'.  To also remove the
     files that `configure' created (so you can compile the package for
     a different kind of computer), type `make distclean'.  There is
     also a `make maintainer-clean' target, but that is intended mainly
     for the package's developers.  If you use it, you may have to get
     all sorts of other programs in order to regenerate files that came
     with the distribution.

Compilers and Options
=====================

   Some systems require unusual options for compilation or linking that
the `configure' script does not know about.  You can give `configure'
initial values for variables by setting them in the environment.  Using
a Bourne-compatible shell, you can do that on the command line like
this:
     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

Or on systems that have the `env' program, you can do it like this:
     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure

Compiling For Multiple Architectures
====================================

   You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory.  To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'.  `cd' to the
directory where you want the object files and executables to go and run
the `configure' script.  `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

   If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory.  After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.

Installation Names
==================

   By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc.  You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.

   You can specify separate installation prefixes for
architecture-specific files and architecture-independent files.  If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

   In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files.  Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.

   If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features
=================

   Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System).  The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

   For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type
==========================

   There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on.  Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option.  TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
     CPU-COMPANY-SYSTEM

See the file `config.sub' for the possible values of each field.  If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.

   If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.

Sharing Defaults
================

   If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists.  Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.

Operation Controls
==================

   `configure' recognizes the following options to control how it
operates.

`--cache-file=FILE'
     Use and save the results of the tests in FILE instead of
     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
     debugging `configure'.

`--help'
     Print a summary of the options to `configure', and exit.

`--quiet'
`--silent'
`-q'
     Do not print messages saying which checks are being made.

`--srcdir=DIR'
     Look for the package's source code in directory DIR.  Usually
     `configure' can determine that directory automatically.

`--version'
     Print the version of Autoconf used to generate the `configure'
     script, and exit.

`configure' also accepts some other, not widely useful, options.

@


1.1.1.1
log
@This is unmodified GNU texinfo-3.9 source.  I'll be commiting a few
patches in a bit.

-josh
@
text
@@


1.1.1.1.8.1
log
@MFC: GNU texinfo 4.1 import.
@
text
@d170 1
a170 3
     Do not print messages saying which checks are being made.  To
     suppress all normal output, redirect it to `/dev/null' (any error
     messages will still be shown).
@


1.1.1.1.8.2
log
@MFC: GNU texinfo 4.6.
@
text
@d1 2
a2 1
$Id: INSTALL,v 1.2 2002/09/11 16:32:09 karl Exp $
d4 1
a4 3
     Copying and distribution of this file, with or without modification,
     are permitted in any medium without royalty provided the copyright
     notice and this notice are preserved.
d6 175
a180 2
For generic installation instructions on compiling and installing this
Automake-based distribution, please read the file `INSTALL.generic'.
d182 1
a182 1
Installation notes specific to Texinfo:
a183 16
* The Info tree uses a file `dir' as its root node; the `dir-example'
  file in this distribution is included as a possible starting point.
  Use it, modify it, or ignore it just as you like.

* You can create a file texinfo.cnf to be read by TeX when
  processing Texinfo manuals.  For example, you might like to use
  @@afourpaper by default.  See the `Preparing for TeX' node in
  texinfo.txi for more details.  You don't have to create the file if
  you have nothing to put in it.

* If your info files are not in $prefix/info, you may wish to add a line
#define DEFAULT_INFOPATH "/mydir1:/mydir2:..."
  to config.h after running configure.

* For instructions on compiling this distribution with DJGPP tools
  for MS-DOS and MS-Windows, see the file djgpp/README.
@


1.1.1.2
log
@Import of stripped down GNU texinfo 4.1
@
text
@d170 1
a170 3
     Do not print messages saying which checks are being made.  To
     suppress all normal output, redirect it to `/dev/null' (any error
     messages will still be shown).
@


1.1.1.3
log
@Import of stripped down GNU texinfo 4.5
@
text
@d1 2
a2 1
$Id: INSTALL,v 1.2 2002/09/11 16:32:09 karl Exp $
d4 1
a4 3
     Copying and distribution of this file, with or without modification,
     are permitted in any medium without royalty provided the copyright
     notice and this notice are preserved.
d6 175
a180 2
For generic installation instructions on compiling and installing this
Automake-based distribution, please read the file `INSTALL.generic'.
d182 1
a182 1
Installation notes specific to Texinfo:
a183 16
* The Info tree uses a file `dir' as its root node; the `dir-example'
  file in this distribution is included as a possible starting point.
  Use it, modify it, or ignore it just as you like.

* You can create a file texinfo.cnf to be read by TeX when
  processing Texinfo manuals.  For example, you might like to use
  @@afourpaper by default.  See the `Preparing for TeX' node in
  texinfo.txi for more details.  You don't have to create the file if
  you have nothing to put in it.

* If your info files are not in $prefix/info, you may wish to add a line
#define DEFAULT_INFOPATH "/mydir1:/mydir2:..."
  to config.h after running configure.

* For instructions on compiling this distribution with DJGPP tools
  for MS-DOS and MS-Windows, see the file djgpp/README.
@


1.1.1.4
log
@Import of stripped down GNU texinfo 4.8
@
text
@d1 1
a1 1
$Id: INSTALL,v 1.5 2004/11/19 13:08:47 karl Exp $
a11 21
* texinfo.tex and the other *.tex files are not installed by `make
  install'.  This is because there is no reliable way to know where to
  install them.  Instead, you have to run an additional make command
  after the normal make install:
    make TEXMF=/your/texmf install-tex
  texinfo.tex is installed in ${TEXMF}/tex/texinfo/texinfo.tex, etc.

* On the other hand, if you're maintaining a TeX distribution, you don't
  want your users to see the installation warnings, because you already
  have the files installed.  (And you're keeping them up to date, right?)
  In this case, run configure --disable-install-warnings, or set
  enable_install_warnings=no in the environment.

* On MacOSX, if configure fails with the error:
	ac_cv_build='config.sub: invalid option -apple-darwin7.2.0
this is probably because your uname -p is returning "unknown".  Use
/usr/bin/uname instead.

* For instructions on compiling this distribution with DJGPP tools
  for MS-DOS and MS-Windows, see the file djgpp/README.

d25 3
@


1.1.1.4.42.1
log
@file INSTALL was added on branch RELENG_8_4 on 2013-03-28 13:02:08 +0000
@
text
@d1 45
@


1.1.1.4.42.2
log
@## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/248810
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
@
text
@a0 45
$Id: INSTALL,v 1.5 2004/11/19 13:08:47 karl Exp $

     Copying and distribution of this file, with or without modification,
     are permitted in any medium without royalty provided the copyright
     notice and this notice are preserved.

For generic installation instructions on compiling and installing this
Automake-based distribution, please read the file `INSTALL.generic'.

Installation notes specific to Texinfo:

* texinfo.tex and the other *.tex files are not installed by `make
  install'.  This is because there is no reliable way to know where to
  install them.  Instead, you have to run an additional make command
  after the normal make install:
    make TEXMF=/your/texmf install-tex
  texinfo.tex is installed in ${TEXMF}/tex/texinfo/texinfo.tex, etc.

* On the other hand, if you're maintaining a TeX distribution, you don't
  want your users to see the installation warnings, because you already
  have the files installed.  (And you're keeping them up to date, right?)
  In this case, run configure --disable-install-warnings, or set
  enable_install_warnings=no in the environment.

* On MacOSX, if configure fails with the error:
	ac_cv_build='config.sub: invalid option -apple-darwin7.2.0
this is probably because your uname -p is returning "unknown".  Use
/usr/bin/uname instead.

* For instructions on compiling this distribution with DJGPP tools
  for MS-DOS and MS-Windows, see the file djgpp/README.

* The Info tree uses a file `dir' as its root node; the `dir-example'
  file in this distribution is included as a possible starting point.
  Use it, modify it, or ignore it just as you like.

* You can create a file texinfo.cnf to be read by TeX when
  processing Texinfo manuals.  For example, you might like to use
  @@afourpaper by default.  See the `Preparing for TeX' node in
  texinfo.txi for more details.  You don't have to create the file if
  you have nothing to put in it.

* If your info files are not in $prefix/info, you may wish to add a line
#define DEFAULT_INFOPATH "/mydir1:/mydir2:..."
  to config.h after running configure.
@


