123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277 |
- $Id: update-patches 24 2008-08-31 14:56:13Z wbx $
- --- cgilib-0.7.orig/INSTALL 2009-02-08 15:13:57.000000000 +0100
- +++ cgilib-0.7/INSTALL 2009-05-09 03:58:09.000000000 +0200
- @@ -1,56 +1,236 @@
- Installation Instructions
- -=========================
- +*************************
-
- -The version control system does not contain all files required to
- -compile this project. This is intentional.
- +Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
- +Software Foundation, Inc.
-
- -These files will be added before releasing a new version of the
- -package outside of the version control system.
- +This file is free documentation; the Free Software Foundation gives
- +unlimited permission to copy, distribute and modify it.
-
- -Compiling from Source
- ----------------------
- +Basic Installation
- +==================
-
- -To compile this package you
- -commands:
- +These are generic installation instructions.
-
- -./configure
- -make
- + The `configure
- +various system-dependent variables used during compilation. It uses
- +those values to create a `Makefile
- +It may also create one or more `.h
- +definitions. Finally, it creates a shell script `config.status
- +you can run in the future to recreate the current configuration, and a
- +file `config.log
- +debugging `configure
-
- -Compiling from CVS
- -------------------
- + It can also use an optional file (typically called `config.cache
- +and enabled with `--cache-file=config.cache
- +the results of its tests to speed up reconfiguring. (Caching is
- +disabled by default to prevent problems with accidental use of stale
- +cache files.)
-
- -Before you can compile this project you
- -following packages:
- + If you need to do unusual things to compile the package, please try
- +to figure out how `configure
- +diffs or instructions to the address given in the `README
- +be considered for the next release. If you are using the cache, and at
- +some point `config.cache
- +may remove or edit it.
-
- - . autoconf
- - . automake
- - . libtool
- + The file `configure.ac
- +`configure
- +`configure.ac
- +a newer version of `autoconf
-
- -Once installed you
- +The simplest way to compile this package is:
-
- -aclocal
- -autoconf
- -libtoolize --force
- -automake --add-missing --foreign
- + 1. `cd
- + `./configure
- + using `csh
- + `sh ./configure
- + `configure
-
- -Now ./configure is generated and needs to be executed.
- + Running `configure
- + messages telling which features it is checking for.
-
- -Preparing a release
- --------------------
- + 2. Type `make
-
- -After the final commit, edit configure.ac and adjust the package version.
- -Run the following commands:
- + 3. Optionally, type `make check
- + the package.
-
- -aclocal
- -autoconf
- -libtoolize --force --copy
- -automake --copy --add-missing --foreign
- + 4. Type `make install
- + documentation.
-
- -Before building the final release tarball some files may be removed.
- + 5. You can remove the program binaries and object files from the
- + source code directory by typing `make clean
- + files that `configure
- + a different kind of computer), type `make distclean
- + also a `make maintainer-clean
- + for the package
- + all sorts of other programs in order to regenerate files that came
- + with the distribution.
-
- -After a normal build run, execute:
- +Compilers and Options
- +=====================
-
- -make distclean
- -rm -rf autom4te.cache
- -rm -f aclocal.m4
- +Some systems require unusual options for compilation or linking that the
- +`configure
- +details on some of the pertinent environment variables.
- +
- + You can give `configure
- +by setting variables in the command line or in the environment. Here
- +is an example:
- +
- + ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
- +
- + *Note Defining Variables::, for more details.
- +
- +Compiling For Multiple Architectures
- +====================================
- +
- +You can compile the package for more than one kind of computer at the
- +same time, by placing the object files for each architecture in their
- +own directory. To do this, you must use a version of `make
- +supports the `VPATH
- +directory where you want the object files and executables to go and run
- +the `configure
- +source code in the directory that `configure
- +
- + If you have to use a `make
- +variable, you have to compile the package for one architecture at a
- +time in the source code directory. After you have installed the
- +package for one architecture, use `make distclean
- +for another architecture.
- +
- +Installation Names
- +==================
- +
- +By default, `make install
- +`/usr/local/bin
- +can specify an installation prefix other than `/usr/local
- +`configure
- +
- + You can specify separate installation prefixes for
- +architecture-specific files and architecture-independent files. If you
- +pass the option `--exec-prefix=PREFIX
- +PREFIX as the prefix for installing programs and libraries.
- +Documentation and other data files still use the regular prefix.
- +
- + In addition, if you use an unusual directory layout you can give
- +options like `--bindir=DIR
- +kinds of files. Run `configure --help
- +you can set and what kinds of files go in them.
- +
- + If the package supports it, you can cause programs to be installed
- +with an extra prefix or suffix on their names by giving `configure
- +option `--program-prefix=PREFIX
- +
- +Optional Features
- +=================
- +
- +Some packages pay attention to `--enable-FEATURE
- +`configure
- +They may also pay attention to `--with-PACKAGE
- +is something like `gnu-as
- +`README
- +package recognizes.
- +
- + For packages that use the X Window System, `configure
- +find the X include and library files automatically, but if it doesn
- +you can use the `configure
- +`--x-libraries=DIR
- +
- +Specifying the System Type
- +==========================
- +
- +There may be some features `configure
- +but needs to determine by the type of machine the package will run on.
- +Usually, assuming the package is built to be run on the _same_
- +architectures, `configure
- +message saying it cannot guess the machine type, give it the
- +`--build=TYPE
- +type, such as `sun4
- +
- + CPU-COMPANY-SYSTEM
- +
- +where SYSTEM can have one of these forms:
- +
- + OS KERNEL-OS
- +
- + See the file `config.sub
- +`config.sub
- +need to know the machine type.
- +
- + If you are _building_ compiler tools for cross-compiling, you should
- +use the option `--target=TYPE
- +produce code for.
- +
- + If you want to _use_ a cross compiler, that generates code for a
- +platform different from the build platform, you should specify the
- +"host" platform (i.e., that on which the generated programs will
- +eventually be run) with `--host=TYPE
- +
- +Sharing Defaults
- +================
- +
- +If you want to set default values for `configure
- +can create a site shell script called `config.site
- +values for variables like `CC
- +`configure
- +`PREFIX/etc/config.site
- +`CONFIG_SITE
- +A warning: not all `configure
- +
- +Defining Variables
- +==================
- +
- +Variables not defined in a site shell script can be set in the
- +environment passed to `configure
- +configure again during the build, and the customized values of these
- +variables may be lost. In order to avoid this problem, you should set
- +them in the `configure
- +
- + ./configure CC=/usr/local2/bin/gcc
- +
- +causes the specified `gcc
- +overridden in the site shell script). Here is a another example:
- +
- + /bin/bash ./configure CONFIG_SHELL=/bin/bash
- +
- +Here the `CONFIG_SHELL=/bin/bash
- +configuration-related scripts to be executed by `/bin/bash
- +
- +`configure
- +======================
- +
- +`configure
- +
- +`--help
- +`-h
- + Print a summary of the options to `configure
- +
- +`--version
- +`-V
- + Print the version of Autoconf used to generate the `configure
- + script, and exit.
- +
- +`--cache-file=FILE
- + Enable the cache: use and save the results of the tests in FILE,
- + traditionally `config.cache
- + disable caching.
- +
- +`--config-cache
- +`-C
- + Alias for `--cache-file=config.cache
- +
- +`--quiet
- +`--silent
- +`-q
- + Do not print messages saying which checks are being made. To
- + suppress all normal output, redirect it to `/dev/null
- + messages will still be shown).
- +
- +`--srcdir=DIR
- + Look for the package
- + `configure
- +
- +`configure
- +`configure --help
-
|