1
0

patch-INSTALL 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277
  1. $Id: update-patches 24 2008-08-31 14:56:13Z wbx $
  2. --- cgilib-0.7.orig/INSTALL 2009-02-08 15:13:57.000000000 +0100
  3. +++ cgilib-0.7/INSTALL 2009-05-09 03:58:09.000000000 +0200
  4. @@ -1,56 +1,236 @@
  5. Installation Instructions
  6. -=========================
  7. +*************************
  8. -The version control system does not contain all files required to
  9. -compile this project. This is intentional.
  10. +Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
  11. +Software Foundation, Inc.
  12. -These files will be added before releasing a new version of the
  13. -package outside of the version control system.
  14. +This file is free documentation; the Free Software Foundation gives
  15. +unlimited permission to copy, distribute and modify it.
  16. -Compiling from Source
  17. ----------------------
  18. +Basic Installation
  19. +==================
  20. -To compile this package you'll have to execute the following two
  21. -commands:
  22. +These are generic installation instructions.
  23. -./configure
  24. -make
  25. + The `configure' shell script attempts to guess correct values for
  26. +various system-dependent variables used during compilation. It uses
  27. +those values to create a `Makefile' in each directory of the package.
  28. +It may also create one or more `.h' files containing system-dependent
  29. +definitions. Finally, it creates a shell script `config.status' that
  30. +you can run in the future to recreate the current configuration, and a
  31. +file `config.log' containing compiler output (useful mainly for
  32. +debugging `configure').
  33. -Compiling from CVS
  34. -------------------
  35. + It can also use an optional file (typically called `config.cache'
  36. +and enabled with `--cache-file=config.cache' or simply `-C') that saves
  37. +the results of its tests to speed up reconfiguring. (Caching is
  38. +disabled by default to prevent problems with accidental use of stale
  39. +cache files.)
  40. -Before you can compile this project you'll have to install the
  41. -following packages:
  42. + If you need to do unusual things to compile the package, please try
  43. +to figure out how `configure' could check whether to do them, and mail
  44. +diffs or instructions to the address given in the `README' so they can
  45. +be considered for the next release. If you are using the cache, and at
  46. +some point `config.cache' contains results you don't want to keep, you
  47. +may remove or edit it.
  48. - . autoconf
  49. - . automake
  50. - . libtool
  51. + The file `configure.ac' (or `configure.in') is used to create
  52. +`configure' by a program called `autoconf'. You only need
  53. +`configure.ac' if you want to change it or regenerate `configure' using
  54. +a newer version of `autoconf'.
  55. -Once installed you'll have to execute the following commands:
  56. +The simplest way to compile this package is:
  57. -aclocal
  58. -autoconf
  59. -libtoolize --force
  60. -automake --add-missing --foreign
  61. + 1. `cd' to the directory containing the package's source code and type
  62. + `./configure' to configure the package for your system. If you're
  63. + using `csh' on an old version of System V, you might need to type
  64. + `sh ./configure' instead to prevent `csh' from trying to execute
  65. + `configure' itself.
  66. -Now ./configure is generated and needs to be executed.
  67. + Running `configure' takes awhile. While running, it prints some
  68. + messages telling which features it is checking for.
  69. -Preparing a release
  70. --------------------
  71. + 2. Type `make' to compile the package.
  72. -After the final commit, edit configure.ac and adjust the package version.
  73. -Run the following commands:
  74. + 3. Optionally, type `make check' to run any self-tests that come with
  75. + the package.
  76. -aclocal
  77. -autoconf
  78. -libtoolize --force --copy
  79. -automake --copy --add-missing --foreign
  80. + 4. Type `make install' to install the programs and any data files and
  81. + documentation.
  82. -Before building the final release tarball some files may be removed.
  83. + 5. You can remove the program binaries and object files from the
  84. + source code directory by typing `make clean'. To also remove the
  85. + files that `configure' created (so you can compile the package for
  86. + a different kind of computer), type `make distclean'. There is
  87. + also a `make maintainer-clean' target, but that is intended mainly
  88. + for the package's developers. If you use it, you may have to get
  89. + all sorts of other programs in order to regenerate files that came
  90. + with the distribution.
  91. -After a normal build run, execute:
  92. +Compilers and Options
  93. +=====================
  94. -make distclean
  95. -rm -rf autom4te.cache
  96. -rm -f aclocal.m4
  97. +Some systems require unusual options for compilation or linking that the
  98. +`configure' script does not know about. Run `./configure --help' for
  99. +details on some of the pertinent environment variables.
  100. +
  101. + You can give `configure' initial values for configuration parameters
  102. +by setting variables in the command line or in the environment. Here
  103. +is an example:
  104. +
  105. + ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
  106. +
  107. + *Note Defining Variables::, for more details.
  108. +
  109. +Compiling For Multiple Architectures
  110. +====================================
  111. +
  112. +You can compile the package for more than one kind of computer at the
  113. +same time, by placing the object files for each architecture in their
  114. +own directory. To do this, you must use a version of `make' that
  115. +supports the `VPATH' variable, such as GNU `make'. `cd' to the
  116. +directory where you want the object files and executables to go and run
  117. +the `configure' script. `configure' automatically checks for the
  118. +source code in the directory that `configure' is in and in `..'.
  119. +
  120. + If you have to use a `make' that does not support the `VPATH'
  121. +variable, you have to compile the package for one architecture at a
  122. +time in the source code directory. After you have installed the
  123. +package for one architecture, use `make distclean' before reconfiguring
  124. +for another architecture.
  125. +
  126. +Installation Names
  127. +==================
  128. +
  129. +By default, `make install' installs the package's commands under
  130. +`/usr/local/bin', include files under `/usr/local/include', etc. You
  131. +can specify an installation prefix other than `/usr/local' by giving
  132. +`configure' the option `--prefix=PREFIX'.
  133. +
  134. + You can specify separate installation prefixes for
  135. +architecture-specific files and architecture-independent files. If you
  136. +pass the option `--exec-prefix=PREFIX' to `configure', the package uses
  137. +PREFIX as the prefix for installing programs and libraries.
  138. +Documentation and other data files still use the regular prefix.
  139. +
  140. + In addition, if you use an unusual directory layout you can give
  141. +options like `--bindir=DIR' to specify different values for particular
  142. +kinds of files. Run `configure --help' for a list of the directories
  143. +you can set and what kinds of files go in them.
  144. +
  145. + If the package supports it, you can cause programs to be installed
  146. +with an extra prefix or suffix on their names by giving `configure' the
  147. +option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
  148. +
  149. +Optional Features
  150. +=================
  151. +
  152. +Some packages pay attention to `--enable-FEATURE' options to
  153. +`configure', where FEATURE indicates an optional part of the package.
  154. +They may also pay attention to `--with-PACKAGE' options, where PACKAGE
  155. +is something like `gnu-as' or `x' (for the X Window System). The
  156. +`README' should mention any `--enable-' and `--with-' options that the
  157. +package recognizes.
  158. +
  159. + For packages that use the X Window System, `configure' can usually
  160. +find the X include and library files automatically, but if it doesn't,
  161. +you can use the `configure' options `--x-includes=DIR' and
  162. +`--x-libraries=DIR' to specify their locations.
  163. +
  164. +Specifying the System Type
  165. +==========================
  166. +
  167. +There may be some features `configure' cannot figure out automatically,
  168. +but needs to determine by the type of machine the package will run on.
  169. +Usually, assuming the package is built to be run on the _same_
  170. +architectures, `configure' can figure that out, but if it prints a
  171. +message saying it cannot guess the machine type, give it the
  172. +`--build=TYPE' option. TYPE can either be a short name for the system
  173. +type, such as `sun4', or a canonical name which has the form:
  174. +
  175. + CPU-COMPANY-SYSTEM
  176. +
  177. +where SYSTEM can have one of these forms:
  178. +
  179. + OS KERNEL-OS
  180. +
  181. + See the file `config.sub' for the possible values of each field. If
  182. +`config.sub' isn't included in this package, then this package doesn't
  183. +need to know the machine type.
  184. +
  185. + If you are _building_ compiler tools for cross-compiling, you should
  186. +use the option `--target=TYPE' to select the type of system they will
  187. +produce code for.
  188. +
  189. + If you want to _use_ a cross compiler, that generates code for a
  190. +platform different from the build platform, you should specify the
  191. +"host" platform (i.e., that on which the generated programs will
  192. +eventually be run) with `--host=TYPE'.
  193. +
  194. +Sharing Defaults
  195. +================
  196. +
  197. +If you want to set default values for `configure' scripts to share, you
  198. +can create a site shell script called `config.site' that gives default
  199. +values for variables like `CC', `cache_file', and `prefix'.
  200. +`configure' looks for `PREFIX/share/config.site' if it exists, then
  201. +`PREFIX/etc/config.site' if it exists. Or, you can set the
  202. +`CONFIG_SITE' environment variable to the location of the site script.
  203. +A warning: not all `configure' scripts look for a site script.
  204. +
  205. +Defining Variables
  206. +==================
  207. +
  208. +Variables not defined in a site shell script can be set in the
  209. +environment passed to `configure'. However, some packages may run
  210. +configure again during the build, and the customized values of these
  211. +variables may be lost. In order to avoid this problem, you should set
  212. +them in the `configure' command line, using `VAR=value'. For example:
  213. +
  214. + ./configure CC=/usr/local2/bin/gcc
  215. +
  216. +causes the specified `gcc' to be used as the C compiler (unless it is
  217. +overridden in the site shell script). Here is a another example:
  218. +
  219. + /bin/bash ./configure CONFIG_SHELL=/bin/bash
  220. +
  221. +Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
  222. +configuration-related scripts to be executed by `/bin/bash'.
  223. +
  224. +`configure' Invocation
  225. +======================
  226. +
  227. +`configure' recognizes the following options to control how it operates.
  228. +
  229. +`--help'
  230. +`-h'
  231. + Print a summary of the options to `configure', and exit.
  232. +
  233. +`--version'
  234. +`-V'
  235. + Print the version of Autoconf used to generate the `configure'
  236. + script, and exit.
  237. +
  238. +`--cache-file=FILE'
  239. + Enable the cache: use and save the results of the tests in FILE,
  240. + traditionally `config.cache'. FILE defaults to `/dev/null' to
  241. + disable caching.
  242. +
  243. +`--config-cache'
  244. +`-C'
  245. + Alias for `--cache-file=config.cache'.
  246. +
  247. +`--quiet'
  248. +`--silent'
  249. +`-q'
  250. + Do not print messages saying which checks are being made. To
  251. + suppress all normal output, redirect it to `/dev/null' (any error
  252. + messages will still be shown).
  253. +
  254. +`--srcdir=DIR'
  255. + Look for the package's source code in directory DIR. Usually
  256. + `configure' can determine that directory automatically.
  257. +
  258. +`configure' also accepts some other, not widely useful, options. Run
  259. +`configure --help' for more details.