PRODUCT uses a configuration system built using the Free Software Foundation's autoconf program.  This system makes Kerberos V5 much simpler to build and reduces the amount of effort required in porting Kerberos V5 to a new platform.

Organization of the Source Directory
====================================

Below is a brief overview of the organization of the complete source directory.  More detailed descriptions follow.

appl
     applications with PRODUCT extensions
clients
     PRODUCT user programs
gen-manpages
     manpages for PRODUCT and the PRODUCT login program
include
     include files
kadmin
     administrative interface to the Kerberos master database
kdc
     the PRODUCT Authentication Service and Key Distribution Center
krb524
     utilities for converting between Kerberos 4 and Kerberos 5
lib
     libraries for use with/by PRODUCT
mac
     source code for building PRODUCT on MacOS
prototype
     templates for source code files
slave
     utilities for propagating the database to slave KDCs
tests
     test suite
util
     various utilities for building/configuring the code, sending bug reports, etc.
windows
     source code for building PRODUCT on Windows (see windows/README)

The appl Directory
------------------

The appl directory contains sample Kerberos application client and server programs.  In previous releases, it contained Kerberized versions of remote access daemons, but those have now been moved to a separate project.

The clients Directory
---------------------

This directory contains the code for several user-oriented programs.

kdestroy
     This program destroys the user's active Kerberos authorization tickets. COMPANY recommends that users kdestroy before logging out.

kinit
     This program prompts users for their Kerberos principal name and password, and attempts to get an initial ticket-granting-ticket for that principal.

klist
     This program lists the Kerberos principal and Kerberos tickets held in a credentials cache, or the keys held in a keytab file.

kpasswd
     This program changes a user's Kerberos password.

ksu
     This program is a Kerberized version of the su program that is meant to securely change the real and effective user ID to that of the target user and to create a new security context.

kvno
     This program acquires a service ticket for the specified Kerberos principals and prints out the key version numbers of each.

The gen-manpages Directory
--------------------------

There are two manual pages in this directory.  One is an introduction to the Kerberos system.  The other describes the .k5login file which allows users to give access with their UID to other users authenticated by the Kerberos system.

The include Directory
---------------------

This directory contains the include files needed to build the Kerberos system.

The kadmin Directory
--------------------

In this directory is the code for the utilities kadmin, kadmin.local, kdb5_util, and ktutil. ktutil is the Kerberos keytab file maintenance utility from which a Kerberos administrator can read, write, or edit entries in a Kerberos V5 keytab or Kerberos V4 srvtab.  kadmin and kadmin.local are command-line interfaces to the Kerberos V5 KADM5 administration system.  kadmin.local runs on the master KDC and does not use Kerberos to authenticate to the database, while kadmin uses Kerberos authentication and an encrypted RPC.  The two provide identical functionalities, which allow administrators to modify the database of Kerberos principals.  kdb5_util allows administrators to perform low-level maintenance procedures on Kerberos and the KADM5 database.  With this utility, databases can be created, destroyed, or dumped to and loaded from ASCII files.  It can also be used to create master key stash files.

The kdc Directory
-----------------

This directory contains the code for the krb5kdc daemon, the Kerberos Authentication Service and Key Distribution Center.

The krb524 Directory
--------------------

This directory contains the code for krb524, a service that converts Kerberos V5 credentials into Kerberos V4 credentials suitable for use with applications that for whatever reason do not use V5 directly.

The lib Directory
-----------------

The lib directory contain 10 subdirectories as well as some definition and glue files.  The crypto subdirectory contains the Kerberos V5 encryption library.  The des425 subdirectory exports the Kerberos V4 encryption API, and translates these functions into calls to the Kerberos V5 encryption API.  The gssapi library contains the Generic Security Services API, which is a library of commands to be used in secure client-server communication.  The kadm5 directory contains the libraries for the KADM5 administration utilities.  The Kerberos 5 database libraries are contained in kdb.  The directories krb4 and krb5 contain the Kerberos 4 and Kerberos 5 APIs, respectively.  The rpc directory contains the API for the Kerberos Remote Procedure Call protocol.

The prototype Directory
-----------------------

This directory contains several template files.  The prototype.h and prototype.c files contain the MIT copyright message and a placeholder for the title and description of the file. prototype.h also has a short template for writing ifdef and ifndef preprocessor statements.  The getopt.c file provides a template for writing code that will parse the options with which a program was called.

The slave Directory
-------------------

This directory contains code which allows for the propagation of the Kerberos principal database from the master KDC to slave KDCs over an encrypted, secure channel.  kprop is the program which actually propagates the database dump file.  kpropd is the Kerberos V5 slave KDC update server which accepts connections from the kprop program.  kslave_update is a script that takes the name of a slave server, and propagates the database to that server if the database has been modified since the last dump or if the database has been dumped since the last propagation.

The util Directory
------------------

This directory contains several utility programs and libraries.  The programs used to configure and build the code, such as autoconf, lndir, kbuild, reconf,  and makedepend, are in this directory.  The profile directory contains most of the functions which parse the Kerberos configuration files (krb5.conf and kdc.conf).  Also in this directory are the Kerberos error table library and utilities (et), the Sub-system library and utilities (ss), database utilities (db2), pseudo-terminal utilities (pty), bug-reporting program send-pr, and a generic support library support used by several of our other libraries.

Build Requirements
==================

In order to build Kerberos V5, you will need approximately 60-70 megabytes of disk space.  The exact amount will vary depending on the platform and whether the distribution is compiled with debugging symbol tables or not.

Your C compiler must conform to ANSI C (ISO/IEC 9899:1990, ``c89''). Some operating systems do not have an ANSI C compiler, or their default compiler requires extra command-line options to enable ANSI C conformance.

If you wish to keep a separate build tree, which contains the compiled *.o file and executables, separate from your source tree, you will need a make program which supports VPATH, or you will need to use a tool such as lndir to produce a symbolic link tree for your build tree.

Unpacking the Sources
=====================

The first step in each of these build procedures is to unpack the source distribution.  The Kerberos V5 distribution comes in a tar file, generally named krb5-RELEASE.tar, which contains a compressed tar file consisting of the sources for all of Kerberos (generally krb5-RELEASE.tar.gz) and a PGP signature for this source tree (generally krb5-RELEASE.tar.gz.asc). COMPANY highly recommends that you verify the integrity of the source code using this signature.

Unpack the compressed tar file in some directory, such as /u1/krb5-RELEASE.  (In the rest of this document, we will assume that you have chosen to unpack the Kerberos V5 source distribution in this directory.  Note that the tarfiles will by default all unpack into the ./krb5-RELEASE directory, so that if your current directory is /u1 when you unpack the tarfiles, you will get /u1/krb5-RELEASE/src, etc.)

Doing the Build
===============

You have a number of different options in how to build Kerberos.  If you only need to build Kerberos for one platform, using a single directory tree which contains both the source files and the object files is the simplest.  However, if you need to maintain Kerberos for a large number of platforms, you will probably want to use separate build trees for each platform. We recommend that you look at OS Incompatibilities, for notes that we have on particular operating systems.

Building Within a Single Tree
-----------------------------

If you don't want separate build trees for each architecture, then use the following abbreviated procedure.

 1. cd /u1/krb5-RELEASE/src

 2. ./configure

 3. make

That's it!

Building with Separate Build Directories
----------------------------------------

If you wish to keep separate build directories for each platform, you can do so using the following procedure.  (Note, this requires that your make program support VPATH.  GNU's make will provide this functionality, for example.)  If your make program does not support this, see the next section.

For example, if you wish to create a build directory for pmax binaries you might use the following procedure:

 1. mkdir /u1/krb5-RELEASE/pmax

 2. cd /u1/krb5-RELEASE/pmax

 3. ../src/configure

 4. make

Building Using lndir
--------------------

If you wish to keep separate build directories for each platform, and you do not have access to a make program which supports VPATH, all is not lost.  You can use the lndir program to create symbolic link trees in your build directory.

For example, if you wish to create a build directory for solaris binaries you might use the following procedure:

 1. mkdir /u1/krb5-RELEASE/solaris

 2. cd /u1/krb5-RELEASE/solaris

 3. /u1/krb5-RELEASE/src/util/lndir `pwd`/../src

 4. ./configure

 5. make

You must give an absolute pathname to lndir because it has a bug that makes it fail for relative pathnames. Note that this version differs from the latest version as distributed and installed by the XConsortium with X11R6. Either version should be acceptable.

Installing the Binaries
=======================

Once you have built Kerberos, you should install the binaries.  You can do this by running:

     % make install

If you want to install the binaries into a destination directory that is not their final destination, which may be convenient if you want to build a binary distribution to be deployed on multiple hosts, you may use:

     % make install DESTDIR=/path/to/destdir

This will install the binaries under DESTDIR/PREFIX, e.g., the user programs will install into DESTDIR/PREFIX/bin, the libraries into DESTDIR/PREFIX/lib, etc.

Note that if you want to test the build (see Testing the Build), you usually do not need to do a make install first.

Some implementations of make allow multiple commands to be run in parallel, for faster builds.  We test our Makefiles in parallel builds with GNU make only; they may not be compatible with other parallel build implementations.

Testing the Build
=================

The Kerberos V5 distribution comes with built-in regression tests.  To run them, simply type the following command while in the top-level build directory (i.e., the directory where you sent typed make to start building Kerberos; see Doing the Build.):

     % make check

However, there are several prerequisites that must be satisfied first:

  * Configure and build Kerberos with Tcl support.  Tcl is used to drive the test suite.  This often means passing --with-tcl to configure to tell it the location of the Tcl configuration script.  (See Options to Configure.)

  * On some operating systems, you have to run make install before running make check, or the test suite will pick up installed versions of Kerberos libraries rather than the newly built ones.  You can install into a prefix that isn't in the system library search path, though.  Alternatively, you can configure with --disable-rpath, which renders the build tree less suitable for installation, but allows testing without interference from previously installed libraries.

  * In order to test the RPC layer, the local system has to be running the portmap daemon and it has to be listening to the regular network interface (not just localhost).

The DejaGnu Tests
-----------------

Some of the built-in regression tests are setup to use the DejaGnu framework for running tests. These tests tend to be more comprehensive than the normal built-in tests as they setup test servers and test client/server activities.

DejaGnu may be found wherever GNU software is archived.

The KADM5 Tests
---------------

Regression tests for the KADM5 system, including the GSS-RPC, KADM5 client and server libraries, and kpasswd, are also included in this release.  Each set of KADM5 tests is contained in a sub-directory called unit-test directly below the system being tested.  For example, lib/rpc/unit-test contains the tests for GSS-RPC.  The tests are all based on DejaGnu (but they are not actually called part of "The DejaGnu tests," whose naming predates the inclusion of the KADM5 system).  In addition, they require the Tool Command Language (TCL) header files and libraries to be available during compilation and some of the tests also require Perl in order to operate.  If all of these resources are not available during configuration, the KADM5 tests will not run.  The TCL installation directory can be specified with the --with-tcl configure option.  (See Options to Configure.)  The runtest and perl programs must be in the current execution path.

If you install DejaGnu, TCL, or Perl after configuring and building Kerberos and then want to run the KADM5 tests, you will need to re-configure the tree and run make at the top level again to make sure all the proper programs are built.  To save time, you actually only need to reconfigure and build in the directories src/kadmin/testing, src/lib/rpc, src/lib/kadm5.

Options to Configure
====================

There are a number of options to configure which you can use to control how the Kerberos distribution is built.  The following table lists the most commonly used options to Kerberos V5's configure program.

--help

     Provides help to configure. This will list the set of commonly used options for building Kerberos.

--prefix=PREFIX

     By default, Kerberos will install the package's files rooted at `/usr/local' as in `/usr/local/bin', `/usr/local/sbin', etc. If you desire a different location, use this option.

--exec-prefix=EXECPREFIX

     This option allows one to separate the architecture independent programs from the configuration files and manual pages.

--localstatedir=LOCALSTATEDIR

     This option sets the directory for locally modifiable single-machine data.  In Kerberos, this mostly is useful for setting a location for the KDC data files, as they will be installed in LOCALSTATEDIR/krb5kdc, which is by default PREFIX/var/krb5kdc.

CC=COMPILER

     Use COMPILER as the C compiler.

CFLAGS=FLAGS

     Use FLAGS as the default set of C compiler flags.

     Note that if you use the native Ultrix compiler on a DECstation you are likely to lose if you pass no flags to cc; md4.c takes an estimated 3,469 billion years to compile if you provide neither the -g flag nor the -O flag to cc.

CPPFLAGS=CPPOPTS

     Use CPPOPTS as the default set of C preprocessor flags.  The most common use of this option is to select certain #define's for use with the operating system's include files.

LD=LINKER

     Use LINKER as the default loader if it should be different from C compiler as specified above.

LDFLAGS=LDOPTS

     This option allows one to specify optional arguments to be passed to the linker. This might be used to specify optional library paths.

--with-krb4

     This option enables Kerberos V4 backwards compatibility using the builtin Kerberos V4 library.

--with-krb4=KRB4DIR

     This option enables Kerberos V4 backwards compatibility using a pre-existing Kerberos V4 installation.  The directory specified by KRB4DIR specifies where the V4 header files should be found (KRB4DIR/include) as well as where the V4 Kerberos library should be found (KRB4DIR/lib).

--without-krb4

     Disables Kerberos V4 backwards compatibility. This prevents Kerberos V4 clients from using the V5 services including the KDC. This would be useful if you know you will never install or need to interact with V4 clients.

--with-netlib[=libs]

     Allows for suppression of or replacement of network libraries. By default, Kerberos V5 configuration will look for -lnsl and -lsocket. If your operating system has a broken resolver library (see Solaris versions 2.0 through 2.3) or fails to pass the tests in src/tests/resolv you will need to use this option.

--with-tcl=TCLPATH

     Some of the unit-tests in the build tree rely upon using a program in Tcl. The directory specified by TCLPATH specifies where the Tcl header file (TCLPATH/include/tcl.h as well as where the Tcl library should be found (TCLPATH/lib).

--enable-shared

     This option will turn on the building and use of shared library objects in the Kerberos build. This option is only supported on certain platforms.

--enable-dns

--enable-dns-for-kdc

--enable-dns-for-realm

     Enable the use of DNS to look up a host's Kerberos realm, or a realm's KDCs, if the information is not provided in krb5.conf. See Hostnames for the Master and Slave KDCs for information about using DNS to locate the KDCs, and Mapping Hostnames onto Kerberos Realms for information about using DNS to determine the default realm.  By default, DNS lookups are enabled for the former but not for the latter.

--disable-kdc-lookaside-cache

     Disables the cache in the KDC which detects retransmitted client requests and resends the previous responses to them.

--with-system-et

     Use an installed version of the error-table support software, the compile_et program, the com_err.h header file and the com_err library.  If these are not in the default locations, you may wish to specify CPPFLAGS=-I/some/dir and LDFLAGS=-L/some/other/dir options at configuration time as well.

     If this option is not given, a version supplied with the Kerberos sources will be built and installed along with the rest of the Kerberos tree, for Kerberos applications to link against.

--with-system-ss

     Use an installed version of the subsystem command-line interface software, the mk_cmds program, the ss/ss.h header file and the ss library.  If these are not in the default locations, you may wish to specify CPPFLAGS=-I/some/dir and LDFLAGS=-L/some/other/dir options at configuration time as well.  See also the SS_LIB option.

     If this option is not given, the ss library supplied with the Kerberos sources will be compiled and linked into those programs that need it; it will not be installed separately.

SS_LIB=libs...

     If -lss is not the correct way to link in your installed ss library, for example if additional support libraries are needed, specify the correct link options here.  Some variants of this library are around which allow for Emacs-like line editing, but different versions require different support libraries to be explicitly specified.

     This option is ignored if --with-system-ss is not specified.

--with-system-db

     Use an installed version of the Berkeley DB package, which must provide an API compatible with version 1.85.  This option is unsupported and untested.  In particular, we do not know if the database-rename code used in the dumpfile load operation will behave properly.

     If this option is not given, a version supplied with the Kerberos sources will be built and installed.  (We are not updating this version at this time because of licensing issues with newer versions that we haven't investigated sufficiently yet.)

DB_HEADER=headername.h

     If db.h is not the correct header file to include to compile against the Berkeley DB 1.85 API, specify the correct header file name with this option.  For example, DB_HEADER=db3/db_185.h.

DB_LIB=libs...

     If -ldb is not the correct library specification for the Berkeley DB library version to be used, override it with this option. For example, DB_LIB=-ldb-3.3.

--with-crypto-impl=IMPL

     Use specified crypto implementation in lieu of the default builtin. Currently only one alternative crypto-system openssl is available and it requires version 1.0.0 or higher of OpenSSL.

For example, in order to configure Kerberos on a Solaris machine using the suncc compiler with the optimizer turned on, run the configure script with the following options:

     % ./configure CC=suncc CFLAGS=-O

For a slightly more complicated example, consider a system where several packages to be used by Kerberos are installed in /usr/foobar, including Berkeley DB 3.3, and an ss library that needs to link against the curses library.  The configuration of Kerberos might be done thus:

     % ./configure CPPFLAGS=-I/usr/foobar/include LDFLAGS=-L/usr/foobar/lib \
                   --with-system-et --with-system-ss --with-system-db \
                   SS_LIB='-lss -lcurses' \
                   DB_HEADER=db3/db_185.h DB_LIB=-ldb-3.3

In previous releases, --with- options were used to specify the compiler and linker and their options.

osconf.h
========

There is one configuration file which you may wish to edit to control various compile-time parameters in the Kerberos distribution: include/stock/osconf.h. The list that follows is by no means complete, just some of the more interesting variables.

Please note: The former configuration file config.h no longer exists as its functionality has been merged into the auto-configuration process. See Options to Configure.

DEFAULT_PROFILE_PATH

     The pathname to the file which contains the profiles for the known realms, their KDCs, etc.  The default value is DefaultDefaultProfilePath.

     The profile file format is no longer the same format as Kerberos V4's krb.conf file.

DEFAULT_KEYTAB_NAME

     The type and pathname to the default server keytab file (the equivalent of Kerberos V4's /etc/srvtab).  The default is DefaultDefaultKeytabName.

DEFAULT_KDC_ENCTYPE

     The default encryption type for the KDC.  The default value is DefaultMasterKeyType.

KDCRCACHE

     The name of the replay cache used by the KDC.  The default value is DefaultKDCRCache.

RCTMPDIR

     The directory which stores replay caches.  The default is to try DefaultRCTmpDirs.

DEFAULT_KDB_FILE

     The location of the default database.  The default value is DefaultDatabaseName.

Shared Library Support
======================

Shared library support is provided for a few operating systems. There are restrictions as to which compiler to use when using shared libraries. In all cases, executables linked with the shared libraries in this build process will have built in the location of the libraries, therefore obliterating the need for special LD_LIBRARY_PATH, et al environment variables when using the programs. Except where noted, multiple versions of the libraries may be installed on the same system and continue to work.

Currently the supported platforms are Solaris 2.6-2.9 (aka SunOS 5.6-5.9), Irix 6.5, Redhat Linux, MacOS 8-10, and Microsoft Windows (using DLLs).

Shared library support has been tested on the following platforms but not exhaustively (they have been built but not necessarily tested in an installed state): Tru64 (aka Alpha OSF/1 or Digital Unix) 4.0, and HP/UX 10.20.

Platforms for which there is shared library support but not significant testing include FreeBSD, OpenBSD, AIX (4.3.3), Linux, NetBSD 1.4.x (i386).

To enable shared libraries on the above platforms, run the configure script with the option --enable-shared.

Operating System Incompatibilities
==================================

This section details operating system incompatibilities with Kerberos V5 which have been reported to the developers at MIT.  If you find additional incompatibilities, and/or discover workarounds to such problems, please send a report via the krb5-send-pr program. Thanks!

AIX
---

The AIX 3.2.5 linker dumps core trying to build a shared libkrb5.a produced with the GNU C compiler.  The native AIX compiler works fine.  This problem is fixed using the AIX 4.1 linker.

Alpha OSF/1 V1.3
----------------

Using the native compiler, compiling with the -O compiler flag causes the asn.1 library to be compiled incorrectly.

Using GCC version 2.6.3 or later instead of the native compiler will also work fine, both with or without optimization.

Alpha OSF/1 V2.0
----------------

There used to be a bug when using the native compiler in compiling md4.c when compiled without either the -O or -g compiler options.  We have changed the code and there is no problem under V2.1, but we do not have access to V2.0 to test and see if the problem would exist there. (We welcome feedback on this issue). There was never a problem in using GCC version 2.6.3.

In version 3.2 and beyond of the operating system, we have not seen this sort of problem with the native compiler.

Alpha OSF/1 (Digital UNIX) V4.0
-------------------------------

The C compiler provided with Alpha OSF/1 V4.0 (a.k.a. Digital UNIX) defaults to an extended K&R C mode, not ANSI C.  You need to provide the -std argument to the compiler (i.e., ./configure CC='cc -std') to enable extended ANSI C mode.  More recent versions of the operating system, such as 5.0, seem to have C compilers which default to -std.

BSDI
----

BSDI versions 1.0 and 1.1 reportedly has a bad sed which causes it to go into an infinite loop during the build.  The work around is to use a sed from somewhere else, such as GNU.  (This may be true for some versions of other systems derived from BSD 4.4, such as NetBSD and FreeBSD.)

HPUX
----

The native (bundled) compiler for HPUX currently will not work, because it is not a full ANSI C compiler.  The optional ANSI C compiler should work as long as you give it the -Ae flag (i.e. ./configure CC='cc -Ae').  This is equivalent to ./configure CC='c89 -D_HPUX_SOURCE', which was the previous recommendation.  This has only been tested recently for HPUX 10.20.

You will need to configure with --disable-shared --enable-static, because as of 1.4 we don't have support for HPUX shared library finalization routines, nor the option (yet) to ignore that lack of support (which means repeated dlopen/dlclose cycles on the Kerberos libraries may not be safe) and build the shared libraries anyways.

You will also need to configure the build tree with --disable-thread-support if you are on HPUX 10 and do not have the DCE development package installed, because that's where the pthread.h header file is found.  (We don't know if our code will work with such a package installed, because according to some HP documentation, their pthread.h has to be included before any other header files, and our code doesn't do that.)

If you use GCC, it may work, but some versions of GCC have omitted certain important preprocessor defines, like __STDC_EXT__ and __hpux.

Solaris versions 2.0 through 2.3
--------------------------------

The gethostbyname() routine is broken; it does not return a fully qualified domain name, even if you are using the Domain Name Service routines.  Since Kerberos V5 uses the fully qualified domain name as the second component of a service principal (i.e, host/tsx-11.mit.edu@ATHENA.MIT.EDU), this causes problems for servers who try to figure out their own fully qualified domain name.

Workarounds:

 1. Supply your own resolver library. (such as bind-4.9.3pl1 available from ftp.vix.com)

 2. Upgrade to Solaris 2.4

 3. Make sure your /etc/nsswitch.conf has `files' before `dns' like:

          hosts:      files dns

     and then in /etc/hosts, make sure there is a line with your workstation's IP address and hostname, with the fully qualified domain name first.  Example:

          18.172.1.4      dcl.mit.edu dcl

     Note that making this change may cause other programs in your environment to break or behave differently.

Solaris 2.X
-----------

You must compile Kerberos V5 without the UCB compatibility libraries.  This means that /usr/ucblib must not be in the LD_LIBRARY_PATH environment variable when you compile it.  Alternatively you can use the -i option to cc, by using the specifying CFLAGS=-i option to configure.

If you are compiling for a 64-bit execution environment, you may need to configure with the option CFLAGS="-D_XOPEN_SOURCE=500 -D__EXTENSIONS__".  This is not well tested; at MIT we work primarily with the 32-bit execution environment.

Solaris 9
---------

Solaris 9 has a kernel race condition which causes the final output written to the slave side of a pty to be lost upon the final close() of the slave device.  This causes the dejagnu-based tests to fail intermittently.  A workaround exists, but requires some help from the scheduler, and the ``make check'' must be executed from a shell with elevated priority limits.

Run something like

priocntl -s -c FX -m 30 -p 30 -i pid nnnn

as root, where nnnn is the pid of the shell whose priority limit you wish to raise.

Sun has released kernel patches for this race condition.  Apply patch 117171-11 for sparc, or patch 117172-11 for x86.  Later revisions of the patches should also work.  It is not necessary to run ``make check'' from a shell with elevated priority limits once the patch has been applied.

SGI Irix 5.X
------------

If you are building in a tree separate from the source tree, the vendors version of make does not work properly with regards to VPATH. It also has problems with standard inference rules in 5.2 (not tested yet in 5.3) so one needs to use GNU's make.

Under 5.2, there is a bug in the optional System V -lsocket library in which the routine gethostbyname() is broken. The system supplied version in -lc appears to work though so one may simply specify --with-netlib option to configure.

In 5.3, gethostbyname() is no longer present in -lsocket and is no longer an issue.

Ultrix 4.2/3
------------

The DEC MIPS platform currently will not support the native compiler, since the Ultrix compiler is not a full ANSI C compiler.  You should use GCC instead.

Using Autoconf
==============

(If you are not a developer, you can skip this section.)

In most of the Kerberos V5 source directories, there is a configure script which automatically determines the compilation environment and creates the proper Makefiles for a particular platform.  These configure files are generated using autoconf, which can be found in the src/util/autoconf directory in the distribution.

Normal users will not need to worry about running autoconf; the distribution comes with the configure files already prebuilt. Developers who wish to modify the configure.in files should see Overview (The Autoconf Manual).

Note that in order to run autoconf, you must have GNU m4 in your path.  Before you use the autoconf in the Kerberos V5 source tree, you may also need to run configure, and then run make in the src/util/autoconf directory in order to properly set up autoconf.

One tool which is provided for the convenience of developers can be found in src/util/reconf.  This program should be run while the current directory is the top source directory.  It will automatically rebuild any configure files which need rebuilding.  If you know that you have made a change that will require that all the configure files need to be rebuilt from scratch, specify the --force option:

     % cd /u1/krb5-RELEASE/src
     % ./util/reconf --force

The developmental sources are a raw source tree (before it's been packaged for public release), without the pre-built configure files. In order to build from such a source tree, you must do:

     % cd krb5/util/autoconf
     % ./configure
     % make
     % cd ../..
     % util/reconf

Then follow the instructions for building packaged source trees (above). To install the binaries into a binary tree, do:

     % cd /u1/krb5-RELEASE/src
     % make all
     % make install DESTDIR=somewhere-else