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