/[path-sandbox]/trunk/INSTALL
Gentoo

Diff of /trunk/INSTALL

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

Revision 363 Revision 364
1Installation Instructions 1Installation Instructions
2************************* 2*************************
3 3
4Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free 4Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
5Software Foundation, Inc. 52006, 2007 Free Software Foundation, Inc.
6 6
7This file is free documentation; the Free Software Foundation gives 7This file is free documentation; the Free Software Foundation gives
8unlimited permission to copy, distribute and modify it. 8unlimited permission to copy, distribute and modify it.
9 9
10Basic Installation 10Basic Installation
11================== 11==================
12 12
13These are generic installation instructions. 13Briefly, the shell commands `./configure; make; make install' should
14configure, build, and install this package. The following
15more-detailed instructions are generic; see the `README' file for
16instructions specific to this package.
14 17
15 The `configure' shell script attempts to guess correct values for 18 The `configure' shell script attempts to guess correct values for
16various system-dependent variables used during compilation. It uses 19various system-dependent variables used during compilation. It uses
17those values to create a `Makefile' in each directory of the package. 20those values to create a `Makefile' in each directory of the package.
18It may also create one or more `.h' files containing system-dependent 21It may also create one or more `.h' files containing system-dependent
21file `config.log' containing compiler output (useful mainly for 24file `config.log' containing compiler output (useful mainly for
22debugging `configure'). 25debugging `configure').
23 26
24 It can also use an optional file (typically called `config.cache' 27 It can also use an optional file (typically called `config.cache'
25and enabled with `--cache-file=config.cache' or simply `-C') that saves 28and enabled with `--cache-file=config.cache' or simply `-C') that saves
26the results of its tests to speed up reconfiguring. (Caching is 29the results of its tests to speed up reconfiguring. Caching is
27disabled by default to prevent problems with accidental use of stale 30disabled by default to prevent problems with accidental use of stale
28cache files.) 31cache files.
29 32
30 If you need to do unusual things to compile the package, please try 33 If you need to do unusual things to compile the package, please try
31to figure out how `configure' could check whether to do them, and mail 34to figure out how `configure' could check whether to do them, and mail
32diffs or instructions to the address given in the `README' so they can 35diffs or instructions to the address given in the `README' so they can
33be considered for the next release. If you are using the cache, and at 36be considered for the next release. If you are using the cache, and at
34some point `config.cache' contains results you don't want to keep, you 37some point `config.cache' contains results you don't want to keep, you
35may remove or edit it. 38may remove or edit it.
36 39
37 The file `configure.ac' (or `configure.in') is used to create 40 The file `configure.ac' (or `configure.in') is used to create
38`configure' by a program called `autoconf'. You only need 41`configure' by a program called `autoconf'. You need `configure.ac' if
39`configure.ac' if you want to change it or regenerate `configure' using 42you want to change it or regenerate `configure' using a newer version
40a newer version of `autoconf'. 43of `autoconf'.
41 44
42The simplest way to compile this package is: 45The simplest way to compile this package is:
43 46
44 1. `cd' to the directory containing the package's source code and type 47 1. `cd' to the directory containing the package's source code and type
45 `./configure' to configure the package for your system. If you're 48 `./configure' to configure the package for your system.
46 using `csh' on an old version of System V, you might need to type
47 `sh ./configure' instead to prevent `csh' from trying to execute
48 `configure' itself.
49 49
50 Running `configure' takes awhile. While running, it prints some 50 Running `configure' might take a while. While running, it prints
51 messages telling which features it is checking for. 51 some messages telling which features it is checking for.
52 52
53 2. Type `make' to compile the package. 53 2. Type `make' to compile the package.
54 54
55 3. Optionally, type `make check' to run any self-tests that come with 55 3. Optionally, type `make check' to run any self-tests that come with
56 the package. 56 the package.
65 also a `make maintainer-clean' target, but that is intended mainly 65 also a `make maintainer-clean' target, but that is intended mainly
66 for the package's developers. If you use it, you may have to get 66 for the package's developers. If you use it, you may have to get
67 all sorts of other programs in order to regenerate files that came 67 all sorts of other programs in order to regenerate files that came
68 with the distribution. 68 with the distribution.
69 69
70 6. Often, you can also type `make uninstall' to remove the installed
71 files again.
72
70Compilers and Options 73Compilers and Options
71===================== 74=====================
72 75
73Some systems require unusual options for compilation or linking that the 76Some systems require unusual options for compilation or linking that the
74`configure' script does not know about. Run `./configure --help' for 77`configure' script does not know about. Run `./configure --help' for
76 79
77 You can give `configure' initial values for configuration parameters 80 You can give `configure' initial values for configuration parameters
78by setting variables in the command line or in the environment. Here 81by setting variables in the command line or in the environment. Here
79is an example: 82is an example:
80 83
81 ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix 84 ./configure CC=c99 CFLAGS=-g LIBS=-lposix
82 85
83 *Note Defining Variables::, for more details. 86 *Note Defining Variables::, for more details.
84 87
85Compiling For Multiple Architectures 88Compiling For Multiple Architectures
86==================================== 89====================================
87 90
88You can compile the package for more than one kind of computer at the 91You can compile the package for more than one kind of computer at the
89same time, by placing the object files for each architecture in their 92same time, by placing the object files for each architecture in their
90own directory. To do this, you must use a version of `make' that 93own directory. To do this, you can use GNU `make'. `cd' to the
91supports the `VPATH' variable, such as GNU `make'. `cd' to the
92directory where you want the object files and executables to go and run 94directory where you want the object files and executables to go and run
93the `configure' script. `configure' automatically checks for the 95the `configure' script. `configure' automatically checks for the
94source code in the directory that `configure' is in and in `..'. 96source code in the directory that `configure' is in and in `..'.
95 97
96 If you have to use a `make' that does not support the `VPATH' 98 With a non-GNU `make', it is safer to compile the package for one
97variable, you have to compile the package for one architecture at a
98time in the source code directory. After you have installed the 99architecture at a time in the source code directory. After you have
99package for one architecture, use `make distclean' before reconfiguring 100installed the package for one architecture, use `make distclean' before
100for another architecture. 101reconfiguring for another architecture.
101 102
102Installation Names 103Installation Names
103================== 104==================
104 105
105By default, `make install' installs the package's commands under 106By default, `make install' installs the package's commands under
188them in the `configure' command line, using `VAR=value'. For example: 189them in the `configure' command line, using `VAR=value'. For example:
189 190
190 ./configure CC=/usr/local2/bin/gcc 191 ./configure CC=/usr/local2/bin/gcc
191 192
192causes the specified `gcc' to be used as the C compiler (unless it is 193causes the specified `gcc' to be used as the C compiler (unless it is
193overridden in the site shell script). Here is a another example: 194overridden in the site shell script).
194 195
195 /bin/bash ./configure CONFIG_SHELL=/bin/bash 196Unfortunately, this technique does not work for `CONFIG_SHELL' due to
197an Autoconf bug. Until the bug is fixed you can use this workaround:
196 198
197Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent 199 CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
198configuration-related scripts to be executed by `/bin/bash'.
199 200
200`configure' Invocation 201`configure' Invocation
201====================== 202======================
202 203
203`configure' recognizes the following options to control how it operates. 204`configure' recognizes the following options to control how it operates.

Legend:
Removed from v.363  
changed lines
  Added in v.364

  ViewVC Help
Powered by ViewVC 1.1.20