From: Michael Meffie Date: Mon, 12 Nov 2007 17:37:33 +0000 (+0000) Subject: none X-Git-Url: http://git.openafs.org/?p=openafs-wiki.git;a=commitdiff_plain;h=d0e4969b45d178e76f0ee6aa19cd13afadae6a8d;hp=a201bd7c7031f002492413c971e41309f482ddec none --- diff --git a/AFSLore/HowToBuildOpenAFSFromSource.mdwn b/AFSLore/HowToBuildOpenAFSFromSource.mdwn index 9ae4857..d4a8ebf 100644 --- a/AFSLore/HowToBuildOpenAFSFromSource.mdwn +++ b/AFSLore/HowToBuildOpenAFSFromSource.mdwn @@ -19,6 +19,8 @@ Libraries - ncurses - kernel headers +The Kerberos development libraries are required if you are going to build with Kerberos 5 support. The [[OpenAFS]] legacy kaserver is deprecated. + If you are building on Debian, you can get the required software with the following apt-get commands. apt-get install cvs autoconf automake make gcc flex bison @@ -26,7 +28,7 @@ If you are building on Debian, you can get the required software with the follow ### Getting the Source Code from CVS -You can get development snapshots from the [[OpenAFS]] CVS repository. The CVS tree may not always have code which can currently be built. While every effort is made to keep the head of the tree buildable, you may at any time find yourself between commits and hence have a tree which does not build, or worse, causes more serious problems. +You can get development snapshots from the [[OpenAFS]] CVS repository . The CVS tree may not always have code which can currently be built. While every effort is made to keep the head of the tree buildable, you may at any time find yourself between commits and hence have a tree which does not build, or worse, causes more serious problems. First you need to run cvs login. This step is normally only done once. A ~/.cvspass file will be created for additional checkouts. @@ -47,21 +49,21 @@ CVS snapshots do not include files generated by autoconf; You can run regen.sh a ### Building the Binaries -#### Quick Answer +#### Transarc Paths + +By convention, [[OpenAFS]] server binaries and related files are located in /usr/afs, and client binaries and related files are located in /usr/vice. These are known as Transarc paths, so called because that is is the convention used by Transarc, the company that first commercized AFS. -To build [[OpenAFS]] with Kerberos 5 support and the traditional paths: +To build [[OpenAFS]] with Kerberos 5 support and the traditional, Transarc paths: cd openafs ./regen.sh - ./configure --enable-debug --enable-transarc-paths --with-krb5-conf=(full path to krb5-config script) + ./configure --enable-transarc-paths --with-krb5-conf=(full path to krb5-config script) make make dest -You will need the Kerberos development libraries to build Kerbose support. - -### Installing the Binaries +If all goes well, then the binaries are located in a platform sub-directory, the name of which is platform specific, for example 'i386\_linux26/dest'. -After make dest, the binaries are placed into a dest directory, under a platform directory, such as i386\_linux26. +The 'make install' command does not work with Transarc paths. You will have to manually copy the binaries into place after running make dest. For more information, see the Quick Start Guide for Unix on the [[OpenAFS]] documentation page. # cp -r i386_linux26/dest/root.client/usr/vice/etc/modload /usr/vice/etc # cp i386_linux26/dest/root.client/usr/vice/etc/afsd /usr/vice/etc @@ -71,6 +73,16 @@ After make dest, the binaries are placed into a dest directory, under a platform # cp -r i386_linux26/dest/lib /usr/afsws # cp -r i386_linux26/dest/root.server/usr/afs/* /usr/afs +#### Custom Paths + +To build [[OpenAFS]] with Kerberos 5 support, and with a custom install path, + + cd openafs + ./regen.sh + ./configure --prefix=/usr/local/openafs --with-krb5-conf=(full path to krb5-config script) + make + sudo make install + ### Initial testing -- [[MichaelMeffie]] - 09 Oct 2007