ANNOUNCEMENT

-			A N N O U N C E M E N T
+	A N N O U N C E M E N T
 
-			       LDAP 3.3
+	OpenLDAP 1.2
 
-    The University of Michigan is pleased to announce release 3.3 of
-    UM-LDAP, an implementation of the Lightweight Directory Access
-    Protocol. LDAP is a draft Internet standard directory service
-    protocol that runs over TCP/IP. It can be used to provide a
-    stand-alone directory service, or to provide lightweight access to
-    the X.500 directory.  LDAP is defined by RFC 1777 and RFC 1778.
+	The OpenLDAP Project is pleased to announce the availability
+	of OpenLDAP release 1.2, a suite of the Lightweight Weight
+	Directory Protocol servers, clients, utilities, and development tools.
 
-    This release includes the following components:
+	OpenLDAP is derived from University of Michigan LDAP release 3.3.
+
+	This release includes the following components:
 
 	- slapd - a stand-alone LDAP directory server
 	- slurpd - a stand-alone LDAP replication server
@@ -26,65 +25,68 @@
 	- fax500 - an LDAP-capable mailer that supports remote printing
 	- LDAP tools - A collection of shell-based LDAP utility programs
 
-    In addition, there are some contributed components:
+	In addition, there are some contributed components:
 
-	- web500 - an HTTP-to-LDAP gateway
-	- whois++d - a WHOIS++-to-LDAP gateway
+	- gtk-tool - a demonstration ldap interface written gtk
+	- php3-tool - a demonstration ldap interface written php3 
 	- saucer - a simple command-line oriented client program
+	- whois++d - a WHOIS++-to-LDAP gateway
 
 CHANGES
-
-    Changes since release 3.2 of LDAP include
-
-	- slurpd has been rewritten as a single process threaded daemon
-	- ldaptools (ldapsearch, etc) now support the LDIF format
-	- support for LDAP URLs added to libldap
-	- improved support for LDAP referrals in libldap
-	- preliminary test scripts included
-	- support for additional platforms
-	- various bug fixes and build fixes
-
-    See the CHANGES file in the distribution for more details.
+	Changes from OpenLDAP 1.1
+	- ldappasswd tool, password prompting, salted MD5/SHA1 support
+	- platforms updates, and
+	- numerous bug fixes and build changes.
+
+	Changes from OpenLDAP 1.0
+	- improved build environment with dynamic library support,
+	- externally configurable client library support: ldap.conf(5),
+	- improved password security features include SHA1, MD5, crypt(3)
+	  user and root passwords instead of clear-text password
+	- integrated SDK and tools for MS NT,
+	- platforms updates, and
+	- numerous bug fixes and build changes.
+
+	Changes from U. Mich release 3.3
+	- TCP Wrappers support added to slapd,
+	- Berkeley DB2 compatibility added to slapd,
+	- ACL enhancements including Access by Group and POSIX regex(3) support,
+	- platforms updates, and
+	- numerous bug fixes and build changes.
+
+	See the CHANGES file in the distribution for more details.
 
 AVAILABILITY
 
-    This software is freely available to anyone for any lawful purpose,
-    subject to the U-M copyright notice and disclaimer.  The software is
-    available for anonymous ftp from the following location:
+	This software is available under the OpenLDAP Public License.
+	For download information is available at:
 
-	ftp://terminator.rs.itd.umich.edu/ldap/ldap-3.3.tar.Z
+		http://www.OpenLDAP.org/software/download/
 
 SUPPORT
 
-    The software is provided as is without any express or implied
-    warranty, but there is a bug reporting mail address which is
-    responded to on a best-effort basis:
-
-	ldap-support@umich.edu
+	The software is provided as is without any express or implied
+	warranty, but there is a bug reporting mail address which is
+	responded to on a best-effort basis:
 
-    In addition, there is a discussion list for issues relating to this
-    implementation of ldap:
+		OpenLDAP-bugs@OpenLDAP.org
 
-	ldap@umich.edu			-- discussion list
-	ldap-request@umich.edu		-- to join the list
+	In addition, there are also a number of discussion lists
+	related OpenLDAP.  A list of mailing lists is available at:
 
-    Comments or questions about the LDAP protocol in general should be
-    sent to the IETF ASID discussion group:
+		http://www.OpenLDAP.org/lists/
 
-	ietf-asid@umich.edu		-- discussion list
-	ietf-asid-request@umich.edu	-- to join the list
+	The OpenLDAP home page containing lots of interesting information
+	and online documentation is available at this URL:
 
-    An LDAP home page containing lots of interesting information and
-    online documentation is available at this URL:
-
-        http://www.umich.edu/~rsug/ldap/
+		http://www.OpenLDAP.org/
 
 SUPPORTED PLATFORMS
 
-    This release has been ported to many UNIX platforms, including
-    SunOS 4.1.x, Solaris 2.x, Ultrix 4.3, HP-UX 9.05, AIX 3.2.5,
-    SCO, FreeBSD, NetBSD, LINUX, IRIX, Digital Unix (OSF/1), and
-    NeXTSTEP 3.2.  This release has also been ported to VMS.
+	This release has been ported to many UNIX (and UNIX-like) platforms
+	including AIX, Digital UNIX (OSF/1), FreeBSD, HP-UX, IRIX, Linux,
+	NetBSD, NexTSTEP, OpenBSD, SCO, Solaris, SunOS, and Ultrix.
+
+	The client libraries and some clients have also been ported to
+	MS Windows 95/NT.
 
-    The client libraries and some clients have also been ported to
-    MacOS 7.x, MSDOS (some TCP stacks), and MS Windows 3.1/95/NT.

COPYRIGHT

-Copyright (c) 1992-1996 Regents of the University of Michigan.
+Copyright 1998,1999 The OpenLDAP Foundation, Redwood City, California, USA
+All rights reserved.
+
+Redistribution and use in source and binary forms are permitted only
+as authorized by the OpenLDAP Public License.  A copy of this
+license is available at http://www.OpenLDAP.org/license.html or
+in file LICENSE in the top-level directory of the distribution.
+
+This work is derived from the University of Michigan LDAP v3.3
+distribution.  Information concerning is available at
+http://www.umich.edu/~dirsvcs/ldap/ldap.html or from
+ldap-support@umich.edu. 
+
+This work also contains materials derived from public sources.
+
+Additional Information about OpenLDAP can be obtained at:
+    http://www.openldap.org/
+
+or by sending e-mail to:
+    info@OpenLDAP.org
+
+---
+
+Portions Copyright (c) 1992-1996 Regents of the University of Michigan.
 All rights reserved.
 
 Redistribution and use in source and binary forms are permitted

INSTALL

-Making and Installing the U-M LDAP Distribution
+Making and Installing the OpenLDAP Distribution
 
+**
 ** It is recommended that you read or at least skim through ALL of the
 ** instructions in this file before attempting to build the software.
+**
+** The OpenLDAP Installation FAQ is available at:
+**    http://www.openldap.org/faq/index.cgi?file=8
+**
+** You should also check for platform specific hints.
+** These are located in doc/install/hints or:
+**    http://www.openldap.org/faq/index.cgi?file=9
+**
 
 If you want to build binaries for more than one platform from a single
 source tree, skip ahead to the "Building LDAP For More Than One Platform"
-section near the end of this file. If you are planning to run slapd,
-you should read the "SLAPD and SLURPD Administrator's Guide", found in
-the doc/guides/ directory within the distribution.
+section near the end of this file.
 
 If you simply want to build LDAP for a single machine platform, follow
 these steps:
 
  1. untar the distribution and cd to the top:
 
-	% zcat ldap-3.3.tar.Z | tar xf -
-	% cd ldap-3.3
+	% tar xfz openldap-VERSION.tgz
+	% cd ldap
 
     If you are reading this file, you probably have already done this!
 
+ 2. Type:
+	% ./configure --help
 
- 2. edit the files Make-common and include/ldapconfig.h.edit to configure
+	to list available configuration options.   A description of
+	these options is provided in the 'CONFIGURE OPTIONS' section
+	below.
+
+	The configure script uses environmental variables for
+	determining compiler/linker options.  See the HINTS
+	section for commonly used settings. 
+
+	These environment variables are used: 
+		CC			C Compiler	(cc, ecgs)
+		CFLAGS		C Flags		(-ansi)
+		CPPFLAGS	CPP Flags	(-I/path/include -Ddef)
+		LDFLAGS		LDFLAGS		(-L/path/lib)
+		LIBS		LIBS		(-llib)
+
+	See the 'USING ENVIRONMENT VARIABLES' section for information
+	on how to use the variables. 
+
+ 3. edit the file include/ldapconfig.h.edit to configure
     the software for your site (the files are well-commented):
 
-	% vi Make-common
 	% vi include/ldapconfig.h.edit
 
-    Note that you should NOT need to edit the Makefile located at the
-    top of the distribution.
+ 4. Configure the build system
 
-    If you just want to see if things will build, you can leave the
-    configuration alone and change it later.
+	% [env settings] ./configure [options]
 
-    If you have the ISODE package built and want to build the
-    LDAP-to-X.500 server (ldapd), be sure to uncomment the appropriate
-    lines near the end of the Make-common file.  By default only the
-    stand-alone server, LDAP libraries and client software are built.
+	If all goes well, the configure script with auto-detect the
+	appropriate settings.  Use configure enable/with options and/or
+	environment variables to obtain desired results.
 
- 3. make the software:
+ 5. Build dependencies
 
-	% make
+	% make depend
+
+ 6. Build the system
 
-    If all goes well, then make will figure out what platform you are on,
-    pick a compiler to use, construct Makefiles, and build everything.
-    If you see a message like "unknown platform..." LDAP has probably not
-    been set up to build on your machine.  See the file build/PORTS for
-    hints on what to do in that case.
-
-    Note that if your make does not use the Bourne (sh) shell by
-    default when executing internal scripts (reportedly the case on SGI
-    machines at least), you will need to run the make explicitly from
-    within a Bourne shell.  If you a syntax error such as "Missing ]"
-    when you do the make under your usual shell, try this:
-
-	% sh
-	$ make
-
-    If you don't like the some of the platform-specific options chosen
-    by the automatic build process (such as the compiler to use, etc),
-    you can intervene and edit them before anything is actually compiled
-    by explicitly doing a "make platform" step, editing the .make-platform
-    file (actually a link to the file to be edited), and then doing a
-    regular make:
-
-	% make platform
-	% vi .make-platform
 	% make
 
-    If you want to choose the build platform yourself from among those that
-    the distribution supports, cd to the appropriate directory underneath
-    build/platforms and make from there.  For example, if you are on a
-    machine running SunOS 4.1.4 and you want to force the use of the cc
-    compiler, you would do this:
+    If all goes well, the system will build as configured.  If not,
+	return to step 4 after reviewing the configuration settings.
 
-	% cd build/platforms/sunos4-cc
+	You may want to consult the doc/install/hints file for your
+	platform.
+
+ 7. Test the standalone system
+
+	This step requires the standalone LDAP server (slapd) with
+	LDBM support.
+
+	% cd tests
 	% make
 
-    If you want to run some simple tests after the build is complete, you
-    can do this:
+	If all goes well, the system has been built as configured.  If not,
+	return to step 4 after reviewing your configuration settings.
 
-	% make test
+	You may want to consult the doc/install/hints file for your
+	platform.
 
- 4. install the binaries and man pages.  You may need to be superuser to
+ 8. install the binaries and man pages.  You may need to be superuser to
     do this (depending on where you are installing things):
 
 	% su
 	# make install
 
-    That's it!  See the man pages for the individual clients for information
-    on configuring and using them.  Eventually you will probably want to
-    edit the configuration files used by the various clients (installed in
-    the LDAP etc directory).  The files are:
+    That's it!
 
+	See the man pages for the individual applications for
+	information on configuring and using them.  You may also want
+	to edit the configuration files used by the various clients.
+	These configuration files are located in the OpenLDAP
+	configuration directory (normally /usr/local/etc/openldap).
+
+	ldap.conf            - LDAP defaults
 	ldapfilter.conf      - search filter configuration
-	ldapfriendly         - mapping of X.500 names to human-friendly names
 	ldapsearchprefs.conf - search object definitions
 	ldaptemplates.conf   - display template definitions
 
     There are section 5 man pages for all of these files.
 
+ 9. edit client configuration files as needed.
+	See ldap.conf(5) for details.
+
+10. edit server configuration files as needed.
+	See slapd.conf(5) if running slapd.
+	See ldapd.conf(5) if running ldapd.
+
 
 Building LDAP For More Than One Platform
 
 It is now possible to build LDAP for more than one platform from the same
-source tree.  This is accomplished by some rules in the Makefiles that
-create a shadow (linked) directory tree where the binaries are placed.
+source tree.  This is accomplished by using make(1) VPATH support.  If
+your make(1) program is old and doesn't have VPATH support, install GNU
+Make.
 
 Follow these steps for each different platform:
 
- 1. move to the directory that matches the platform and compiler you
-    want to build for and type make.  The directories are all located
-    underneath the build/platforms directory.  If your platform is not
-    there, you may need to do a port - see the build/PORTS file for
-    more information.  For a Sun running SunOS 4.1.4, you might do
-    this:
+ 1.	Create a directory for the platform object files.
 
-	% cd build/platforms/sunos4-cc
-	% make links
+	% mkdir obj-platform
 
-    This will create a linked source area.
+ 2. Change your working directory to the platform object directory.
 
+	% cd obj-platform
 
- 2. move to the new directory and make as for a single platform.  Follow steps
-    1-4 above to accomplish this.  For example:
+ 3. Configure the build system
 
-	% cd obj-sunos4-cc
-	% make
+	% [env settings] ../configure --src-dir=.. [options]
+
+		( replace ".." with the appropriate path )
+
+ 4. Continue as above (starting at step 6).
+
+	Note: make depend in VPATH environment is not yet supported.
+
+
+CONFIGURE OPTIONS
+
+Regrettably, this section has not been written (yet).  See
+"./configure --help" for current list of options.  For general
+information about how to use "configure", please read:
+	doc/install/configure
+
+
+USING ENVIRONMENT VARIABLES
+
+The configure script will also use your environmental
+variables for determining compiler/linker options.   This can
+be used to manual specify features and compilation options.
+
+NOTE: If you change environment setting, be sure to remove
+	any config.cache before running ./configure.
+
+Supported Environmental Variables
+	CC			C compiler		(cc, egcc)
+	CFLAGS		C flags			(-ansi)
+	CPPFLAGS	cpp flags		(-I/path/include -Ddef)
+	LDFLAGS		ld flags		(-L/usr/local/lib)
+	LIBS		libraries		(-llib)
+	PATH		command path	/usr/local/bin:/usr/bin:/bin
+
+* Including alternative compilers
+	Use the CC environment variable to tell configure to
+	use a specific compiler.  For example, to use ecgs
+	instead of the compiler configure choose, use:
+
+	[env] CC=egcc ./configure 
+
+	You can also use CC use specific flags with the
+	specified compiler.  For example, to require strict
+	ANSI C using the GNU C Compiler, use:
+
+	[env] CC="gcc -ansi -pedantic" ./configure
+
+	(you can use CFLAGS to specify compiler flags)
+
+* Preprocessor Flags
+	You may specify additional preprocessor flags by setting
+	CPPFLAGS.  For example, if you would like to use headers
+	installed in /usr/local/include, use:
+
+	[env] CPPFLAGS="-I/usr/local/include" ./configure
+
+	You can also use CPPFLAGS to specify preprocessor macros.
+
+	[env] CPPFLAGS="-D__SPECIAL_FLAG__" ./configure
+
+* Linker Flags
+	You may specify additional linker flags by setting LDFLAGS.
+	For example, if you would like to use libraries installed
+	in /usr/local/lib, use:
+
+	[env] LDFLAGS="-L/usr/local/lib" ./configure
+
+	You can also use CPPFLAGS to specify linker flags:
+
+	[env] LDFLAGS="-Bstatic" ./configure
+
+* Path
+	You may alter your path to affect configure ability to
+	find (or not find) commands.  For example, to have configure
+	additionally look in /usr/css/bin for commands, use:
+
+	[env] PATH="/usr/css/bin:$PATH" ./configure
+	
+
+HINTS
+
+* Platform specific hints are available in doc/install/hints.
 
-    That's all there is to it.  You can also create the linked source area(s)
-    by just typing "make links" at the top of the distribution, in which case
-    the Makefile will try to automatically determine the platform and
-    compiler.
+* Use software under installed in /usr/local/{include,lib}
+	[env] \
+		CPPFLAGS="-I/usr/local/include" \
+		LDFLAGS="-L/usr/local/lib" \
+		./configure
 
 
-End of LDAP INSTALL file.
+End of OpenLDAP INSTALL file.

LICENSE

+The OpenLDAP Public License
+
+Version 1.4, 18 January 1999
+Copyright 1998-1999, The OpenLDAP Foundation.
+All Rights Reserved.
+
+Note:
+    This license is derived from the "Artistic License" as distributed
+    with the Perl Programming Language.  As significant differences
+    exist, the complete license should be read.
+
+PREAMBLE
+
+The intent of this document is to state the conditions under which
+a Package may be copied, such that the Copyright Holder maintains
+some semblance of artistic control over the development of the
+package, while giving the users of the package the right to use
+and distribute the Package in a more-or-less customary fashion,
+plus the right to make reasonable modifications.
+
+Definitions:
+
+    "Package" refers to the collection of files distributed by the
+    Copyright Holder, and derivatives of that collection of files
+    created through textual modification.
+
+    "Standard Version" refers to such a Package if it has not been
+    modified, or has been modified in accordance with the wishes
+    of the Copyright Holder.
+
+    "Copyright Holder" is whoever is named in the copyright or
+    copyrights for the package.
+
+    "You" is you, if you're thinking about copying or distributing
+    this Package.
+
+    "Reasonable copying fee" is whatever you can justify on the
+    basis of media cost, duplication charges, time of people
+    involved, and so on.  (You will not be required to justify it
+    to the Copyright Holder, but only to the computing community
+    at large as a market that must bear the fee.)
+
+    "Freely Available" means that no fee is charged for the item
+    itself, though there may be fees involved in handling the item.
+    It also means that recipients of the item may redistribute it
+    under the same conditions they received it.
+
+1. You may make and give away verbatim copies of the source form
+of the Standard Version of this Package without restriction, provided
+that you duplicate all of the original copyright notices and
+associated disclaimers.
+
+2. You may apply bug fixes, portability fixes and other modifications
+derived from the Public Domain or from the Copyright Holder.  A
+Package modified in such a way shall still be considered the Standard
+Version.
+
+3. You may otherwise modify your copy of this Package in any way,
+provided that you insert a prominent notice in each changed file
+stating how and when you changed that file, and provided that you
+do at least ONE of the following:
+
+    a) place your modifications in the Public Domain or otherwise
+    make them Freely Available, such as by posting said modifications
+    to Usenet or an equivalent medium, or placing the modifications
+    on a major archive site such as uunet.uu.net, or by allowing
+    the Copyright Holder to include your modifications in the
+    Standard Version of the Package.
+
+    b) use the modified Package only within your corporation or
+    organization.
+
+    c) rename any non-standard executables so the names do not
+    conflict with standard executables, which must also be provided,
+    and provide a separate manual page for each non-standard
+    executable that clearly documents how it differs from the
+    Standard Version.
+
+    d) make other distribution arrangements with the Copyright
+    Holder.
+
+4. You may distribute the programs of this Package in object code
+or executable form, provided that you do at least ONE of the
+following:
+
+    a) distribute a Standard Version of the executables and library
+    files, together with instructions (in the manual page or
+    equivalent) on where to get the Standard Version.
+
+    b) accompany the distribution with the machine-readable source
+    of the Package with your modifications.
+
+    c) accompany any non-standard executables with their corresponding
+    Standard Version executables, giving the non-standard executables
+    non-standard names, and clearly documenting the differences in
+    manual pages (or equivalent), together with instructions on
+    where to get the Standard Version.
+
+    d) make other distribution arrangements with the Copyright
+    Holder.
+
+5. You may charge a reasonable copying fee for any distribution of
+this Package.  You may charge any fee you choose for support of
+this Package.  You may not charge a fee for this Package itself.
+However, you may distribute this Package in aggregate with other
+(possibly commercial) programs as part of a larger (possibly
+commercial) software distribution provided that you do not advertise
+this Package as a product of your own.
+
+6. The scripts and library files supplied as input to or produced
+as output from the programs of this Package do not automatically
+fall under the copyright of this Package, but belong to whomever
+generated them, and may be sold commercially, and may be aggregated
+with this Package.
+
+7. C subroutines supplied by you and linked into this Package in
+order to emulate subroutines and variables defined by this Package
+shall not be considered part of this Package, but are the equivalent
+of input as in Paragraph 6, provided these subroutines do not change
+the behavior of the Package in any way that would cause it to fail
+the regression tests for the Package.
+
+8. Software supplied by you and linked with this Package in order
+to use subroutines and variables defined by this Package shall not
+be considered part of this Package and do not automatically fall
+under the copyright of this Package.  Executables produced
+by linking your software with this Package may be used and
+redistributed without restriction and may be sold commercially
+so long as the primary function of your software is different
+than the package itself.
+
+9. The name of the Copyright Holder may not be used to endorse or
+promote products derived from this software without specific prior
+written permission.
+
+10. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
+IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
+WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
+
+The End

Makefile.in

+# Master Makefile for OpenLDAP
+##
+## Copyright 1998,1999 The OpenLDAP Foundation, Redwood City, California, USA
+## All rights reserved.
+##
+## Redistribution and use in source and binary forms are permitted only
+## as authorized by the OpenLDAP Public License.  A copy of this
+## license is available at http://www.OpenLDAP.org/license.html or
+## in file LICENSE in the top-level directory of the distribution.
+##
+
+SUBDIRS= include libraries clients servers # contrib
+CLEANDIRS= tests doc
+INSTALLDIRS= doc
+
+makefiles:	FORCE
+	./config.status
+
+# force a make all before make install
+#	only done at the top-level
+install-common: all FORCE
+
+clean-local: FORCE
+	$(RM) config.log
+
+veryclean-local: FORCE
+	$(RM) config.cache config.status libtool stamp-h stamp-h.in
+
+distclean: veryclean FORCE

README

-UM-LDAP 3.3 README file
+OpenLDAP 1.1.1 README
+	This is the OpenLDAP Release 1.1.1.
 
-    This is the UM-LDAP version 3.3 distribution.  For a description of
-    what this distribution contains, see the ANNOUNCEMENT file in this
-    directory.  For a description of changes from previous releases,
-    see the CHANGES file in this directory.  For a more detailed
-    description of how to make and install the distribution, see the
-    INSTALL file in this directory.  For more information on making and
-    installing slapd, see the "SLAPD and SLURPD Administrator's Guide"
-    in the doc/guides/ directory.
+	For a description of what this distribution contains, see the
+	ANNOUNCEMENT file in this directory.  For a description of
+	changes from previous releases, see the CHANGES file in this
+	directory.
+
+	For a more detailed description of how to make an install the
+	distribution, see the INSTALL file in this directory.  Additional
+	installation information, such as per platform hints can be found
+	in the doc/install directory.
+
+	For more information:
+		http://www.OpenLDAP.org/software/
+
+
+REQUIRED SOFTWARE
+	Build OpenLDAP requires the following software components:
+
+	Base system (libraries and tools):
+		Standard C compiler, headers, and libraries
+		POSIX REGEX headers and libraries
+
+	SLAPD:
+		LDBM compatible datastore
+			(Sleepycat Berkeley DB 2.3.16 or GDBM)
+
+	SLURPD:
+		LTHREAD compatible thread package
+			(POSIX pthreads, MIT pthreads, Mach Cthreads or Sun LWP)
+
+	LDAPD:
+		ISODE compatible X.500 distribution
+
+	CLIENTS/CONTRIB ware:
+		Depends on package.  See per package README.
+		
 
 MAKING AND INSTALLING THE DISTRIBUTION
+	This is a quick guide.  For details, see the INSTALL file.
+
+	% ./configure
+		configure OpenLDAP for current platform
 
-    You should be able to make and install the distribution with a pretty
-    standard default configuration by typing the following commands
+	% make depend
+		this will create dependency information
+
+	% make 
+		this will build the system
 
-	% make
 	% su
 	# make install
 
-    in this directory.  This should produce something that basically
-    works.
+	in this directory.  This should produce something that basically
+	works.  You can "cd tests; make" to verify the build.
 
-    You will probably want to do a little configuration to suit your
-    site, though.  There are two files you might want to edit:
+	See the INSTALL file in this directory for more information.
 
-	Make-common		   This file contains definitions for
-				   where things will be installed, where
-				   to find various things, etc.  If you
-				   want to build an ldap server, you'll
-				   definitely need to edit this file
 
-	include/ldapconfig.h.edit  This file contains #defines used
-				   by many parts of the distribution.
-				   You'll at least want to change
-				   DEFAULT_BASE.
+DOCUMENTATION
+	There are man pages for most programs in the distribution and
+	routines in the various libraries.  See ldap(3) for details.
 
-    See the INSTALL file in this directory for more information.
+	Additional documentation can be found in the doc directory.
+		doc/devel   Developer Information
+		doc/drafts  LDAP-related IETF drafts
+		doc/install Installation and Integration
+		doc/man     Raw man(1) pages
+		doc/rfcs    LDAP-related Request for Comments
+
+	There is an OpenLDAP home page available that contains the latest
+	LDAP news, releases announcements, pointers to other LDAP resources,
+	etc..  It is located at:
+		http://www.OpenLDAP.org/
+
+	The OpenLDAP Software FAQ is available at:
+		http://www.openldap.org/faq/index.cgi?file=2
 
-DOCUMENTATION
 
-    There are man pages for most programs in the distribution and
-    routines in the various libraries.  See ldap(3) for details.
+FEEDBACK / PROBLEM REPORTS / DISCUSSIONS
+	We would appreciate any feedback you can provide.  If you have
+	problems, report them using our Issue Tracking System:
 
-    There is a postscript version of an administrator's guide for
-    slapd in doc/guides/slapd.ps.
+		http://www.OpenLDAP.com/its/
 
-    There is an LDAP homepage available that contains the latest
-    LDAP news, releases announcements, pointers to other LDAP resources,
-    etc. You can access it at this URL:
+	or by sending e-mail to:
 
-	http://www.umich.edu/~rsug/ldap/
+		OpenLDAP-its@OpenLDAP.org
 
-FEEDBACK / PROBLEM REPORTS
+	Additional mailing lists are available.  Please see:
 
-    We would appreciate any feedback you can provide.  If you have
-    problems, report them to this address:
+		http://www.OpenLDAP.com/lists/
 
-	ldap-support@umich.edu

acconfig.h

+/*
+ * Copyright 1998,1999 The OpenLDAP Foundation, Redwood City, California, USA
+ * All rights reserved.
+ *
+ * Redistribution and use in source and binary forms are permitted only
+ * as authorized by the OpenLDAP Public License.  A copy of this
+ * license is available at http://www.OpenLDAP.org/license.html or
+ * in file LICENSE in the top-level directory of the distribution.
+ */
+
+#ifndef _LDAP_PORTABLE_H
+#define _LDAP_PORTABLE_H
+
+/* end of preamble */
+@TOP@
+
+/* define this if needed to get reentrant functions */
+#ifndef REENTRANT
+#undef REENTRANT
+#endif
+#ifndef _REENTRANT
+#undef _REENTRANT
+#endif
+
+/* define this if needed to get threadsafe functions */
+#ifndef THREADSAFE
+#undef THREADSAFE
+#endif
+#ifndef _THREADSAFE
+#undef _THREADSAFE
+#endif
+#ifndef THREAD_SAFE
+#undef THREAD_SAFE
+#endif
+#ifndef _THREAD_SAFE
+#undef _THREAD_SAFE
+#endif
+
+/* define this if cross compiling */
+#undef CROSS_COMPILING
+
+/* define this if toupper() requires tolower() check */
+#undef C_UPPER_LOWER
+
+/* define this if sys_errlist is not defined in stdio.h or errno.h */
+#undef DECL_SYS_ERRLIST
+
+/* define this if TIOCGWINSZ is defined in sys/ioctl.h */
+#undef GWINSZ_IN_SYS_IOCTL
+
+/* define if you have berkeley db */
+#undef HAVE_BERKELEY_DB
+
+/* define if you have berkeley db2 */
+#undef HAVE_BERKELEY_DB2
+
+/* define if you have crypt */
+#undef HAVE_CRYPT
+
+/* define if you have DSAP */
+#undef HAVE_DSAP
+
+/* define if you have GDBM */
+#undef HAVE_GDBM
+
+/* define if you have ISODE */
+#undef HAVE_ISODE
+
+/* define if you have Kerberos */
+#undef HAVE_KERBEROS
+
+/* define if you have LinuxThreads */
+#undef HAVE_LINUX_THREADS
+
+/* define if you have Sun LWP (SunOS style) */
+#undef HAVE_LWP
+
+/* define if you have -lncurses */
+#undef HAVE_NCURSES
+
+/* define if you have NDBM */
+#undef HAVE_NDBM
+
+/* define if you have Mach CThreads */
+#undef HAVE_MACH_CTHREADS
+
+/* define if you have POSIX termios */
+#undef HAVE_POSIX_TERMIOS
+
+/* define if you have PP */
+#undef HAVE_PP
+
+/* define if you have POSIX Threads */
+#undef HAVE_PTHREADS
+
+/* define if your POSIX Threads implementation is circa Final Draft */
+#undef HAVE_PTHREADS_FINAL
+
+/* define if your POSIX Threads implementation is circa Draft 4 */
+#undef HAVE_PTHREADS_D4
+
+/* define if you have ptrdiff_t */
+#undef HAVE_PTRDIFF_T
+
+/* define if you have res_search() */
+#ifdef __notdef__
+/* see second res_search define */
+#undef HAVE_RES_SEARCH
+#endif
+
+/* define if you have sched_yield() */
+#ifdef __notdef__
+/* see second sched_yield define */
+#undef HAVE_SCHED_YIELD
+#endif
+
+/* define if you have setproctitle() */
+#undef HAVE_SETPROCTITLE
+
+/* define if you have -lwrap */
+#undef HAVE_TCPD
+
+/* define if you have -ltermcap */
+#undef HAVE_TERMCAP
+
+/* define if you have Sun LWP (Solaris style) */
+#undef HAVE_THR
+
+/* define if you have XTPP */
+#undef HAVE_XTPP
+
+/* define this if select() implicitly yields in thread environments */
+#undef HAVE_YIELDING_SELECT
+
+/* define this for connectionless LDAP support */
+#undef LDAP_CONNECTIONLESS
+
+/* define this to add debugging code */
+#undef LDAP_DEBUG
+
+/* define this for LDAP DNS support */
+#undef LDAP_DNS
+
+/* define this to remove -lldap cache support */
+#undef LDAP_NOCACHE
+
+/* define this for LDAP process title support */
+#undef LDAP_PROCTITLE
+
+/* define this for LDAP referrals support */
+#undef LDAP_REFERRALS
+
+/* define this for LDAP User Interface support */
+#undef LDAP_LIBUI
+
+/* define this to use DB2 in native mode */
+#undef LDBM_USE_DB2
+
+/* define this to use DB2 in compat185 mode */
+#undef LDBM_USE_DB2_COMPAT185
+
+/* define this to use DBBTREE w/ LDBM backend */
+#undef LDBM_USE_DBBTREE
+
+/* define this to use DBHASH w/ LDBM backend */
+#undef LDBM_USE_DBHASH
+
+/* define this to use GDBM w/ LDBM backend */
+#undef LDBM_USE_GDBM
+
+/* define this to use NDBM w/ LDBM backend */
+#undef LDBM_USE_NDBM
+
+/* define this if you want no termcap support */
+#undef NO_TERMCAP
+
+/* define this if you want no thread support */
+#undef NO_THREADS
+
+/* define this for ACL Group support */
+#undef SLAPD_ACLGROUPS
+
+/* define this for ClearText password support */
+#undef SLAPD_CLEARTEXT
+
+/* define this for crypt(3) password support */
+#undef SLAPD_CRYPT
+
+/* define this to use SLAPD LDBM backend */
+#undef SLAPD_LDBM
+
+/* define this to use SLAPD passwd backend */
+#undef SLAPD_PASSWD
+
+/* define this for phonetic support */
+#undef SLAPD_PHONETIC
+
+/* define this for Reverse Lookup support */
+#undef SLAPD_RLOOKUPS
+
+/* define this to use SLAPD shell backend */
+#undef SLAPD_SHELL
+
+
+/* Leave that blank line there!!  Autoheader needs it. */
+
+@BOTTOM@
+/* begin of postamble */
+
+#ifdef HAVE_STDDEF_H
+#	include <stddef.h>
+#endif
+
+#include "ldap_cdefs.h"
+
+#endif /* _LDAP_PORTABLE_H */

acinclude.m4

+dnl Copyright 1998 The OpenLDAP Foundation,  All Rights Reserved.
+dnl COPYING RESTRICTIONS APPLY, See COPYRIGHT file
+dnl
+dnl OpenLDAP Autoconf Macros
+dnl
+builtin(include, build/openldap.m4)dnl

aclocal.m4

+dnl aclocal.m4 generated automatically by aclocal 1.4
+
+dnl Copyright (C) 1994, 1995-8, 1999 Free Software Foundation, Inc.
+dnl This file is free software; the Free Software Foundation
+dnl gives unlimited permission to copy and/or distribute it,
+dnl with or without modifications, as long as this notice is preserved.
+
+dnl This program is distributed in the hope that it will be useful,
+dnl but WITHOUT ANY WARRANTY, to the extent permitted by law; without
+dnl even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+dnl PARTICULAR PURPOSE.
+
+dnl Copyright 1998 The OpenLDAP Foundation,  All Rights Reserved.
+dnl COPYING RESTRICTIONS APPLY, See COPYRIGHT file
+dnl
+dnl OpenLDAP Autoconf Macros
+dnl
+builtin(include, build/openldap.m4)dnl
+
+# Do all the work for Automake.  This macro actually does too much --
+# some checks are only needed if your package does certain things.
+# But this isn't really a big deal.
+
+# serial 1
+
+dnl Usage:
+dnl AM_INIT_AUTOMAKE(package,version, [no-define])
+
+AC_DEFUN(AM_INIT_AUTOMAKE,
+[AC_REQUIRE([AC_PROG_INSTALL])
+PACKAGE=[$1]
+AC_SUBST(PACKAGE)
+VERSION=[$2]
+AC_SUBST(VERSION)
+dnl test to see if srcdir already configured
+if test "`cd $srcdir && pwd`" != "`pwd`" && test -f $srcdir/config.status; then
+  AC_MSG_ERROR([source directory already configured; run "make distclean" there first])
+fi
+ifelse([$3],,
+AC_DEFINE_UNQUOTED(PACKAGE, "$PACKAGE", [Name of package])
+AC_DEFINE_UNQUOTED(VERSION, "$VERSION", [Version number of package]))
+AC_REQUIRE([AM_SANITY_CHECK])
+AC_REQUIRE([AC_ARG_PROGRAM])
+dnl FIXME This is truly gross.
+missing_dir=`cd $ac_aux_dir && pwd`
+AM_MISSING_PROG(ACLOCAL, aclocal, $missing_dir)
+AM_MISSING_PROG(AUTOCONF, autoconf, $missing_dir)
+AM_MISSING_PROG(AUTOMAKE, automake, $missing_dir)
+AM_MISSING_PROG(AUTOHEADER, autoheader, $missing_dir)
+AM_MISSING_PROG(MAKEINFO, makeinfo, $missing_dir)
+AC_REQUIRE([AC_PROG_MAKE_SET])])
+
+#
+# Check to make sure that the build environment is sane.
+#
+
+AC_DEFUN(AM_SANITY_CHECK,
+[AC_MSG_CHECKING([whether build environment is sane])
+# Just in case
+sleep 1
+echo timestamp > conftestfile
+# Do `set' in a subshell so we don't clobber the current shell's
+# arguments.  Must try -L first in case configure is actually a
+# symlink; some systems play weird games with the mod time of symlinks
+# (eg FreeBSD returns the mod time of the symlink's containing
+# directory).
+if (
+   set X `ls -Lt $srcdir/configure conftestfile 2> /dev/null`
+   if test "[$]*" = "X"; then
+      # -L didn't work.
+      set X `ls -t $srcdir/configure conftestfile`
+   fi
+   if test "[$]*" != "X $srcdir/configure conftestfile" \
+      && test "[$]*" != "X conftestfile $srcdir/configure"; then
+
+      # If neither matched, then we have a broken ls.  This can happen
+      # if, for instance, CONFIG_SHELL is bash and it inherits a
+      # broken ls alias from the environment.  This has actually
+      # happened.  Such a system could not be considered "sane".
+      AC_MSG_ERROR([ls -t appears to fail.  Make sure there is not a broken
+alias in your environment])
+   fi
+
+   test "[$]2" = conftestfile
+   )
+then
+   # Ok.
+   :
+else
+   AC_MSG_ERROR([newly created file is older than distributed files!
+Check your system clock])
+fi
+rm -f conftest*
+AC_MSG_RESULT(yes)])
+
+dnl AM_MISSING_PROG(NAME, PROGRAM, DIRECTORY)
+dnl The program must properly implement --version.
+AC_DEFUN(AM_MISSING_PROG,
+[AC_MSG_CHECKING(for working $2)
+# Run test in a subshell; some versions of sh will print an error if
+# an executable is not found, even if stderr is redirected.
+# Redirect stdin to placate older versions of autoconf.  Sigh.
+if ($2 --version) < /dev/null > /dev/null 2>&1; then
+   $1=$2
+   AC_MSG_RESULT(found)
+else
+   $1="$3/missing $2"
+   AC_MSG_RESULT(missing)
+fi
+AC_SUBST($1)])
+
+
+# serial 24 AM_PROG_LIBTOOL
+AC_DEFUN(AM_PROG_LIBTOOL,
+[AC_REQUIRE([AM_ENABLE_SHARED])dnl
+AC_REQUIRE([AM_ENABLE_STATIC])dnl
+AC_REQUIRE([AC_CANONICAL_HOST])dnl
+AC_REQUIRE([AC_PROG_RANLIB])dnl
+AC_REQUIRE([AC_PROG_CC])dnl
+AC_REQUIRE([AM_PROG_LD])dnl
+AC_REQUIRE([AM_PROG_NM])dnl
+AC_REQUIRE([AC_PROG_LN_S])dnl
+dnl
+# Always use our own libtool.
+LIBTOOL='$(SHELL) $(top_builddir)/libtool'
+AC_SUBST(LIBTOOL)dnl
+
+# Check for any special flags to pass to ltconfig.
+libtool_flags=
+test "$enable_shared" = no && libtool_flags="$libtool_flags --disable-shared"
+test "$enable_static" = no && libtool_flags="$libtool_flags --disable-static"
+test "$silent" = yes && libtool_flags="$libtool_flags --silent"
+test "$ac_cv_prog_gcc" = yes && libtool_flags="$libtool_flags --with-gcc"
+test "$ac_cv_prog_gnu_ld" = yes && libtool_flags="$libtool_flags --with-gnu-ld"
+
+# Some flags need to be propagated to the compiler or linker for good
+# libtool support.
+case "$host" in
+*-*-irix6*)
+  # Find out which ABI we are using.
+  echo '[#]line __oline__ "configure"' > conftest.$ac_ext
+  if AC_TRY_EVAL(ac_compile); then
+    case "`/usr/bin/file conftest.o`" in
+    *32-bit*)
+      LD="${LD-ld} -32"
+      ;;
+    *N32*)
+      LD="${LD-ld} -n32"
+      ;;
+    *64-bit*)
+      LD="${LD-ld} -64"
+      ;;
+    esac
+  fi
+  rm -rf conftest*
+  ;;
+
+*-*-sco3.2v5*)
+  # On SCO OpenServer 5, we need -belf to get full-featured binaries.
+  CFLAGS="$CFLAGS -belf"
+  ;;
+esac
+
+# Actually configure libtool.  ac_aux_dir is where install-sh is found.
+CC="$CC" CFLAGS="$CFLAGS" CPPFLAGS="$CPPFLAGS" \
+LD="$LD" NM="$NM" RANLIB="$RANLIB" LN_S="$LN_S" \
+${CONFIG_SHELL-/bin/sh} $ac_aux_dir/ltconfig \
+$libtool_flags --no-verify $ac_aux_dir/ltmain.sh $host \
+|| AC_MSG_ERROR([libtool configure failed])
+])
+
+# AM_ENABLE_SHARED - implement the --enable-shared flag
+# Usage: AM_ENABLE_SHARED[(DEFAULT)]
+#   Where DEFAULT is either `yes' or `no'.  If omitted, it defaults to
+#   `yes'.
+AC_DEFUN(AM_ENABLE_SHARED,
+[define([AM_ENABLE_SHARED_DEFAULT], ifelse($1, no, no, yes))dnl
+AC_ARG_ENABLE(shared,
+changequote(<<, >>)dnl
+<<  --enable-shared         build shared libraries [default=>>AM_ENABLE_SHARED_DEFAULT]
+changequote([, ])dnl
+[  --enable-shared=PKGS    only build shared libraries if the current package
+                          appears as an element in the PKGS list],
+[p=${PACKAGE-default}
+case "$enableval" in
+yes) enable_shared=yes ;;
+no) enable_shared=no ;;
+*)
+  enable_shared=no
+  # Look at the argument we got.  We use all the common list separators.
+  IFS="${IFS= 	}"; ac_save_ifs="$IFS"; IFS="${IFS}:,"
+  for pkg in $enableval; do
+    if test "X$pkg" = "X$p"; then
+      enable_shared=yes
+    fi
+  done
+  IFS="$ac_save_ifs"
+  ;;
+esac],
+enable_shared=AM_ENABLE_SHARED_DEFAULT)dnl
+])
+
+# AM_DISABLE_SHARED - set the default shared flag to --disable-shared
+AC_DEFUN(AM_DISABLE_SHARED,
+[AM_ENABLE_SHARED(no)])
+
+# AM_DISABLE_STATIC - set the default static flag to --disable-static
+AC_DEFUN(AM_DISABLE_STATIC,
+[AM_ENABLE_STATIC(no)])
+
+# AM_ENABLE_STATIC - implement the --enable-static flag
+# Usage: AM_ENABLE_STATIC[(DEFAULT)]
+#   Where DEFAULT is either `yes' or `no'.  If omitted, it defaults to
+#   `yes'.
+AC_DEFUN(AM_ENABLE_STATIC,
+[define([AM_ENABLE_STATIC_DEFAULT], ifelse($1, no, no, yes))dnl
+AC_ARG_ENABLE(static,
+changequote(<<, >>)dnl
+<<  --enable-static         build static libraries [default=>>AM_ENABLE_STATIC_DEFAULT]
+changequote([, ])dnl
+[  --enable-static=PKGS    only build shared libraries if the current package
+                          appears as an element in the PKGS list],
+[p=${PACKAGE-default}
+case "$enableval" in
+yes) enable_static=yes ;;
+no) enable_static=no ;;
+*)
+  enable_static=no
+  # Look at the argument we got.  We use all the common list separators.
+  IFS="${IFS= 	}"; ac_save_ifs="$IFS"; IFS="${IFS}:,"
+  for pkg in $enableval; do
+    if test "X$pkg" = "X$p"; then
+      enable_static=yes
+    fi
+  done
+  IFS="$ac_save_ifs"
+  ;;
+esac],
+enable_static=AM_ENABLE_STATIC_DEFAULT)dnl
+])
+
+
+# AM_PROG_LD - find the path to the GNU or non-GNU linker
+AC_DEFUN(AM_PROG_LD,
+[AC_ARG_WITH(gnu-ld,
+[  --with-gnu-ld           assume the C compiler uses GNU ld [default=no]],
+test "$withval" = no || with_gnu_ld=yes, with_gnu_ld=no)
+AC_REQUIRE([AC_PROG_CC])
+ac_prog=ld
+if test "$ac_cv_prog_gcc" = yes; then
+  # Check if gcc -print-prog-name=ld gives a path.
+  AC_MSG_CHECKING([for ld used by GCC])
+  ac_prog=`($CC -print-prog-name=ld) 2>&5`
+  case "$ac_prog" in
+  # Accept absolute paths.
+  /* | [A-Za-z]:\\*)
+    test -z "$LD" && LD="$ac_prog"
+    ;;
+  "")
+    # If it fails, then pretend we aren't using GCC.
+    ac_prog=ld
+    ;;
+  *)
+    # If it is relative, then search for the first ld in PATH.
+    with_gnu_ld=unknown
+    ;;
+  esac
+elif test "$with_gnu_ld" = yes; then
+  AC_MSG_CHECKING([for GNU ld])
+else
+  AC_MSG_CHECKING([for non-GNU ld])
+fi
+AC_CACHE_VAL(ac_cv_path_LD,
+[if test -z "$LD"; then
+  IFS="${IFS= 	}"; ac_save_ifs="$IFS"; IFS="${IFS}:"
+  for ac_dir in $PATH; do
+    test -z "$ac_dir" && ac_dir=.
+    if test -f "$ac_dir/$ac_prog"; then
+      ac_cv_path_LD="$ac_dir/$ac_prog"
+      # Check to see if the program is GNU ld.  I'd rather use --version,
+      # but apparently some GNU ld's only accept -v.
+      # Break only if it was the GNU/non-GNU ld that we prefer.
+      if "$ac_cv_path_LD" -v 2>&1 < /dev/null | egrep '(GNU|with BFD)' > /dev/null; then
+	test "$with_gnu_ld" != no && break
+      else
+        test "$with_gnu_ld" != yes && break
+      fi
+    fi
+  done
+  IFS="$ac_save_ifs"
+else
+  ac_cv_path_LD="$LD" # Let the user override the test with a path.
+fi])
+LD="$ac_cv_path_LD"
+if test -n "$LD"; then
+  AC_MSG_RESULT($LD)
+else
+  AC_MSG_RESULT(no)
+fi
+test -z "$LD" && AC_MSG_ERROR([no acceptable ld found in \$PATH])
+AC_SUBST(LD)
+AM_PROG_LD_GNU
+])
+
+AC_DEFUN(AM_PROG_LD_GNU,
+[AC_CACHE_CHECK([if the linker ($LD) is GNU ld], ac_cv_prog_gnu_ld,
+[# I'd rather use --version here, but apparently some GNU ld's only accept -v.
+if $LD -v 2>&1 </dev/null | egrep '(GNU|with BFD)' 1>&5; then
+  ac_cv_prog_gnu_ld=yes
+else
+  ac_cv_prog_gnu_ld=no
+fi])
+])
+
+# AM_PROG_NM - find the path to a BSD-compatible name lister
+AC_DEFUN(AM_PROG_NM,
+[AC_MSG_CHECKING([for BSD-compatible nm])
+AC_CACHE_VAL(ac_cv_path_NM,
+[case "$NM" in
+/* | [A-Za-z]:\\*)
+  ac_cv_path_NM="$NM" # Let the user override the test with a path.
+  ;;
+*)
+  IFS="${IFS= 	}"; ac_save_ifs="$IFS"; IFS="${IFS}:"
+  for ac_dir in /usr/ucb /usr/ccs/bin $PATH /bin; do
+    test -z "$ac_dir" && ac_dir=.
+    if test -f $ac_dir/nm; then
+      # Check to see if the nm accepts a BSD-compat flag.
+      # Adding the `sed 1q' prevents false positives on HP-UX, which says:
+      #   nm: unknown option "B" ignored
+      if ($ac_dir/nm -B /dev/null 2>&1 | sed '1q'; exit 0) | egrep /dev/null >/dev/null; then
+        ac_cv_path_NM="$ac_dir/nm -B"
+      elif ($ac_dir/nm -p /dev/null 2>&1 | sed '1q'; exit 0) | egrep /dev/null >/dev/null; then
+        ac_cv_path_NM="$ac_dir/nm -p"
+      else
+        ac_cv_path_NM="$ac_dir/nm"
+      fi
+      break
+    fi
+  done
+  IFS="$ac_save_ifs"
+  test -z "$ac_cv_path_NM" && ac_cv_path_NM=nm
+  ;;
+esac])
+NM="$ac_cv_path_NM"
+AC_MSG_RESULT([$NM])
+AC_SUBST(NM)
+])
+
+
+# serial 1
+
+# @defmac AC_PROG_CC_STDC
+# @maindex PROG_CC_STDC
+# @ovindex CC
+# If the C compiler in not in ANSI C mode by default, try to add an option
+# to output variable @code{CC} to make it so.  This macro tries various
+# options that select ANSI C on some system or another.  It considers the
+# compiler to be in ANSI C mode if it handles function prototypes correctly.
+#
+# If you use this macro, you should check after calling it whether the C
+# compiler has been set to accept ANSI C; if not, the shell variable
+# @code{am_cv_prog_cc_stdc} is set to @samp{no}.  If you wrote your source
+# code in ANSI C, you can make an un-ANSIfied copy of it by using the
+# program @code{ansi2knr}, which comes with Ghostscript.
+# @end defmac
+
+AC_DEFUN(AM_PROG_CC_STDC,
+[AC_REQUIRE([AC_PROG_CC])
+AC_BEFORE([$0], [AC_C_INLINE])
+AC_BEFORE([$0], [AC_C_CONST])
+dnl Force this before AC_PROG_CPP.  Some cpp's, eg on HPUX, require
+dnl a magic option to avoid problems with ANSI preprocessor commands
+dnl like #elif.
+dnl FIXME: can't do this because then AC_AIX won't work due to a
+dnl circular dependency.
+dnl AC_BEFORE([$0], [AC_PROG_CPP])
+AC_MSG_CHECKING(for ${CC-cc} option to accept ANSI C)
+AC_CACHE_VAL(am_cv_prog_cc_stdc,
+[am_cv_prog_cc_stdc=no
+ac_save_CC="$CC"
+# Don't try gcc -ansi; that turns off useful extensions and
+# breaks some systems' header files.
+# AIX			-qlanglvl=ansi
+# Ultrix and OSF/1	-std1
+# HP-UX			-Aa -D_HPUX_SOURCE
+# SVR4			-Xc -D__EXTENSIONS__
+for ac_arg in "" -qlanglvl=ansi -std1 "-Aa -D_HPUX_SOURCE" "-Xc -D__EXTENSIONS__"
+do
+  CC="$ac_save_CC $ac_arg"
+  AC_TRY_COMPILE(
+[#include <stdarg.h>
+#include <stdio.h>
+#include <sys/types.h>
+#include <sys/stat.h>
+/* Most of the following tests are stolen from RCS 5.7's src/conf.sh.  */
+struct buf { int x; };
+FILE * (*rcsopen) (struct buf *, struct stat *, int);
+static char *e (p, i)
+     char **p;
+     int i;
+{
+  return p[i];
+}
+static char *f (char * (*g) (char **, int), char **p, ...)
+{
+  char *s;
+  va_list v;
+  va_start (v,p);
+  s = g (p, va_arg (v,int));
+  va_end (v);
+  return s;
+}
+int test (int i, double x);
+struct s1 {int (*f) (int a);};
+struct s2 {int (*f) (double a);};
+int pairnames (int, char **, FILE *(*)(struct buf *, struct stat *, int), int, int);
+int argc;
+char **argv;
+], [
+return f (e, argv, 0) != argv[0]  ||  f (e, argv, 1) != argv[1];
+],
+[am_cv_prog_cc_stdc="$ac_arg"; break])
+done
+CC="$ac_save_CC"
+])
+if test -z "$am_cv_prog_cc_stdc"; then
+  AC_MSG_RESULT([none needed])
+else
+  AC_MSG_RESULT($am_cv_prog_cc_stdc)
+fi
+case "x$am_cv_prog_cc_stdc" in
+  x|xno) ;;
+  *) CC="$CC $am_cv_prog_cc_stdc" ;;
+esac
+])
+
+dnl From Jim Meyering.
+
+# serial 1
+
+AC_DEFUN(AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL,
+[AC_REQUIRE([AM_SYS_POSIX_TERMIOS])
+ AC_CACHE_CHECK([whether use of TIOCGWINSZ requires sys/ioctl.h],
+	        am_cv_sys_tiocgwinsz_needs_sys_ioctl_h,
+  [am_cv_sys_tiocgwinsz_needs_sys_ioctl_h=no
+
+  gwinsz_in_termios_h=no
+  if test $am_cv_sys_posix_termios = yes; then
+    AC_EGREP_CPP([yes],
+    [#include <sys/types.h>
+#     include <termios.h>
+#     ifdef TIOCGWINSZ
+        yes
+#     endif
+    ], gwinsz_in_termios_h=yes)
+  fi
+
+  if test $gwinsz_in_termios_h = no; then
+    AC_EGREP_CPP([yes],
+    [#include <sys/types.h>
+#     include <sys/ioctl.h>
+#     ifdef TIOCGWINSZ
+        yes
+#     endif
+    ], am_cv_sys_tiocgwinsz_needs_sys_ioctl_h=yes)
+  fi
+  ])
+  if test $am_cv_sys_tiocgwinsz_needs_sys_ioctl_h = yes; then
+    AC_DEFINE(GWINSZ_IN_SYS_IOCTL,1,
+              [Define if TIOCGWINSZ requires sys/ioctl.h])
+  fi
+])
+
+dnl From Jim Meyering.
+
+# serial 1
+
+AC_DEFUN(AM_SYS_POSIX_TERMIOS,
+[AC_CACHE_CHECK([POSIX termios], am_cv_sys_posix_termios,
+  [AC_TRY_LINK([#include <sys/types.h>
+#include <unistd.h>
+#include <termios.h>],
+  [/* SunOS 4.0.3 has termios.h but not the library calls.  */
+   tcgetattr(0, 0);],
+  am_cv_sys_posix_termios=yes,
+  am_cv_sys_posix_termios=no)])
+])
+
+# From Ulrich Drepper.
+
+# serial 1
+
+AC_DEFUN(AM_TYPE_PTRDIFF_T,
+  [AC_CACHE_CHECK([for ptrdiff_t], am_cv_type_ptrdiff_t,
+     [AC_TRY_COMPILE([#include <stddef.h>], [ptrdiff_t p],
+		     am_cv_type_ptrdiff_t=yes, am_cv_type_ptrdiff_t=no)])
+   if test $am_cv_type_ptrdiff_t = yes; then
+     AC_DEFINE(HAVE_PTRDIFF_T,1,[Define if system has ptrdiff_t type])
+   fi
+])
+

build/db.2.x.README

+Berkeley DB version 2.x and OpenLDAP running threads
+====================================================
+
+Special care has to be taken when building Berkeley DB 2.x
+for use with OpenLDAP as an slapd backend.  If OpenLDAP is with
+threads, so must Berkeley DB.   If OpenLDAP is built without
+threads, so must Berkeley DB.
+
+The configuration tool of Sleepycat's Berkeley DB will automatically
+set appropriate options on IRIX, OSF/1, and SUN Solaris platforms
+(version 2.3.16), as well as FreeBSD (version 2.6.4).  The options
+must be manually defined on other plaforms, e.g. on LINUX.
+
+On PC-LINUX (kernel version 2.0.35, linux kernel threads as imple-
+mented by libpthreads.so.1.60.4) with gcc as the standard compiler
+the environment variable CPPFLAGS must define -D_REENTRANT, while
+building the Berkeley DB package.
+
+DO NOT USE THE -ansi CFLAG, SINCE THEN THE DB PACKAGE'S CONFIGURE
+CANNOT FIND THE X86/GCC SPINLOCKS, WHICH ARE NEEDED FOR THREAD-
+SUPPORT WITH THE BERKELEY DB.
+
+Please check carefully if your platform is not mentioned above.
+
+The OpenLDAP configure tool will most probably find the correct
+configuration itself.   No special action has to be taken
+while building the OpenLDAP package.
+
+Jan, 9th, 1999, /KSp (ksp@openldap.org)
+

build/dir.mk

+## Copyright 1998,1999 The OpenLDAP Foundation
+## COPYING RESTRICTIONS APPLY.  See COPYRIGHT File in top level directory
+## of this package for details.
+##---------------------------------------------------------------------------
+##
+## Makes subdirectories
+##
+
+
+all-common: FORCE
+	@echo "Making all in `$(PWD)`"
+	@for i in $(SUBDIRS) $(ALLDIRS); do 		\
+		echo "  Entering subdirectory $$i";		\
+		( cd $$i; $(MAKE) $(MFLAGS) all );		\
+		echo " ";								\
+	done
+
+install-common: FORCE
+	@echo "Making install in `$(PWD)`"
+	@for i in $(SUBDIRS) $(INSTALLDIRS); do 	\
+		echo "  Entering subdirectory $$i";		\
+		( cd $$i; $(MAKE) $(MFLAGS) install );	\
+		echo " ";								\
+	done
+
+clean-common: FORCE
+	@echo "Making clean in `$(PWD)`"
+	@for i in $(SUBDIRS) $(CLEANDIRS); do		\
+		echo "  Entering subdirectory $$i";		\
+		( cd $$i; $(MAKE) $(MFLAGS) clean );	\
+		echo " ";								\
+	done
+
+veryclean-common: FORCE
+	@echo "Making veryclean in `$(PWD)`"
+	@for i in $(SUBDIRS) $(CLEANDIRS); do		\
+		echo "  Entering subdirectory $$i";		\
+		( cd $$i; $(MAKE) $(MFLAGS) veryclean );	\
+		echo " ";								\
+	done
+
+depend-common: FORCE
+	@echo "Making depend in `$(PWD)`"
+	@for i in $(SUBDIRS) $(DEPENDDIRS); do		\
+		echo "  Entering subdirectory $$i";		\
+		( cd $$i; $(MAKE) $(MFLAGS) depend );	\
+		echo " ";								\
+	done
+
+Makefile: $(top_srcdir)/build/dir.mk

build/info.mk

+## Copyright 1998,1999 The OpenLDAP Foundation
+## COPYING RESTRICTIONS APPLY.  See COPYRIGHT File in top level directory
+## of this package for details.
+##---------------------------------------------------------------------------
+##
+## Makefile Template for Non-Source Directories
+##
+
+Makefile: $(top_srcdir)/build/info.mk

build/lib-shared.mk

+## Copyright 1998,1999 The OpenLDAP Foundation
+## COPYING RESTRICTIONS APPLY.  See COPYRIGHT File in top level directory
+## of this package for details.
+##---------------------------------------------------------------------------
+##
+## Makefile Template for Shared Libraries
+##
+
+LTVERSION = -version-info $(LIBVERSION)
+LINK    = $(LTLINK)
+COMPILE = $(LIBTOOL) --mode=compile $(CC) $(CFLAGS) -c
+MKDEPFLAG = -l
+
+.SUFFIXES: .c .o .lo
+
+.c.lo:
+	$(COMPILE) $<
+
+$(LIBRARY):  version.lo
+	$(LINK) -rpath $(libdir) -o $@ $(OBJS) version.lo
+	$(RM) ../$@;	\
+	(d=`$(PWD)` ; $(LN_S) `$(BASENAME) $$d`/$@ ../$@)
+	$(RM) ../`$(BASENAME) $@ .la`.a;	\
+	(d=`$(PWD)`; t=`$(BASENAME) $@ .la`.a; $(LN_S) `$(BASENAME) $$d`/.libs/$$t ../$$t)
+
+Makefile: $(top_srcdir)/build/lib-shared.mk

build/lib-static.mk

+## Copyright 1998,1999 The OpenLDAP Foundation
+## COPYING RESTRICTIONS APPLY.  See COPYRIGHT File in top level directory
+## of this package for details.
+##---------------------------------------------------------------------------
+##
+## Makefile Template for Static Libraries
+##
+
+$(LIBRARY): version.o
+	$(AR) ru $@ $(OBJS) version.o
+	@$(RANLIB) $@;	\
+	$(RM) ../$@;	\
+	(d=`$(PWD)` ; $(LN_S) `$(BASENAME) $$d`/$@ ../$@)
+
+Makefile: $(top_srcdir)/build/lib-static.mk

build/lib.mk

+## Copyright 1998,1999 The OpenLDAP Foundation
+## COPYING RESTRICTIONS APPLY.  See COPYRIGHT File in top level directory
+## of this package for details.
+##---------------------------------------------------------------------------
+##
+## Makefile Template for Libraries
+##
+
+all-common: $(LIBRARY) $(PROGRAMS)
+
+version.c: $(OBJS) $(srcdir)/Version.c
+	$(RM) $@
+	(u=$${USER-root} v=`$(CAT) $(VERSIONFILE)` d=`$(PWD)` \
+	h=`$(HOSTNAME)` t=`$(DATE)`; $(SED) -e "s|%WHEN%|$${t}|" \
+	-e "s|%WHOANDWHERE%|$${u}@$${h}:$${d}|" \
+	-e "s|%VERSION%|$${v}|" \
+	< $(srcdir)/Version.c > $@)
+
+install-common: FORCE
+
+lint: lint-local FORCE
+	$(LINT) $(DEFS) $(DEFINES) $(SRCS)
+
+lint5: lint5-local FORCE
+	$(5LINT) $(DEFS) $(DEFINES) $(SRCS)
+
+clean-common: 	FORCE
+	$(RM) $(LIBRARY) ../$(LIBRARY) $(XLIBRARY) \
+		$(PROGRAMS) $(XPROGRAMS) $(XSRCS) $(XXSRCS) \
+		*.o *.lo a.out core version.c .libs/*
+
+depend-common: FORCE
+	$(MKDEP) $(DEFS) $(DEFINES) $(SRCS) $(XXSRCS)
+
+lint-local: FORCE
+lint5-local: FORCE
+
+Makefile: $(top_srcdir)/build/lib.mk