/[make]/make/INSTALL
ViewVC logotype

Diff of /make/INSTALL

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.5 by psmith, Sat Mar 6 08:00:17 2004 UTC revision 1.6 by psmith, Tue Nov 30 20:58:55 2004 UTC
# Line 1  Line 1 
1  Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software  Installation Instructions
2  Foundation, Inc.  *************************
3    
4     This file is free documentation; the Free Software Foundation gives  Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 Free
5    Software Foundation, Inc.
6    
7    This file is free documentation; the Free Software Foundation gives
8  unlimited permission to copy, distribute and modify it.  unlimited permission to copy, distribute and modify it.
9    
10  Basic Installation  Basic Installation
11  ==================  ==================
12    
13     These are generic installation instructions.  These are generic installation instructions.
14    
15     The `configure' shell script attempts to guess correct values for     The `configure' shell script attempts to guess correct values for
16  various system-dependent variables used during compilation.  It uses  various system-dependent variables used during compilation.  It uses
# Line 67  The simplest way to compile this package Line 70  The simplest way to compile this package
70  Compilers and Options  Compilers and Options
71  =====================  =====================
72    
73     Some systems require unusual options for compilation or linking that  Some systems require unusual options for compilation or linking that the
74  the `configure' script does not know about.  Run `./configure --help'  `configure' script does not know about.  Run `./configure --help' for
75  for details on some of the pertinent environment variables.  details on some of the pertinent environment variables.
76    
77     You can give `configure' initial values for configuration parameters     You can give `configure' initial values for configuration parameters
78  by setting variables in the command line or in the environment.  Here  by setting variables in the command line or in the environment.  Here
# Line 82  is an example: Line 85  is an example:
85  Compiling For Multiple Architectures  Compiling For Multiple Architectures
86  ====================================  ====================================
87    
88     You can compile the package for more than one kind of computer at the  You can compile the package for more than one kind of computer at the
89  same time, by placing the object files for each architecture in their  same time, by placing the object files for each architecture in their
90  own directory.  To do this, you must use a version of `make' that  own directory.  To do this, you must use a version of `make' that
91  supports the `VPATH' variable, such as GNU `make'.  `cd' to the  supports the `VPATH' variable, such as GNU `make'.  `cd' to the
# Line 99  for another architecture. Line 102  for another architecture.
102  Installation Names  Installation Names
103  ==================  ==================
104    
105     By default, `make install' will install the package's files in  By default, `make install' will install the package's files in
106  `/usr/local/bin', `/usr/local/man', etc.  You can specify an  `/usr/local/bin', `/usr/local/man', etc.  You can specify an
107  installation prefix other than `/usr/local' by giving `configure' the  installation prefix other than `/usr/local' by giving `configure' the
108  option `--prefix=PATH'.  option `--prefix=PREFIX'.
109    
110     You can specify separate installation prefixes for     You can specify separate installation prefixes for
111  architecture-specific files and architecture-independent files.  If you  architecture-specific files and architecture-independent files.  If you
112  give `configure' the option `--exec-prefix=PATH', the package will use  give `configure' the option `--exec-prefix=PREFIX', the package will
113  PATH as the prefix for installing programs and libraries.  use PREFIX as the prefix for installing programs and libraries.
114  Documentation and other data files will still use the regular prefix.  Documentation and other data files will still use the regular prefix.
115    
116     In addition, if you use an unusual directory layout you can give     In addition, if you use an unusual directory layout you can give
117  options like `--bindir=PATH' to specify different values for particular  options like `--bindir=DIR' to specify different values for particular
118  kinds of files.  Run `configure --help' for a list of the directories  kinds of files.  Run `configure --help' for a list of the directories
119  you can set and what kinds of files go in them.  you can set and what kinds of files go in them.
120    
# Line 122  option `--program-prefix=PREFIX' or `--p Line 125  option `--program-prefix=PREFIX' or `--p
125  Optional Features  Optional Features
126  =================  =================
127    
128     Some packages pay attention to `--enable-FEATURE' options to  Some packages pay attention to `--enable-FEATURE' options to
129  `configure', where FEATURE indicates an optional part of the package.  `configure', where FEATURE indicates an optional part of the package.
130  They may also pay attention to `--with-PACKAGE' options, where PACKAGE  They may also pay attention to `--with-PACKAGE' options, where PACKAGE
131  is something like `gnu-as' or `x' (for the X Window System).  The  is something like `gnu-as' or `x' (for the X Window System).  The
# Line 137  you can use the `configure' options `--x Line 140  you can use the `configure' options `--x
140  Specifying the System Type  Specifying the System Type
141  ==========================  ==========================
142    
143     There may be some features `configure' cannot figure out  There may be some features `configure' cannot figure out automatically,
144  automatically, but needs to determine by the type of machine the package  but needs to determine by the type of machine the package will run on.
145  will run on.  Usually, assuming the package is built to be run on the  Usually, assuming the package is built to be run on the _same_
146  _same_ architectures, `configure' can figure that out, but if it prints  architectures, `configure' can figure that out, but if it prints a
147  a message saying it cannot guess the machine type, give it the  message saying it cannot guess the machine type, give it the
148  `--build=TYPE' option.  TYPE can either be a short name for the system  `--build=TYPE' option.  TYPE can either be a short name for the system
149  type, such as `sun4', or a canonical name which has the form:  type, such as `sun4', or a canonical name which has the form:
150    
# Line 167  eventually be run) with `--host=TYPE'. Line 170  eventually be run) with `--host=TYPE'.
170  Sharing Defaults  Sharing Defaults
171  ================  ================
172    
173     If you want to set default values for `configure' scripts to share,  If you want to set default values for `configure' scripts to share, you
174  you can create a site shell script called `config.site' that gives  can create a site shell script called `config.site' that gives default
175  default values for variables like `CC', `cache_file', and `prefix'.  values for variables like `CC', `cache_file', and `prefix'.
176  `configure' looks for `PREFIX/share/config.site' if it exists, then  `configure' looks for `PREFIX/share/config.site' if it exists, then
177  `PREFIX/etc/config.site' if it exists.  Or, you can set the  `PREFIX/etc/config.site' if it exists.  Or, you can set the
178  `CONFIG_SITE' environment variable to the location of the site script.  `CONFIG_SITE' environment variable to the location of the site script.
# Line 178  A warning: not all `configure' scripts l Line 181  A warning: not all `configure' scripts l
181  Defining Variables  Defining Variables
182  ==================  ==================
183    
184     Variables not defined in a site shell script can be set in the  Variables not defined in a site shell script can be set in the
185  environment passed to `configure'.  However, some packages may run  environment passed to `configure'.  However, some packages may run
186  configure again during the build, and the customized values of these  configure again during the build, and the customized values of these
187  variables may be lost.  In order to avoid this problem, you should set  variables may be lost.  In order to avoid this problem, you should set
# Line 192  overridden in the site shell script). Line 195  overridden in the site shell script).
195  `configure' Invocation  `configure' Invocation
196  ======================  ======================
197    
198     `configure' recognizes the following options to control how it  `configure' recognizes the following options to control how it operates.
 operates.  
199    
200  `--help'  `--help'
201  `-h'  `-h'

Legend:
Removed from v.1.5  
changed lines
  Added in v.1.6

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26