Debian Codegraph @

INSTALL

raw
1 NOTE by Alexey Eremenko: if you're running rpm-based distro, most chances
2 that you will need "fuse-devel" package installed.
3
4
5 Basic Installation
6 ==================
7
8 These are generic installation instructions.
9
10 The `configure' shell script attempts to guess correct values for
11 various system-dependent variables used during compilation. It uses
12 those values to create a `Makefile' in each directory of the package.
13 It may also create one or more `.h' files containing system-dependent
14 definitions. Finally, it creates a shell script `config.status' that
15 you can run in the future to recreate the current configuration, a file
16 `config.cache' that saves the results of its tests to speed up
17 reconfiguring, and a file `config.log' containing compiler output
18 (useful mainly for debugging `configure').
19
20 If you need to do unusual things to compile the package, please try
21 to figure out how `configure' could check whether to do them, and mail
22 diffs or instructions to the address given in the `README' so they can
23 be considered for the next release. If at some point `config.cache'
24 contains results you don't want to keep, you may remove or edit it.
25
26 The file `configure.in' is used to create `configure' by a program
27 called `autoconf'. You only need `configure.in' if you want to change
28 it or regenerate `configure' using a newer version of `autoconf'.
29
30 The simplest way to compile this package is:
31
32 1. `cd' to the directory containing the package's source code and type
33 `./configure' to configure the package for your system. If you're
34 using `csh' on an old version of System V, you might need to type
35 `sh ./configure' instead to prevent `csh' from trying to execute
36 `configure' itself.
37
38 Running `configure' takes a while. While running, it prints some
39 messages telling which features it is checking for.
40
41 2. Type `make' to compile the package.
42
43 3. Type `make install' to install the programs and any data files and
44 documentation.
45
46 4. You can remove the program binaries and object files from the
47 source code directory by typing `make clean'.
48
49 Compilers and Options
50 =====================
51
52 Some systems require unusual options for compilation or linking that
53 the `configure' script does not know about. You can give `configure'
54 initial values for variables by setting them in the environment. Using
55 a Bourne-compatible shell, you can do that on the command line like
56 this:
57 CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
58
59 Or on systems that have the `env' program, you can do it like this:
60 env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
61
62 Compiling For Multiple Architectures
63 ====================================
64
65 You can compile the package for more than one kind of computer at the
66 same time, by placing the object files for each architecture in their
67 own directory. To do this, you must use a version of `make' that
68 supports the `VPATH' variable, such as 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
73 If you have to use a `make' that does not supports the `VPATH'
74 variable, you have to compile the package for one architecture at a time
75 in the source code directory. After you have installed the package for
76 one architecture, use `make distclean' before reconfiguring for another
77 architecture.
78
79 Installation Names
80 ==================
81
82 By default, `make install' will install the package's files in
83 `/usr/local/bin', `/usr/local/man', etc. You can specify an
84 installation prefix other than `/usr/local' by giving `configure' the
85 option `--prefix=PATH'.
86
87 You can specify separate installation prefixes for
88 architecture-specific files and architecture-independent files. If you
89 give `configure' the option `--exec-prefix=PATH', the package will use
90 PATH as the prefix for installing programs and libraries.
91 Documentation and other data files will still use the regular prefix.
92
93 If the package supports it, you can cause programs to be installed
94 with an extra prefix or suffix on their names by giving `configure' the
95 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
96
97 Optional Features
98 =================
99
100 Some packages pay attention to `--enable-FEATURE' options to
101 `configure', where FEATURE indicates an optional part of the package.
102 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
103 is something like `gnu-as' or `x' (for the X Window System). The
104 `README' should mention any `--enable-' and `--with-' options that the
105 package recognizes.
106
107 For packages that use the X Window System, `configure' can usually
108 find the X include and library files automatically, but if it doesn't,
109 you can use the `configure' options `--x-includes=DIR' and
110 `--x-libraries=DIR' to specify their locations.
111
112 Specifying the System Type
113 ==========================
114
115 There may be some features `configure' can not figure out
116 automatically, but needs to determine by the type of host the package
117 will run on. Usually `configure' can figure that out, but if it prints
118 a message saying it can not guess the host type, give it the
119 `--host=TYPE' option. TYPE can either be a short name for the system
120 type, such as `sun4', or a canonical name with three fields:
121 CPU-COMPANY-SYSTEM
122
123 See the file `config.sub' for the possible values of each field. If
124 `config.sub' isn't included in this package, then this package doesn't
125 need to know the host type.
126
127 If you are building compiler tools for cross-compiling, you can also
128 use the `--target=TYPE' option to select the type of system they will
129 produce code for and the `--build=TYPE' option to select the type of
130 system on which you are compiling the package.
131
132 Sharing Defaults
133 ================
134
135 If you want to set default values for `configure' scripts to share,
136 you can create a site shell script called `config.site' that gives
137 default values for variables like `CC', `cache_file', and `prefix'.
138 `configure' looks for `PREFIX/share/config.site' if it exists, then
139 `PREFIX/etc/config.site' if it exists. Or, you can set the
140 `CONFIG_SITE' environment variable to the location of the site script.
141 A warning: not all `configure' scripts look for a site script.
142
143 Operation Controls
144 ==================
145
146 `configure' recognizes the following options to control how it
147 operates.
148
149 `--cache-file=FILE'
150 Use and save the results of the tests in FILE instead of
151 `./config.cache'. Set FILE to `/dev/null' to disable caching, for
152 debugging `configure'.
153
154 `--help'
155 Print a summary of the options to `configure', and exit.
156
157 `--quiet'
158 `--silent'
159 `-q'
160 Do not print messages saying which checks are being made.
161
162 `--srcdir=DIR'
163 Look for the package's source code in directory DIR. Usually
164 `configure' can determine that directory automatically.
165
166 `--version'
167 Print the version of Autoconf used to generate the `configure'
168 script, and exit.
169
170 `configure' also accepts some other, not widely useful, options.
171