Installation Summary
--------------------

To compile and install this package:

  1. Normally, you would want to set up your local news server first. 
     The default newsx auto-configuration checks which news server files
     and directories exist.

     If you want to build newsx before setting up a news server, see
     Runtine News Configuration below.

  2. Look over the Installation Details and Special Cases below to see if
     you need to give ./configure any special options.

  3. As user 'news' (or whoever owns your USENET News software), do

		./configure     (with the options you prefer)

     (Note: ./configure produces README from README.in .)

		make            (to build the programs).

  4. If you need to be superuser/root to install software, do so, then do

		make install    (installs the programs, data files, and
				 documentation).

  5. Consult the README and FAQ for further advice regarding installation
     and setting up the package.

  6. 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'. 


Installation Details and Special Cases
--------------------------------------

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 should pick them up. Otherwise, the directory
where they are found should be specified by the --with-newslib configuration
option.

It is now also required that the corresponding INN include file "storage.h" 
is available. The configuration option --with-newsinclude may be used to
specify where the storage.h file is found.

Many INN packages will include a storage.h. But if INN is compiled and
installed from the standard INN tarball (at least <= 2.3.4), no include
file will be installed. The patch found in more/inn234.patch may be
installed to repair this.


Support for INN 1.x
===================

Support for common INN 1.x versions is built in. It will probably work for
early 2.x versions also.


Support for Cnews
===================

Support for common Cnews versions is built in.


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"


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 bug-newsx@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.ac' is used to create `configure' by a program
called `autoconf'.  You only need `configure.ac' 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.


Known Workarounds
=================

1) `dbx newsx' complains of a symbol table problem and won't run

   Apparently, `gcc -g' can produce things dbx can't handle.  This has been
   seen in dbz/dbz-v3.o, dbz/dbz.o, and dbz/hash.o.  Recompile the file
   without the "-g" option and relink newsx.  E.g., if dbx complains about
   dbz/dbz.o, edit dbz/Makefile to remove "-g " from CFLAGS,
   `rm dbz/dbz.o src/newsx', and rerun `make'.
