Compiling Stage


Once the libraries are properly installed, the server installation should be fairly painless, as it follows the usual autoconf conventions:

1. ./autogen.sh
2. ./configure
3. make
4. make check
5. make install (usually as root)
6. make clean (or `make distclean` if you'd rather)

One catchme: by default, it seems autogen.sh and aclocal ONLY look in /usr/share/aclocal for the m4 macros. libsigc++ (one of the required libraries) will install its configuration macro package in to /usr/local/share/aclocal. To ease this build step, make a link from /usr/local/share/aclocal/sigc++.m4 to /usr/share/aclocal ( ln -sf /usr/local/share/aclocal/sigc++.m4 /usr/share/aclocal )

You may want to consider creating a special user account to hold the stage installation.

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 may also create one or more `.h' files 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').

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 the address given in the `README' 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'.