Debian Codegraph @

INSTALL

raw
1 To install:
2
3 0) if you are uncommon with configuration and installation of GNU/autoconf'd
4 software please read to generic install text at the end of this file.
5 1) configure the package, possibly with
6 CFLAGS=-O2 ./configure
7 Use the following options if you need to:
8 --disble-timesync
9 this saves a few bytes. The timesync protocol allows to set the
10 receivers system time to the sender's time (see option S in
11 the manual pages). Including timesync support doesn't introduce
12 any incompatabilites (but *using* timesync does).
13 --enable-pubdir=/var/spool/uucppublic
14 if you want support for a public writeable directory.
15 --enable-syslog[=[[FACILITY,]level]]
16 to include syslog support. Not much will be written to syslog,
17 just one line per file.
18 Default facility is LOG_UUCP, but you can change that to whatever
19 your syslog.h supports.
20 Level defaults to "default", meaning syslog is on by default,
21 but is can be forced ("force"), meaning users will not be
22 allowed to turn it off, and it can be "optional", meaning users
23 have to turn it on for every transmission.
24 Example:
25 --enable-syslog=LOG_LOCAL0,force
26 every filetransfer will be logged to LOG_LOCAL0.
27 --enable-syslog=default and --enable-syslog
28 every filetransfer will be logged to LOG_UUCP, unless
29 the user turns this off with the "--syslog=off" runtime
30 option of lsz and lrz.
31 --enable-syslog=optional
32 no filetransfer will be logged, but syslogging can be
33 enabled with the "--syslog" runtime option of lsz and lrz.
34 --disable-mkdir
35 if rz shall never create directories (this option is only included
36 because disbaling the directory creation was possible with the
37 original sources).
38 --prefix=/usr/local
39 to install the programs and documentation under /usr/local instead
40 of /usr (default).
41 --program-transform-name=s/l//
42 to install the programs and manual pages under the traditional
43 names (sz, sz.1 instead of lsz, lsz.1).
44 2) make
45 (please contact [email protected] if there are any problems.)
46 3) make check
47 will perform a selftest, sending some files in the distribution
48 through a named pipe.
49 ("make vcheck" will do the same as "make check" does, but prints
50 a progress report)
51 4) please read COMPATABILITY
52 5) make install
53 if everything is ok.
54
55 -------------------- generic GNU INSTALL text -----------------------------
56 Basic Installation
57 ==================
58
59 These are generic installation instructions.
60
61 The `configure' shell script attempts to guess correct values for
62 various system-dependent variables used during compilation. It uses
63 those values to create a `Makefile' in each directory of the package.
64 It may also create one or more `.h' files containing system-dependent
65 definitions. Finally, it creates a shell script `config.status' that
66 you can run in the future to recreate the current configuration, a file
67 `config.cache' that saves the results of its tests to speed up
68 reconfiguring, and a file `config.log' containing compiler output
69 (useful mainly for debugging `configure').
70
71 If you need to do unusual things to compile the package, please try
72 to figure out how `configure' could check whether to do them, and mail
73 diffs or instructions to the address given in the `README' so they can
74 be considered for the next release. If at some point `config.cache'
75 contains results you don't want to keep, you may remove or edit it.
76
77 The file `configure.in' is used to create `configure' by a program
78 called `autoconf'. You only need `configure.in' if you want to change
79 it or regenerate `configure' using a newer version of `autoconf'.
80
81 The simplest way to compile this package is:
82
83 1. `cd' to the directory containing the package's source code and type
84 `./configure' to configure the package for your system. If you're
85 using `csh' on an old version of System V, you might need to type
86 `sh ./configure' instead to prevent `csh' from trying to execute
87 `configure' itself.
88
89 Running `configure' takes awhile. While running, it prints some
90 messages telling which features it is checking for.
91
92 2. Type `make' to compile the package.
93
94 3. Optionally, type `make check' to run any self-tests that come with
95 the package.
96
97 4. Type `make install' to install the programs and any data files and
98 documentation.
99
100 5. You can remove the program binaries and object files from the
101 source code directory by typing `make clean'. To also remove the
102 files that `configure' created (so you can compile the package for
103 a different kind of computer), type `make distclean'. There is
104 also a `make maintainer-clean' target, but that is intended mainly
105 for the package's developers. If you use it, you may have to get
106 all sorts of other programs in order to regenerate files that came
107 with the distribution.
108
109 Compilers and Options
110 =====================
111
112 Some systems require unusual options for compilation or linking that
113 the `configure' script does not know about. You can give `configure'
114 initial values for variables by setting them in the environment. Using
115 a Bourne-compatible shell, you can do that on the command line like
116 this:
117 CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
118
119 Or on systems that have the `env' program, you can do it like this:
120 env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
121
122 Compiling For Multiple Architectures
123 ====================================
124
125 You can compile the package for more than one kind of computer at the
126 same time, by placing the object files for each architecture in their
127 own directory. To do this, you must use a version of `make' that
128 supports the `VPATH' variable, such as GNU `make'. `cd' to the
129 directory where you want the object files and executables to go and run
130 the `configure' script. `configure' automatically checks for the
131 source code in the directory that `configure' is in and in `..'.
132
133 If you have to use a `make' that does not supports the `VPATH'
134 variable, you have to compile the package for one architecture at a time
135 in the source code directory. After you have installed the package for
136 one architecture, use `make distclean' before reconfiguring for another
137 architecture.
138
139 Installation Names
140 ==================
141
142 By default, `make install' will install the package's files in
143 `/usr/local/bin', `/usr/local/man', etc. You can specify an
144 installation prefix other than `/usr/local' by giving `configure' the
145 option `--prefix=PATH'.
146
147 You can specify separate installation prefixes for
148 architecture-specific files and architecture-independent files. If you
149 give `configure' the option `--exec-prefix=PATH', the package will use
150 PATH as the prefix for installing programs and libraries.
151 Documentation and other data files will still use the regular prefix.
152
153 In addition, if you use an unusual directory layout you can give
154 options like `--bindir=PATH' to specify different values for particular
155 kinds of files. Run `configure --help' for a list of the directories
156 you can set and what kinds of files go in them.
157
158 If the package supports it, you can cause programs to be installed
159 with an extra prefix or suffix on their names by giving `configure' the
160 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
161
162 Optional Features
163 =================
164
165 Some packages pay attention to `--enable-FEATURE' options to
166 `configure', where FEATURE indicates an optional part of the package.
167 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
168 is something like `gnu-as' or `x' (for the X Window System). The
169 `README' should mention any `--enable-' and `--with-' options that the
170 package recognizes.
171
172 For packages that use the X Window System, `configure' can usually
173 find the X include and library files automatically, but if it doesn't,
174 you can use the `configure' options `--x-includes=DIR' and
175 `--x-libraries=DIR' to specify their locations.
176
177 Specifying the System Type
178 ==========================
179
180 There may be some features `configure' can not figure out
181 automatically, but needs to determine by the type of host the package
182 will run on. Usually `configure' can figure that out, but if it prints
183 a message saying it can not guess the host type, give it the
184 `--host=TYPE' option. TYPE can either be a short name for the system
185 type, such as `sun4', or a canonical name with three fields:
186 CPU-COMPANY-SYSTEM
187
188 See the file `config.sub' for the possible values of each field. If
189 `config.sub' isn't included in this package, then this package doesn't
190 need to know the host type.
191
192 If you are building compiler tools for cross-compiling, you can also
193 use the `--target=TYPE' option to select the type of system they will
194 produce code for and the `--build=TYPE' option to select the type of
195 system on which you are compiling the package.
196
197 Sharing Defaults
198 ================
199
200 If you want to set default values for `configure' scripts to share,
201 you can create a site shell script called `config.site' that gives
202 default values for variables like `CC', `cache_file', and `prefix'.
203 `configure' looks for `PREFIX/share/config.site' if it exists, then
204 `PREFIX/etc/config.site' if it exists. Or, you can set the
205 `CONFIG_SITE' environment variable to the location of the site script.
206 A warning: not all `configure' scripts look for a site script.
207
208 Operation Controls
209 ==================
210
211 `configure' recognizes the following options to control how it
212 operates.
213
214 `--cache-file=FILE'
215 Use and save the results of the tests in FILE instead of
216 `./config.cache'. Set FILE to `/dev/null' to disable caching, for
217 debugging `configure'.
218
219 `--help'
220 Print a summary of the options to `configure', and exit.
221
222 `--quiet'
223 `--silent'
224 `-q'
225 Do not print messages saying which checks are being made.
226
227 `--srcdir=DIR'
228 Look for the package's source code in directory DIR. Usually
229 `configure' can determine that directory automatically.
230
231 `--version'
232 Print the version of Autoconf used to generate the `configure'
233 script, and exit.
234
235 `configure' also accepts some other, not widely useful, options.
236