INSTALLATION

In order to compile and install debug, follow these steps:

 0) To regenerate 'configure' cd to the debug-x.x.x root directory
    and enter the following from the command line:
    'autoconf autoconf/configure.in > configure'
    Autoconf 2.13 works, more recent versions may not.
    DO NOT PERFORM THIS REGENERATION UNLESS ABSOLUTELY NECESSARY. 
    The delivered 'configure' should take care of normal needs.

 1) Enter the debug-x.x.x source tree and execute "./configure",
    a script which will configure various settings for the
    build.

 2) After configure finishes, execute "make" to compile the
    package.

 3) Finally, become root if necessary, and execute "make install"
    to install the debugger. The default installation path is
    /usr/local/bin, but this can be changed with the --prefix
    option to configure as explained below.

If you wish to install debug in a location other than /usr/local/bin,
run configure with the --prefix option. For example, if you want
binaries installed in /usr/bin, type:
  ./configure --prefix=/usr

Curses support is an illusion. If you do manage to get configure to enable
curses support, the resulting binary will just tell you 'curses not enabled'.

Default 'configure' will generate '--enable-readline' which automatically
adds libtermcap.so as well as libreadline.so to the build. If you need a
libc.so only linked debug, use the following configure command:
'configure --enable-readline=no'
The libc.so only version uses fgets() for line input and does not have a
command history. But it will run in a non-libreadline environment such as
a floppy.

debug is known to compile cleanly and run on linux 2.2.* and 2.4.*.

The original ald was known to compile cleanly and run on the following
operating systems:

  FreeBSD 4.0-STABLE, 4.1-STABLE, 3.2-RELEASE
  OpenBSD 2.7
  Linux 2.2.*, 2.4.*

If you have to make changes to get debug to compile on any of the above,
please send the changes for inclusion in further releases.

TROUBLESHOOTING

If something goes wrong during the build or installation and
your operating system is among those listed above, it is most
likely a bug, and I would like to hear about it.

Special Note: If the configure script outputs a warning about
              being unable to detect your machine's word size,
              you *must* manually edit include/defs.h and
              #define WORDSIZE <value>, where <value> is the
              number of bytes in your machine word. On most intel
              systems, this is 2.

If you believe you have encountered a bug please email me
at loveall@iinet.com supplying as much information as you can.
