Current Path : /usr/src/crypto/heimdal/doc/ |
FreeBSD hs32.drive.ne.jp 9.1-RELEASE FreeBSD 9.1-RELEASE #1: Wed Jan 14 12:18:08 JST 2015 root@hs32.drive.ne.jp:/sys/amd64/compile/hs32 amd64 |
Current File : //usr/src/crypto/heimdal/doc/install.texi |
@c $Id: install.texi 16768 2006-02-27 12:26:49Z joda $ @node Building and Installing, Setting up a realm, What is Kerberos?, Top @comment node-name, next, previous, up @chapter Building and Installing Heimdal uses GNU Autoconf to configure for specific hosts, and GNU Automake to manage makefiles. If this is new to you, the short instruction is to run the @code{configure} script in the top level directory, and when that finishes @code{make}. If you want to build the distribution in a different directory from the source directory, you will need a make that implements VPATH correctly, such as GNU make. You will need to build the distribution: @itemize @bullet @item A compiler that supports a ``loose'' ANSI C mode, such as @code{gcc}. @item lex or flex @item awk @item yacc or bison @item a socket library @item NDBM or Berkeley DB for building the server side. @end itemize When everything is built, you can install by doing @kbd{make install}. The default location for installation is @file{/usr/heimdal}, but this can be changed by running @code{configure} with @samp{--prefix=/some/other/place}. If you need to change the default behaviour, configure understands the following options: @table @asis @item @kbd{--without-berkeley-db} DB is preferred before NDBM, but if you for some reason want to use NDBM instead, you can use this option. @item @kbd{--with-krb4=@file{dir}} Gives the location of Kerberos 4 libraries and headers. This enables Kerberos 4 support in the applications (telnet, rsh, popper, etc) and the KDC. It is automatically found if present under @file{/usr/athena}. If you keep libraries and headers in different places, you can instead give the path to each with the @kbd{--with-krb4-lib=@file{dir}}, and @kbd{--with-krb4-include=@file{dir}} options. You will need a fairly recent version of our Kerberos 4 distribution for @code{rshd} and @code{popper} to support version 4 clients. @item @kbd{--enable-dce} Enables support for getting DCE credentials and tokens. See the README files in @file{appl/dceutils} for more information. @item @kbd{--disable-otp} By default some of the application programs will build with support for one-time passwords (OTP). Use this option to disable that support. @item @kbd{--enable-osfc2} Enable some C2 support for OSF/Digital Unix/Tru64. Use this option if you are running your OSF operating system in C2 mode. @item @kbd{--with-readline=@file{dir}} Gives the path for the GNU Readline library, which will be used in some programs. If no readline library is found, the (simpler) editline library will be used instead. @item @kbd{--with-hesiod=@file{dir}} Enables hesiod support in push. @item @kbd{--enable-netinfo} Add support for using netinfo to lookup configuration information. Probably only useful (and working) on NextStep/Mac OS X. @item @kbd{--without-ipv6} Disable the IPv6 support. @item @kbd{--with-openldap} Compile Heimdal with support for storing the database in LDAP. Requires OpenLDAP @url{http://www.openldap.org}. See @url{http://www.padl.com/Research/Heimdal.html} for more information. @item @kbd{--enable-bigendian} @item @kbd{--enable-littleendian} Normally, the build process will figure out by itself if the machine is big or little endian. It might fail in some cases when cross-compiling. If it does fail to figure it out, use the relevant of these two options. @item @kbd{--with-mips-abi=@var{abi}} On Irix there are three different ABIs that can be used (@samp{32}, @samp{n32}, or @samp{64}). This option allows you to override the automatic selection. @item @kbd{--disable-mmap} Do not use the mmap system call. Normally, configure detects if there is a working mmap and it is only used if there is one. Only try this option if it fails to work anyhow. @end table