"Fossies" - the Fresh Open Source Software Archive
Member "zsync-0.6.2/INSTALL" (16 Sep 2010, 9296 Bytes) of package /linux/privat/old/zsync-0.6.2.tar.gz:
As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard
) with prefixed line numbers.
Alternatively you can here view
the uninterpreted source code file.
1 Basic Installation
4 These are the instructions for compiling and installing zsync for your
5 system. These are mostly generic instructions on how to use the normal
6 configure/make/gcc tools to build zsync.
8 The `configure' shell script attempts to guess correct values for
9 various system-dependent variables used during compilation. It uses
10 those values to create a `Makefile' in each directory of the package.
11 It may also create one or more `.h' files containing system-dependent
12 definitions. Finally, it creates a shell script `config.status' that
13 you can run in the future to recreate the current configuration, and a
14 file `config.log' containing compiler output (useful mainly for
15 debugging `configure').
17 It can also use an optional file (typically called `config.cache'
18 and enabled with `--cache-file=config.cache' or simply `-C') that saves
19 the results of its tests to speed up reconfiguring. (Caching is
20 disabled by default to prevent problems with accidental use of stale
21 cache files.)
23 If you need to do unusual things to compile the package, please try
24 to figure out how `configure' could check whether to do them, and mail
25 diffs or instructions to the address given in the `README' so they can
26 be considered for the next release. If you are using the cache, and at
27 some point `config.cache' contains results you don't want to keep, you
28 may remove or edit it.
30 The file `configure.ac' (or `configure.in') is used to create
31 `configure' by a program called `autoconf'. You only need
32 `configure.ac' if you want to change it or regenerate `configure' using
33 a newer version of `autoconf'.
35 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. If you're
39 using `csh' on an old version of System V, you might need to type
40 `sh ./configure' instead to prevent `csh' from trying to execute
41 `configure' itself.
43 Running `configure' takes awhile. While running, it prints some
44 messages telling which features it is checking for.
46 2. Type `make' to compile the package.
48 3. Optionally, type `make check' to run any self-tests that come with
49 the package. This is strongly recommended if compiling for OSes other
50 than Linux/FreeBSD or for processors other than i386.
52 4. Type `make install' to install the programs and any data files and
55 5. You can remove the program binaries and object files from the
56 source code directory by typing `make clean'. To also remove the
57 files that `configure' created (so you can compile the package for
58 a different kind of computer), type `make distclean'. There is
59 also a `make maintainer-clean' target, but that is intended mainly
60 for the package's developers. If you use it, you may have to get
61 all sorts of other programs in order to regenerate files that came
62 with the distribution.
64 Compilers and Options
67 Some systems require unusual options for compilation or linking that
68 the `configure' script does not know about. Run `./configure --help'
69 for details on some of the pertinent environment variables.
71 You can give `configure' initial values for configuration parameters
72 by setting variables in the command line or in the environment. Here
73 is an example:
75 ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
77 *Note Defining Variables::, for more details.
79 Compiling For Multiple Architectures
82 You can compile the package for more than one kind of computer at the
83 same time, by placing the object files for each architecture in their
84 own directory. To do this, you must use a version of `make' that
85 supports the `VPATH' variable, such as GNU `make'. `cd' to the
86 directory where you want the object files and executables to go and run
87 the `configure' script. `configure' automatically checks for the
88 source code in the directory that `configure' is in and in `..'.
90 If you have to use a `make' that does not support the `VPATH'
91 variable, you have to compile the package for one architecture at a
92 time in the source code directory. After you have installed the
93 package for one architecture, use `make distclean' before reconfiguring
94 for another architecture.
96 Installation Names
99 By default, `make install' will install the package's files in
100 `/usr/local/bin', `/usr/local/man', etc. You can specify an
101 installation prefix other than `/usr/local' by giving `configure' the
102 option `--prefix=PATH'.
104 You can specify separate installation prefixes for
105 architecture-specific files and architecture-independent files. If you
106 give `configure' the option `--exec-prefix=PATH', the package will use
107 PATH as the prefix for installing programs and libraries.
108 Documentation and other data files will still use the regular prefix.
110 In addition, if you use an unusual directory layout you can give
111 options like `--bindir=PATH' to specify different values for particular
112 kinds of files. Run `configure --help' for a list of the directories
113 you can set and what kinds of files go in them.
115 If the package supports it, you can cause programs to be installed
116 with an extra prefix or suffix on their names by giving `configure' the
117 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
119 Optional Features
122 Some packages pay attention to `--enable-FEATURE' options to
123 `configure', where FEATURE indicates an optional part of the package.
124 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
125 is something like `gnu-as' or `x' (for the X Window System). The
126 `README' should mention any `--enable-' and `--with-' options that the
127 package recognizes.
129 Specifying the System Type
132 There may be some features `configure' cannot figure out
133 automatically, but needs to determine by the type of machine the package
134 will run on. Usually, assuming the package is built to be run on the
135 _same_ architectures, `configure' can figure that out, but if it prints
136 a message saying it cannot guess the machine type, give it the
137 `--build=TYPE' option. TYPE can either be a short name for the system
138 type, such as `sun4', or a canonical name which has the form:
142 where SYSTEM can have one of these forms:
144 OS KERNEL-OS
146 See the file `config.sub' for the possible values of each field. If
147 `config.sub' isn't included in this package, then this package doesn't
148 need to know the machine type.
150 If you are _building_ compiler tools for cross-compiling, you should
151 use the `--target=TYPE' option to select the type of system they will
152 produce code for.
154 If you want to _use_ a cross compiler, that generates code for a
155 platform different from the build platform, you should specify the
156 "host" platform (i.e., that on which the generated programs will
157 eventually be run) with `--host=TYPE'.
159 Sharing Defaults
162 If you want to set default values for `configure' scripts to share,
163 you can create a site shell script called `config.site' that gives
164 default values for variables like `CC', `cache_file', and `prefix'.
165 `configure' looks for `PREFIX/share/config.site' if it exists, then
166 `PREFIX/etc/config.site' if it exists. Or, you can set the
167 `CONFIG_SITE' environment variable to the location of the site script.
168 A warning: not all `configure' scripts look for a site script.
170 Defining Variables
173 Variables not defined in a site shell script can be set in the
174 environment passed to `configure'. However, some packages may run
175 configure again during the build, and the customized values of these
176 variables may be lost. In order to avoid this problem, you should set
177 them in the `configure' command line, using `VAR=value'. For example:
179 ./configure CC=/usr/local2/bin/gcc
181 will cause the specified gcc to be used as the C compiler (unless it is
182 overridden in the site shell script).
184 `configure' Invocation
187 `configure' recognizes the following options to control how it
192 Print a summary of the options to `configure', and exit.
196 Print the version of Autoconf used to generate the `configure'
197 script, and exit.
200 Enable the cache: use and save the results of the tests in FILE,
201 traditionally `config.cache'. FILE defaults to `/dev/null' to
202 disable caching.
206 Alias for `--cache-file=config.cache'.
211 Do not print messages saying which checks are being made. To
212 suppress all normal output, redirect it to `/dev/null' (any error
213 messages will still be shown).
216 Look for the package's source code in directory DIR. Usually
217 `configure' can determine that directory automatically.
219 `configure' also accepts some other, not widely useful, options. Run
220 `configure --help' for more details.
222 Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
223 Foundation, Inc.
225 This file is free documentation; the Free Software Foundation gives
226 unlimited permission to copy, distribute and modify it.
228 Copyright (C) 2009 Colin Phipps <email@example.com>