4 To configure and compile SILC package give the commands:
10 This will install the SILC binaries and configuration files into the
11 /usr/local/silc/ directory. System wide configuration files are installed
12 into the /etc/silc/ directory.
14 You may need to add the /usr/local/silc path to your PATH environment
15 variable after the installation.
20 You can give various options to the `configure' shell script. You should
21 give --help command to the `configure' to see all of them. Here is listed
22 few options that you might want to use. Please refer to the rest of this
23 file for more generic installation instructions.
27 If you wish to use GMP library for arbitrary precision arithmetic
28 library instead of using the MPI library included in the package, you can
29 give the --with-gmp[=DIR] option to the `configure'. The DIR is the upper
30 path in your system which contains lib/ and include/ for GMP library.
31 Note that MPI is the prefered arbitrary precision arithmetic library and
32 GMP can be used as a fall-back if you have problems with the MPI library
33 included within this package.
37 If your system doesn't provide iconv() function in its native libraries
38 (usually libc) or if this function is broken (e.g. older Solaris systems),
39 you may want to use libiconv instead. The DIR is the upper path in your
40 system which contains lib/ and include/ for libiconv (e.g. /usr/local).
44 If you do not want to compile the programs with POSIX multi-threads
45 support you can give --without-pthreads option. In this case all compiled
46 programs will work in single thread only.
50 If you have trouble compiling the assembler optimized code in the
51 package or does not want to use them, you can give the --disable-asm
52 option to the `configure' script. This will assure that assembler
53 optimized code is not compiled in.
57 If you wish to compile and install shared libraries then enable this
58 option. By default all libraries are compiled as static libraries.
62 If you would like to enable the debugging for the compiled programs
63 you can give this option to the `configure'.
67 The `configure' will attempt to check for IPv6 support in your system.
68 However, if it fails, but you still want to compile in the IPv6 support
69 you can give --enable-ipv6 option to force the IPv6 support.
74 These are generic installation instructions.
76 The `configure' shell script attempts to guess correct values for
77 various system-dependent variables used during compilation. It uses
78 those values to create a `Makefile' in each directory of the package.
79 It may also create one or more `.h' files containing system-dependent
80 definitions. Finally, it creates a shell script `config.status' that
81 you can run in the future to recreate the current configuration, a file
82 `config.cache' that saves the results of its tests to speed up
83 reconfiguring, and a file `config.log' containing compiler output
84 (useful mainly for debugging `configure').
86 If you need to do unusual things to compile the package, please try
87 to figure out how `configure' could check whether to do them, and mail
88 diffs or instructions to the address given in the `README' so they can
89 be considered for the next release. If at some point `config.cache'
90 contains results you don't want to keep, you may remove or edit it.
92 The file `configure.in' is used to create `configure' by a program
93 called `autoconf'. You only need `configure.in' if you want to change
94 it or regenerate `configure' using a newer version of `autoconf'.
96 The simplest way to compile this package is:
98 1. `cd' to the directory containing the package's source code and type
99 `./configure' to configure the package for your system. If you're
100 using `csh' on an old version of System V, you might need to type
101 `sh ./configure' instead to prevent `csh' from trying to execute
104 Running `configure' takes awhile. While running, it prints some
105 messages telling which features it is checking for.
107 2. Type `make' to compile the package.
109 3. Optionally, type `make check' to run any self-tests that come with
112 4. Type `make install' to install the programs and any data files and
115 5. You can remove the program binaries and object files from the
116 source code directory by typing `make clean'. To also remove the
117 files that `configure' created (so you can compile the package for
118 a different kind of computer), type `make distclean'. There is
119 also a `make maintainer-clean' target, but that is intended mainly
120 for the package's developers. If you use it, you may have to get
121 all sorts of other programs in order to regenerate files that came
122 with the distribution.
124 Compilers and Options
125 =====================
127 Some systems require unusual options for compilation or linking that
128 the `configure' script does not know about. You can give `configure'
129 initial values for variables by setting them in the environment. Using
130 a Bourne-compatible shell, you can do that on the command line like
132 CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
134 Or on systems that have the `env' program, you can do it like this:
135 env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
137 Compiling For Multiple Architectures
138 ====================================
140 You can compile the package for more than one kind of computer at the
141 same time, by placing the object files for each architecture in their
142 own directory. To do this, you must use a version of `make' that
143 supports the `VPATH' variable, such as GNU `make'. `cd' to the
144 directory where you want the object files and executables to go and run
145 the `configure' script. `configure' automatically checks for the
146 source code in the directory that `configure' is in and in `..'.
148 If you have to use a `make' that does not supports the `VPATH'
149 variable, you have to compile the package for one architecture at a time
150 in the source code directory. After you have installed the package for
151 one architecture, use `make distclean' before reconfiguring for another
157 By default, `make install' will install the package's files in
158 `/usr/local/bin', `/usr/local/man', etc. You can specify an
159 installation prefix other than `/usr/local' by giving `configure' the
160 option `--prefix=PATH'.
162 You can specify separate installation prefixes for
163 architecture-specific files and architecture-independent files. If you
164 give `configure' the option `--exec-prefix=PATH', the package will use
165 PATH as the prefix for installing programs and libraries.
166 Documentation and other data files will still use the regular prefix.
168 In addition, if you use an unusual directory layout you can give
169 options like `--bindir=PATH' to specify different values for particular
170 kinds of files. Run `configure --help' for a list of the directories
171 you can set and what kinds of files go in them.
173 If the package supports it, you can cause programs to be installed
174 with an extra prefix or suffix on their names by giving `configure' the
175 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
180 Some packages pay attention to `--enable-FEATURE' options to
181 `configure', where FEATURE indicates an optional part of the package.
182 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
183 is something like `gnu-as' or `x' (for the X Window System). The
184 `README' should mention any `--enable-' and `--with-' options that the
187 For packages that use the X Window System, `configure' can usually
188 find the X include and library files automatically, but if it doesn't,
189 you can use the `configure' options `--x-includes=DIR' and
190 `--x-libraries=DIR' to specify their locations.
192 Specifying the System Type
193 ==========================
195 There may be some features `configure' can not figure out
196 automatically, but needs to determine by the type of host the package
197 will run on. Usually `configure' can figure that out, but if it prints
198 a message saying it can not guess the host type, give it the
199 `--host=TYPE' option. TYPE can either be a short name for the system
200 type, such as `sun4', or a canonical name with three fields:
203 See the file `config.sub' for the possible values of each field. If
204 `config.sub' isn't included in this package, then this package doesn't
205 need to know the host type.
207 If you are building compiler tools for cross-compiling, you can also
208 use the `--target=TYPE' option to select the type of system they will
209 produce code for and the `--build=TYPE' option to select the type of
210 system on which you are compiling the package.
215 `configure' recognizes the following options to control how it
219 Use and save the results of the tests in FILE instead of
220 `./config.cache'. Set FILE to `/dev/null' to disable caching, for
221 debugging `configure'.
224 Print a summary of the options to `configure', and exit.
229 Do not print messages saying which checks are being made. To
230 suppress all normal output, redirect it to `/dev/null' (any error
231 messages will still be shown).
234 Look for the package's source code in directory DIR. Usually
235 `configure' can determine that directory automatically.
238 Print the version of Autoconf used to generate the `configure'
241 `configure' also accepts some other, not widely useful, options.