GateD-5.0 now uses GNU autoconf to detect platform-specific configuration options. You do not need to install autoconf to build GateD. By default, GateD is compiled with all protocols available. Should you wish to disable support for some protocols, this can be done through an "options" file. Normally, protocols will only be turned on/off via the gated.conf run-time configuration file.
In the simplest case, you just want to compile GateD-5.0 for a single architecture, with all protocols supported. The procedure for doing this is just:
./configure make
In the more general case, you may want to compile GateD5.0 for multiple platforms. In this case, you should not build GateD in the original location (i.e., don't follow the steps in section II). If you have already done section II, you may clean out the original location by doing "make cleanall". This removes files created by ./configure in addition to those created by make ("make clean" only removes files created by make).
To build GateD for a new platform, you must first create a build directory manually. (The architecture type is NOT sufficient to uniquely identify the features supported by the machine, so GateD will no longer guess a build directory to use. Different machines can vary in the kernel options enabled, which compiler is available, etc.)
In the examples below, we will use gated-multi/src/
cd gated-multi/src mkdir excelsior cd excelsior ../configure --srcdir=.. make
Enabling support for specific protocols at compile-time is supported through the "options" file. The file gated-multi/src/gated/options contains the standard options (i.e. everything supported).
To disable support for specific protocols, you should: