Note: for now, the testing system is unreleased, and you should ignore
the instructions about it and the related testing and text tar files.

Requirements:

A recent version of gcc (2.7 or higher), GNU make (required to handle
the dependancies files (the .d files)), and a recent version of Perl 5
plus GNU tar for the test system.

Special requirements for particular systems:

AIX was built with the xlc compiler using Makeinclude.AIX.4.2-xlc with
the 991022-1420 timestamped 8.2.09 sources.  You can probably make it
work with gcc, but I didn't have time for it; the previous 8.2 version
was made with xlc.  There are numerous non-fatal errors and warnings
in the compilation due to the pickiness of xlc; I believe they are
harmless.

For Digital Unix/Tru-64, use the 8.2.10 sources, and it is suggested
that you use gcc 2.8.1; I am told that anything later as of gcc 2.95.1
produces bad debugging info.  Do not be concerned about these warnings
in compiling the database:

  ../dist/../btree/bt_curadj.c:44: warning: cast from pointer to
  integer of different size

  ../dist/../db/db_am.c:260: warning: cast from pointer to integer of
  different size

They are in debugging printfs, where throwing away the top portion of
the pointer is ok, or at least tolerable.

As a side note, for any platform, all that ListProc cares about in dbm
is the building of libdb.a and db.h


Pre-compile:
  
1. Create a build directory.
2. Under the build directory create a dbm and a lp8 directory (also a
   testing and a text directory if you're going to use the test system).
3. Under the lp8 directory create a src directory.
4. Create a SRCDIR environment variable set to <full path to build>/lp8/src
   (It would be a good idea to add this to your .profile or .cshrc file.)
5. Untar the ListProc source tar in the <build>/lp8/src directory.
6. cd into the makeincludes directory.
7. cp a likely Makeinclude.<specific-system> file to Makeinclude.local
8. Edit Makeinclude.local for local pathnames, etc.

   (If you are porting to a new system, create a new
    Makefile.<system-name from your edited Makeinclude.local when
    you are finished, and please send that and any diffs back to CREN.

    If you are trying to compile this in a 64 bit environment, start
    with 8.2.10 sources, which are the most 64 bit clean.  But I
    advise sticking to 32 bits if at all possible until 9.0)

9. Untar the dbm tar in the <build>/dbm directory.
10. Untar the testing tar in the <build>/testing directory.
11. Untar the text tar in the <build>/text directory.
  

Database compile:
  
1. cd to <build>/dbm
2. make

You probably shouldn't get any warnings in executing the above, except

	Can't open ../dist/../test/include.tcl

when running configure, because the tcl, java, etc. interfaces are not
shipped in the ListProc distribution of the database.  ( You can get
the full distribution from http://www.sleepycat.com/ )


ListProc compile:
  
1. cd to <build>/lp8/src
2. make

   On all but the most recent version of gcc I get two "warning:
   assignment discards `const' from pointer target type"; this is
   likely to vary with compiler, system, etc.  gcc 2.95 substitutes
   the more opaque "warning: assignment discards qualifiers from
   pointer target type".

3. cd to <build>/testing
4. runtest basic/script (should exit with status 0 and no errors)
5. make simpledist (do not worry that the file is named bins..<etc>)


Installing:   

Into an existing ListProc Installation:

(If you're upgrading from 6.0c be sure to get 

	http://www.cren.net/listproc/docs/6.0c-to-8.2.txt

to guide you in changing the config file, etc..)

1. stop Listproc
2. untar the bins tar file in your listproc home dir as the
   listproc user.

7. if you were previously running 8.2, remove or rename users.db, and
   use the script supplied in

	http://www.cren.net/ftp/software/lp_utils/revdb_update_all1

   to recreate it with the new dbm library.   
8. at this point you ought to be able to restart ListProc and run with it.   

No existing ListProc Installation:

   If you do not have an existing ListProc install the safest thing is
   to get one from us and install and configure it according to the
   instructions, and play with it a bit.  ListProc depends on a number
   of text files being installed and configured correctly.  Do this
   even if you are making a port to a new system---just don't run any
   of the binaries before you've untarred your new ones according to
   the instructions above.

   It would also be a good idea to look at the recently changed files
   in the the source text directory; config has almost certainly been
   changed, and you may want to merge those changes in to customize
   new features.