1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
|
Basic Installation
==================
The easiest way to compile this package is:
1. Type `make' to configure tha package for your system and compile
the package.
To run the configuration as a seperate step, type `./configure'.
2. Type `make install' to install the programs and any data files and
documentation. You will often have to switch to superuser mode for
this.
3. Consult the README and FAQ for further advice regarding installation
and setting up the package.
4. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'.
Support for INN 2.x
===================
Support for INN 2.x relies on the two libraries libinn and libstorage
supplied with INN. If these libraries are available in the standard places,
the configuration script will pick them up. Otherwise, the directory
where they are found should be specified by the --with-newslib configuration
option.
Some support for INN 2.x is available also without these libraries, but
due to many inherent problems this will probably disappear in the future.
Runtine News Configuration
==========================
Runtime configuration is especially useful if you like to produce a newsx
binary that is directly useable for different news installations.
Use the configure option --with-newsconfig to postpone actual news
configuration to runtime. A list of several alternatives may be given,
seperated by colons.
E.g:
--with-newsconfig="/usr/lib/news/innshellvars:/usr/lib/news/bin/config"
Support for runtime configuration is currently experimental.
There are known problems with support for INN 2.x storage API and
tagged hash. Please contact newsx-bugs@kvaleberg.no for further detail.
The Configure Script
====================
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It will also create a `config.h' file containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').
In the vast majority of cases, the configure script will find out by
itself everything it needs to know about a system.
Options on the `configure' script command line can be used for
customizing your configuration in various ways. To find what these
options are, run `./configure --help'.
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to newsx-bugs@kvaleberg.no so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.
The file `configure.in' is used to create `configure' by a program
called `autoconf'. You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
this:
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
Specifying the System Type
==========================
There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
CPU-COMPANY-SYSTEM
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
$Id: INSTALL,v 1.7 1999/04/08 08:04:32 src Exp $
|
