texinfo update (Tue Sep 21 08:22:01 EDT 2004)

[Karl Berry]

Index: INSTALL.generic
===================================================================
RCS file: /cvsroot/texinfo/texinfo/INSTALL.generic,v
retrieving revision 1.2
retrieving revision 1.3
diff -c -r1.2 -r1.3
*** INSTALL.generic     24 Sep 2002 00:46:13 -0000      1.2
--- INSTALL.generic     21 Sep 2004 12:20:48 -0000      1.3
***************
*** 1,13 ****
! Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
! Foundation, Inc.
  
!    This file is free documentation; the Free Software Foundation gives
  unlimited permission to copy, distribute and modify it.
  
  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
--- 1,16 ----
! Installation Instructions
! *************************
  
! Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 Free
! Software Foundation, Inc.
! 
! This file is free documentation; the Free Software Foundation gives
  unlimited permission to copy, distribute and modify it.
  
  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
***************
*** 67,75 ****
  Compilers and Options
  =====================
  
!    Some systems require unusual options for compilation or linking that
! the `configure' script does not know about.  Run `./configure --help'
! for details on some of the pertinent environment variables.
  
     You can give `configure' initial values for configuration parameters
  by setting variables in the command line or in the environment.  Here
--- 70,78 ----
  Compilers and Options
  =====================
  
! Some systems require unusual options for compilation or linking that the
! `configure' script does not know about.  Run `./configure --help' for
! details on some of the pertinent environment variables.
  
     You can give `configure' initial values for configuration parameters
  by setting variables in the command line or in the environment.  Here
***************
*** 82,88 ****
  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
--- 85,91 ----
  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
***************
*** 99,117 ****
  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.
  
--- 102,120 ----
  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=PREFIX'.
  
     You can specify separate installation prefixes for
  architecture-specific files and architecture-independent files.  If you
! give `configure' the option `--exec-prefix=PREFIX', the package will
! use PREFIX 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=DIR' 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.
  
***************
*** 122,128 ****
  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
--- 125,131 ----
  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
***************
*** 137,147 ****
  Specifying the System Type
  ==========================
  
!    There may be some features `configure' cannot figure out
! automatically, but needs to determine by the type of machine the package
! will run on.  Usually, assuming the package is built to be run on the
! _same_ architectures, `configure' can figure that out, but if it prints
! a message saying it cannot guess the machine type, give it the
  `--build=TYPE' option.  TYPE can either be a short name for the system
  type, such as `sun4', or a canonical name which has the form:
  
--- 140,150 ----
  Specifying the System Type
  ==========================
  
! There may be some features `configure' cannot figure out automatically,
! but needs to determine by the type of machine the package will run on.
! Usually, assuming the package is built to be run on the _same_
! architectures, `configure' can figure that out, but if it prints a
! message saying it cannot guess the machine type, give it the
  `--build=TYPE' option.  TYPE can either be a short name for the system
  type, such as `sun4', or a canonical name which has the form:
  
***************
*** 167,175 ****
  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.
--- 170,178 ----
  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.
***************
*** 178,184 ****
  Defining Variables
  ==================
  
!    Variables not defined in a site shell script can be set in the
  environment passed to `configure'.  However, some packages may run
  configure again during the build, and the customized values of these
  variables may be lost.  In order to avoid this problem, you should set
--- 181,187 ----
  Defining Variables
  ==================
  
! Variables not defined in a site shell script can be set in the
  environment passed to `configure'.  However, some packages may run
  configure again during the build, and the customized values of these
  variables may be lost.  In order to avoid this problem, you should set
***************
*** 192,199 ****
  `configure' Invocation
  ======================
  
!    `configure' recognizes the following options to control how it
! operates.
  
  `--help'
  `-h'
--- 195,201 ----
  `configure' Invocation
  ======================
  
! `configure' recognizes the following options to control how it operates.
  
  `--help'
  `-h'
P INSTALL.generic