Hampa Hug 12 years ago
parent
commit
51d9a1bfe9
2 changed files with 82 additions and 74 deletions
  1. 13
    13
      COPYING
  2. 69
    61
      INSTALL

+ 13
- 13
COPYING View File

@@ -1,8 +1,9 @@
1 1
 		    GNU GENERAL PUBLIC LICENSE
2 2
 		       Version 2, June 1991
3 3
 
4
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.
5
-                       59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
4
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
5
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
6
+
6 7
  Everyone is permitted to copy and distribute verbatim copies
7 8
  of this license document, but changing it is not allowed.
8 9
 
@@ -15,7 +16,7 @@ software--to make sure the software is free for all its users.  This
15 16
 General Public License applies to most of the Free Software
16 17
 Foundation's software and to any other program whose authors commit to
17 18
 using it.  (Some other Free Software Foundation software is covered by
18
-the GNU Library General Public License instead.)  You can apply it to
19
+the GNU Lesser General Public License instead.)  You can apply it to
19 20
 your programs, too.
20 21
 
21 22
   When we speak of free software, we are referring to freedom, not
@@ -55,7 +56,7 @@ patent must be licensed for everyone's free use or not licensed at all.
55 56
 
56 57
   The precise terms and conditions for copying, distribution and
57 58
 modification follow.
58
-
59
+
59 60
 		    GNU GENERAL PUBLIC LICENSE
60 61
    TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
61 62
 
@@ -110,7 +111,7 @@ above, provided that you also meet all of these conditions:
110 111
     License.  (Exception: if the Program itself is interactive but
111 112
     does not normally print such an announcement, your work based on
112 113
     the Program is not required to print an announcement.)
113
-
114
+
114 115
 These requirements apply to the modified work as a whole.  If
115 116
 identifiable sections of that work are not derived from the Program,
116 117
 and can be reasonably considered independent and separate works in
@@ -168,7 +169,7 @@ access to copy from a designated place, then offering equivalent
168 169
 access to copy the source code from the same place counts as
169 170
 distribution of the source code, even though third parties are not
170 171
 compelled to copy the source along with the object code.
171
-
172
+
172 173
   4. You may not copy, modify, sublicense, or distribute the Program
173 174
 except as expressly provided under this License.  Any attempt
174 175
 otherwise to copy, modify, sublicense or distribute the Program is
@@ -225,7 +226,7 @@ impose that choice.
225 226
 
226 227
 This section is intended to make thoroughly clear what is believed to
227 228
 be a consequence of the rest of this License.
228
-
229
+
229 230
   8. If the distribution and/or use of the Program is restricted in
230 231
 certain countries either by patents or by copyrighted interfaces, the
231 232
 original copyright holder who places the Program under this License
@@ -278,7 +279,7 @@ PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
278 279
 POSSIBILITY OF SUCH DAMAGES.
279 280
 
280 281
 		     END OF TERMS AND CONDITIONS
281
-
282
+
282 283
 	    How to Apply These Terms to Your New Programs
283 284
 
284 285
   If you develop a new program, and you want it to be of the greatest
@@ -303,10 +304,9 @@ the "copyright" line and a pointer to where the full notice is found.
303 304
     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
304 305
     GNU General Public License for more details.
305 306
 
306
-    You should have received a copy of the GNU General Public License
307
-    along with this program; if not, write to the Free Software
308
-    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
309
-
307
+    You should have received a copy of the GNU General Public License along
308
+    with this program; if not, write to the Free Software Foundation, Inc.,
309
+    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
310 310
 
311 311
 Also add information on how to contact you by electronic and paper mail.
312 312
 
@@ -336,5 +336,5 @@ necessary.  Here is a sample; alter the names:
336 336
 This General Public License does not permit incorporating your program into
337 337
 proprietary programs.  If your program is a subroutine library, you may
338 338
 consider it more useful to permit linking proprietary applications with the
339
-library.  If this is what you want to do, use the GNU Library General
339
+library.  If this is what you want to do, use the GNU Lesser General
340 340
 Public License instead of this License.

+ 69
- 61
INSTALL View File

@@ -1,7 +1,19 @@
1
+Installation Instructions
2
+*************************
3
+
4
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
5
+2006 Free Software Foundation, Inc.
6
+
7
+This file is free documentation; the Free Software Foundation gives
8
+unlimited permission to copy, distribute and modify it.
9
+
1 10
 Basic Installation
2 11
 ==================
3 12
 
4
-   These are generic installation instructions.
13
+Briefly, the shell commands `./configure; make; make install' should
14
+configure, build, and install this package.  The following
15
+more-detailed instructions are generic; see the `README' file for
16
+instructions specific to this package.
5 17
 
6 18
    The `configure' shell script attempts to guess correct values for
7 19
 various system-dependent variables used during compilation.  It uses
@@ -14,9 +26,9 @@ debugging `configure').
14 26
 
15 27
    It can also use an optional file (typically called `config.cache'
16 28
 and enabled with `--cache-file=config.cache' or simply `-C') that saves
17
-the results of its tests to speed up reconfiguring.  (Caching is
29
+the results of its tests to speed up reconfiguring.  Caching is
18 30
 disabled by default to prevent problems with accidental use of stale
19
-cache files.)
31
+cache files.
20 32
 
21 33
    If you need to do unusual things to compile the package, please try
22 34
 to figure out how `configure' could check whether to do them, and mail
@@ -26,20 +38,17 @@ some point `config.cache' contains results you don't want to keep, you
26 38
 may remove or edit it.
27 39
 
28 40
    The file `configure.ac' (or `configure.in') is used to create
29
-`configure' by a program called `autoconf'.  You only need
30
-`configure.ac' if you want to change it or regenerate `configure' using
31
-a newer version of `autoconf'.
41
+`configure' by a program called `autoconf'.  You need `configure.ac' if
42
+you want to change it or regenerate `configure' using a newer version
43
+of `autoconf'.
32 44
 
33 45
 The simplest way to compile this package is:
34 46
 
35 47
   1. `cd' to the directory containing the package's source code and type
36
-     `./configure' to configure the package for your system.  If you're
37
-     using `csh' on an old version of System V, you might need to type
38
-     `sh ./configure' instead to prevent `csh' from trying to execute
39
-     `configure' itself.
48
+     `./configure' to configure the package for your system.
40 49
 
41
-     Running `configure' takes awhile.  While running, it prints some
42
-     messages telling which features it is checking for.
50
+     Running `configure' might take a while.  While running, it prints
51
+     some messages telling which features it is checking for.
43 52
 
44 53
   2. Type `make' to compile the package.
45 54
 
@@ -61,50 +70,49 @@ The simplest way to compile this package is:
61 70
 Compilers and Options
62 71
 =====================
63 72
 
64
-   Some systems require unusual options for compilation or linking that
65
-the `configure' script does not know about.  Run `./configure --help'
66
-for details on some of the pertinent environment variables.
73
+Some systems require unusual options for compilation or linking that the
74
+`configure' script does not know about.  Run `./configure --help' for
75
+details on some of the pertinent environment variables.
67 76
 
68
-   You can give `configure' initial values for variables by setting
69
-them in the environment.  You can do that on the command line like this:
77
+   You can give `configure' initial values for configuration parameters
78
+by setting variables in the command line or in the environment.  Here
79
+is an example:
70 80
 
71
-     ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
81
+     ./configure CC=c99 CFLAGS=-g LIBS=-lposix
72 82
 
73
-   *Note Environment Variables::, for more details.
83
+   *Note Defining Variables::, for more details.
74 84
 
75 85
 Compiling For Multiple Architectures
76 86
 ====================================
77 87
 
78
-   You can compile the package for more than one kind of computer at the
88
+You can compile the package for more than one kind of computer at the
79 89
 same time, by placing the object files for each architecture in their
80
-own directory.  To do this, you must use a version of `make' that
81
-supports the `VPATH' variable, such as GNU `make'.  `cd' to the
90
+own directory.  To do this, you can use GNU `make'.  `cd' to the
82 91
 directory where you want the object files and executables to go and run
83 92
 the `configure' script.  `configure' automatically checks for the
84 93
 source code in the directory that `configure' is in and in `..'.
85 94
 
86
-   If you have to use a `make' that does not support the `VPATH'
87
-variable, you have to compile the package for one architecture at a time
88
-in the source code directory.  After you have installed the package for
89
-one architecture, use `make distclean' before reconfiguring for another
90
-architecture.
95
+   With a non-GNU `make', it is safer to compile the package for one
96
+architecture at a time in the source code directory.  After you have
97
+installed the package for one architecture, use `make distclean' before
98
+reconfiguring for another architecture.
91 99
 
92 100
 Installation Names
93 101
 ==================
94 102
 
95
-   By default, `make install' will install the package's files in
96
-`/usr/local/bin', `/usr/local/man', etc.  You can specify an
97
-installation prefix other than `/usr/local' by giving `configure' the
98
-option `--prefix=PATH'.
103
+By default, `make install' installs the package's commands under
104
+`/usr/local/bin', include files under `/usr/local/include', etc.  You
105
+can specify an installation prefix other than `/usr/local' by giving
106
+`configure' the option `--prefix=PREFIX'.
99 107
 
100 108
    You can specify separate installation prefixes for
101 109
 architecture-specific files and architecture-independent files.  If you
102
-give `configure' the option `--exec-prefix=PATH', the package will use
103
-PATH as the prefix for installing programs and libraries.
104
-Documentation and other data files will still use the regular prefix.
110
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
111
+PREFIX as the prefix for installing programs and libraries.
112
+Documentation and other data files still use the regular prefix.
105 113
 
106 114
    In addition, if you use an unusual directory layout you can give
107
-options like `--bindir=PATH' to specify different values for particular
115
+options like `--bindir=DIR' to specify different values for particular
108 116
 kinds of files.  Run `configure --help' for a list of the directories
109 117
 you can set and what kinds of files go in them.
110 118
 
@@ -115,7 +123,7 @@ option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
115 123
 Optional Features
116 124
 =================
117 125
 
118
-   Some packages pay attention to `--enable-FEATURE' options to
126
+Some packages pay attention to `--enable-FEATURE' options to
119 127
 `configure', where FEATURE indicates an optional part of the package.
120 128
 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
121 129
 is something like `gnu-as' or `x' (for the X Window System).  The
@@ -130,10 +138,11 @@ you can use the `configure' options `--x-includes=DIR' and
130 138
 Specifying the System Type
131 139
 ==========================
132 140
 
133
-   There may be some features `configure' cannot figure out
134
-automatically, but needs to determine by the type of host the package
135
-will run on.  Usually `configure' can figure that out, but if it prints
136
-a message saying it cannot guess the host type, give it the
141
+There may be some features `configure' cannot figure out automatically,
142
+but needs to determine by the type of machine the package will run on.
143
+Usually, assuming the package is built to be run on the _same_
144
+architectures, `configure' can figure that out, but if it prints a
145
+message saying it cannot guess the machine type, give it the
137 146
 `--build=TYPE' option.  TYPE can either be a short name for the system
138 147
 type, such as `sun4', or a canonical name which has the form:
139 148
 
@@ -141,56 +150,55 @@ type, such as `sun4', or a canonical name which has the form:
141 150
 
142 151
 where SYSTEM can have one of these forms:
143 152
 
144
-     OS
145
-     KERNEL-OS
153
+     OS KERNEL-OS
146 154
 
147 155
    See the file `config.sub' for the possible values of each field.  If
148 156
 `config.sub' isn't included in this package, then this package doesn't
149
-need to know the host type.
157
+need to know the machine type.
150 158
 
151 159
    If you are _building_ compiler tools for cross-compiling, you should
152
-use the `--target=TYPE' option to select the type of system they will
160
+use the option `--target=TYPE' to select the type of system they will
153 161
 produce code for.
154 162
 
155 163
    If you want to _use_ a cross compiler, that generates code for a
156
-platform different from the build platform, you should specify the host
157
-platform (i.e., that on which the generated programs will eventually be
158
-run) with `--host=TYPE'.  In this case, you should also specify the
159
-build platform with `--build=TYPE', because, in this case, it may not
160
-be possible to guess the build platform (it sometimes involves
161
-compiling and running simple test programs, and this can't be done if
162
-the compiler is a cross compiler).
164
+platform different from the build platform, you should specify the
165
+"host" platform (i.e., that on which the generated programs will
166
+eventually be run) with `--host=TYPE'.
163 167
 
164 168
 Sharing Defaults
165 169
 ================
166 170
 
167
-   If you want to set default values for `configure' scripts to share,
168
-you can create a site shell script called `config.site' that gives
169
-default values for variables like `CC', `cache_file', and `prefix'.
171
+If you want to set default values for `configure' scripts to share, you
172
+can create a site shell script called `config.site' that gives default
173
+values for variables like `CC', `cache_file', and `prefix'.
170 174
 `configure' looks for `PREFIX/share/config.site' if it exists, then
171 175
 `PREFIX/etc/config.site' if it exists.  Or, you can set the
172 176
 `CONFIG_SITE' environment variable to the location of the site script.
173 177
 A warning: not all `configure' scripts look for a site script.
174 178
 
175
-Environment Variables
176
-=====================
179
+Defining Variables
180
+==================
177 181
 
178
-   Variables not defined in a site shell script can be set in the
179
-environment passed to configure.  However, some packages may run
182
+Variables not defined in a site shell script can be set in the
183
+environment passed to `configure'.  However, some packages may run
180 184
 configure again during the build, and the customized values of these
181 185
 variables may be lost.  In order to avoid this problem, you should set
182 186
 them in the `configure' command line, using `VAR=value'.  For example:
183 187
 
184 188
      ./configure CC=/usr/local2/bin/gcc
185 189
 
186
-will cause the specified gcc to be used as the C compiler (unless it is
190
+causes the specified `gcc' to be used as the C compiler (unless it is
187 191
 overridden in the site shell script).
188 192
 
193
+Unfortunately, this technique does not work for `CONFIG_SHELL' due to
194
+an Autoconf bug.  Until the bug is fixed you can use this workaround:
195
+
196
+     CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
197
+
189 198
 `configure' Invocation
190 199
 ======================
191 200
 
192
-   `configure' recognizes the following options to control how it
193
-operates.
201
+`configure' recognizes the following options to control how it operates.
194 202
 
195 203
 `--help'
196 204
 `-h'

Loading…
Cancel
Save