Ignore:
Timestamp:
Jun 16, 2009, 5:52:30 PM (16 years ago)
Author:
Herwig Bauernfeind
Message:

Update 3.2 to 3.2.12

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/samba-3.2.x/docs/htmldocs/Samba3-HOWTO/compiling.html

    r231 r272  
    1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 42. How to Compile Samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part VI. Reference Section"><link rel="prev" href="Appendix.html" title="Part VI. Reference Section"><link rel="next" href="Portability.html" title="Chapter 43. Portability"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 42. How to Compile Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Appendix.html">Prev</a> </td><th width="60%" align="center">Part VI. Reference Section</th><td width="20%" align="right"> <a accesskey="n" href="Portability.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="compiling"></a>Chapter 42. How to Compile Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate"> 22 May 2001 </p></div><div><p class="pubdate"> 18 March 2003 </p></div><div><p class="pubdate"> June 2005 </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="compiling.html#id2687532">Access Samba Source Code via Subversion</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2687538">Introduction</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2687580">Subversion Access to samba.org</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id2687771">Accessing the Samba Sources via rsync and ftp</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687846">Verifying Samba's PGP Signature</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687984">Building the Binaries</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688221">Compiling Samba with Active Directory Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#startingSamba">Starting the smbd nmbd and winbindd</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688492">Starting from inetd.conf</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2688712">Alternative: Starting smbd as a Daemon</a></span></dt></dl></dd></dl></div><p>
     1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 42. How to Compile Samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="Appendix.html" title="Part VI. Reference Section"><link rel="prev" href="Appendix.html" title="Part VI. Reference Section"><link rel="next" href="Portability.html" title="Chapter 43. Portability"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 42. How to Compile Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="Appendix.html">Prev</a> </td><th width="60%" align="center">Part VI. Reference Section</th><td width="20%" align="right"> <a accesskey="n" href="Portability.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="compiling"></a>Chapter 42. How to Compile Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</code></p></div></div></div></div><div><p class="pubdate"> 22 May 2001 </p></div><div><p class="pubdate"> 18 March 2003 </p></div><div><p class="pubdate"> June 2005 </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="compiling.html#id2687567">Access Samba Source Code via Subversion</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2687573">Introduction</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2687614">Subversion Access to samba.org</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#id2687805">Accessing the Samba Sources via rsync and ftp</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2687880">Verifying Samba's PGP Signature</a></span></dt><dt><span class="sect1"><a href="compiling.html#id2688018">Building the Binaries</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688255">Compiling Samba with Active Directory Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="compiling.html#startingSamba">Starting the smbd nmbd and winbindd</a></span></dt><dd><dl><dt><span class="sect2"><a href="compiling.html#id2688526">Starting from inetd.conf</a></span></dt><dt><span class="sect2"><a href="compiling.html#id2688746">Alternative: Starting smbd as a Daemon</a></span></dt></dl></dd></dl></div><p>
    22You can obtain the Samba source file from the
    33<a class="ulink" href="http://samba.org/" target="_top">Samba Web site</a>. To obtain a development version,
    44you can download Samba from Subversion or using <code class="literal">rsync</code>.
    5 </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687532"></a>Access Samba Source Code via Subversion</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2687538"></a>Introduction</h3></div></div></div><p>
    6 <a class="indexterm" name="id2687546"></a>
     5</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687567"></a>Access Samba Source Code via Subversion</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2687573"></a>Introduction</h3></div></div></div><p>
     6<a class="indexterm" name="id2687581"></a>
    77Samba is developed in an open environment. Developers use a
    88Subversion to &#8220;<span class="quote">checkin</span>&#8221; (also known as
     
    1313This chapter is a modified version of the instructions found at the
    1414<a class="ulink" href="http://samba.org/samba/subversion.html" target="_top">Samba</a> Web site.
    15 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2687580"></a>Subversion Access to samba.org</h3></div></div></div><p>
     15</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2687614"></a>Subversion Access to samba.org</h3></div></div></div><p>
    1616The machine samba.org runs a publicly accessible Subversion
    1717repository for access to the source code of several packages,
    1818including Samba, rsync, distcc, ccache, and jitterbug. There are two main ways
    1919of accessing the Subversion server on this host.
    20 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2687593"></a>Access via ViewCVS</h4></div></div></div><p>
    21 <a class="indexterm" name="id2687601"></a>
     20</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2687627"></a>Access via ViewCVS</h4></div></div></div><p>
     21<a class="indexterm" name="id2687635"></a>
    2222You can access the source code via your favorite WWW browser. This allows you to access
    2323the contents of individual files in the repository and also to look at the revision
     
    2727Use the URL
    2828<a class="ulink" href="http://viewcvs.samba.org/" target="_top">http://viewcvs.samba.org/</a>.
    29 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2687629"></a>Access via Subversion</h4></div></div></div><p>
    30 <a class="indexterm" name="id2687637"></a>
     29</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2687663"></a>Access via Subversion</h4></div></div></div><p>
     30<a class="indexterm" name="id2687671"></a>
    3131You can also access the source code via a normal Subversion client. This gives you much more control over what
    3232you can do with the repository and allows you to check out whole source trees and keep them up to date via
     
    3838</p><p>
    3939To gain access via anonymous Subversion, use the following steps.
    40 </p><div class="procedure"><a name="id2687670"></a><p class="title"><b>Procedure 42.1. Retrieving Samba using Subversion</b></p><ol type="1"><li><p>
     40</p><div class="procedure"><a name="id2687704"></a><p class="title"><b>Procedure 42.1. Retrieving Samba using Subversion</b></p><ol type="1"><li><p>
    4141        Install a recent copy of Subversion. All you really need is a
    4242        copy of the Subversion client binary.
     
    6363        <strong class="userinput"><code>svn update</code></strong>
    6464        </pre><p>
    65         </p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687771"></a>Accessing the Samba Sources via rsync and ftp</h2></div></div></div><p>
    66         <a class="indexterm" name="id2687779"></a>
    67         <a class="indexterm" name="id2687786"></a>
     65        </p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687805"></a>Accessing the Samba Sources via rsync and ftp</h2></div></div></div><p>
     66        <a class="indexterm" name="id2687814"></a>
     67        <a class="indexterm" name="id2687820"></a>
    6868        <em class="parameter"><code>pserver.samba.org</code></em> also exports unpacked copies of most parts of the Subversion tree
    6969        at the Samba <a class="ulink" href="ftp://pserver.samba.org/pub/unpacked" target="_top">pserver</a> location and also
     
    7575        merging of local changes as Subversion does. <code class="literal">rsync</code> access is most convenient
    7676        for an initial install.                     
    77         </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687846"></a>Verifying Samba's PGP Signature</h2></div></div></div><p>
    78 <a class="indexterm" name="id2687854"></a>
    79 <a class="indexterm" name="id2687860"></a>
     77        </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687880"></a>Verifying Samba's PGP Signature</h2></div></div></div><p>
     78<a class="indexterm" name="id2687888"></a>
     79<a class="indexterm" name="id2687894"></a>
    8080It is strongly recommended that you verify the PGP signature for any source file before
    8181installing it. Even if you're not downloading from a mirror site, verifying PGP signatures
     
    8888<code class="prompt">$ </code><strong class="userinput"><code>wget http://us1.samba.org/samba/ftp/samba-pubkey.asc</code></strong>
    8989</pre><p>
    90 <a class="indexterm" name="id2687908"></a>
     90<a class="indexterm" name="id2687943"></a>
    9191The first file is the PGP signature for the Samba source file; the other is the Samba public
    9292PGP key itself. Import the public PGP key with:
     
    106106gpg: BAD signature from &#8220;<span class="quote">Samba Distribution Verification Key</span>&#8221;
    107107</pre><p>
    108 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687984"></a>Building the Binaries</h2></div></div></div><p>
    109         <a class="indexterm" name="id2687992"></a>
    110 <a class="indexterm" name="id2687998"></a>
     108</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2688018"></a>Building the Binaries</h2></div></div></div><p>
     109        <a class="indexterm" name="id2688026"></a>
     110<a class="indexterm" name="id2688033"></a>
    111111        After the source tarball has been unpacked, the next step involves
    112112        configuration to match Samba to your operating system platform.
     
    121121</pre><p>
    122122        </p><p>
    123         <a class="indexterm" name="id2688040"></a>
     123        <a class="indexterm" name="id2688075"></a>
    124124        To build the binaries, run the program <strong class="userinput"><code>./configure
    125125        </code></strong> in the source directory. This should automatically
     
    136136</pre><p>
    137137        </p><p>
    138         <a class="indexterm" name="id2688106"></a>
     138        <a class="indexterm" name="id2688140"></a>
    139139        Execute the following create the binaries:
    140140</p><pre class="screen">
     
    165165        As you can see from this, building and installing Samba does not need to
    166166        result in disaster!
    167         </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688221"></a>Compiling Samba with Active Directory Support</h3></div></div></div><p>
     167        </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688255"></a>Compiling Samba with Active Directory Support</h3></div></div></div><p>
    168168        In order to compile Samba with ADS support, you need to have installed
    169169        on your system:
     
    188188        your LDAP libraries. Look in <code class="filename">config.log</code> to figure
    189189        out why and fix it.
    190         </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688287"></a>Installing the Required Packages for Debian</h4></div></div></div><p>On Debian, you need to install the following packages:</p><p>
     190        </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688321"></a>Installing the Required Packages for Debian</h4></div></div></div><p>On Debian, you need to install the following packages:</p><p>
    191191                </p><div class="itemizedlist"><ul type="disc"><li><p>libkrb5-dev</p></li><li><p>krb5-user</p></li></ul></div><p>
    192         </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688314"></a>Installing the Required Packages for Red Hat Linux</h4></div></div></div><p>On Red Hat Linux, this means you should have at least: </p><p>
     192        </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688348"></a>Installing the Required Packages for Red Hat Linux</h4></div></div></div><p>On Red Hat Linux, this means you should have at least: </p><p>
    193193                </p><div class="itemizedlist"><ul type="disc"><li><p>krb5-workstation (for kinit)</p></li><li><p>krb5-libs (for linking with)</p></li><li><p>krb5-devel (because you are compiling from source)</p></li></ul></div><p>
    194194        </p><p>in addition to the standard development environment.</p><p>If these files are not installed on your system, you should check the installation
    195195        CDs to find which has them and install the files using your tool of choice. If in doubt
    196         about what tool to use, refer to the Red Hat Linux documentation.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688358"></a>SuSE Linux Package Requirements</h4></div></div></div><p>
     196        about what tool to use, refer to the Red Hat Linux documentation.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688393"></a>SuSE Linux Package Requirements</h4></div></div></div><p>
    197197        SuSE Linux installs Heimdal packages that may be required to allow you to build
    198198        binary packages. You should verify that the development libraries have been installed on
     
    205205        packages where they are available.
    206206        </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="startingSamba"></a>Starting the <span class="application">smbd</span> <span class="application">nmbd</span> and <span class="application">winbindd</span></h2></div></div></div><p>
    207         <a class="indexterm" name="id2688412"></a>
     207        <a class="indexterm" name="id2688446"></a>
    208208        You must choose to start <span class="application">smbd</span>, <span class="application">winbindd</span>  and <span class="application">nmbd</span> either as daemons or from
    209209        <span class="application">inetd</span>. Don't try to do both!  Either you can put
     
    217217        The main advantage of starting <span class="application">smbd</span> and <span class="application">nmbd</span> using the recommended daemon method
    218218        is that they will respond slightly more quickly to an initial connection request.
    219         </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688492"></a>Starting from inetd.conf</h3></div></div></div><a class="indexterm" name="id2688498"></a><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The following will be different if
     219        </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688526"></a>Starting from inetd.conf</h3></div></div></div><a class="indexterm" name="id2688532"></a><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The following will be different if
    220220        you use NIS, NIS+, or LDAP to distribute services maps.</p></div><p>Look at your <code class="filename">/etc/services</code>.
    221221        What is defined at port 139/tcp? If nothing is defined,
     
    226226netbios-ns dgram udp wait root /usr/local/samba/sbin/nmbd nmbd
    227227</pre><p>
    228         </p><a class="indexterm" name="id2688560"></a><p>
     228        </p><a class="indexterm" name="id2688595"></a><p>
    229229        The exact syntax of <code class="filename">/etc/inetd.conf</code>
    230230        varies between UNIXes. Look at the other entries in inetd.conf
    231231        for a guide.
    232232        </p><p>
    233         <a class="indexterm" name="id2688580"></a>
     233        <a class="indexterm" name="id2688615"></a>
    234234        Some distributions use xinetd instead of inetd. Consult the
    235235        xinetd manual for configuration information.
     
    239239        <code class="filename">/etc/inetd.conf</code> to make them consistent.
    240240        </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    241         <a class="indexterm" name="id2688618"></a>
     241        <a class="indexterm" name="id2688652"></a>
    242242        On many systems you may need to use the
    243243        <a class="link" href="smb.conf.5.html#INTERFACES" target="_top">interfaces</a> option in <code class="filename">smb.conf</code> to specify
     
    254254        Restart <span class="application">inetd</span>, perhaps just send it a HUP,
    255255        like this:
    256 <a class="indexterm" name="id2688687"></a>
     256<a class="indexterm" name="id2688721"></a>
    257257</p><pre class="screen">
    258258<code class="prompt">root# </code><strong class="userinput"><code>killall -HUP inetd</code></strong>
    259259</pre><p>
    260         </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688712"></a>Alternative: Starting <span class="application">smbd</span> as a Daemon</h3></div></div></div><p>
    261         <a class="indexterm" name="id2688726"></a>
    262 <a class="indexterm" name="id2688733"></a>
     260        </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688746"></a>Alternative: Starting <span class="application">smbd</span> as a Daemon</h3></div></div></div><p>
     261        <a class="indexterm" name="id2688760"></a>
     262<a class="indexterm" name="id2688767"></a>
    263263        To start the server as a daemon, you should create a script something
    264264        like this one, perhaps calling it <code class="filename">startsmb</code>.
     
    279279        <code class="filename">examples/svr4-startup</code> script to make Samba fit
    280280        into that system.
    281         </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688811"></a>Starting Samba for Red Hat Linux</h4></div></div></div><p>
     281        </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688845"></a>Starting Samba for Red Hat Linux</h4></div></div></div><p>
    282282        Red Hat Linux has not always included all Samba components in the standard installation.
    283283        So versions of Red Hat Linux do not install the winbind utility, even though it is present
     
    312312</pre><p>
    313313        Samba will be started automatically at every system reboot.
    314         </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688933"></a>Starting Samba for Novell SUSE Linux</h4></div></div></div><p>
     314        </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688968"></a>Starting Samba for Novell SUSE Linux</h4></div></div></div><p>
    315315        Novell SUSE Linux products automatically install all essential Samba components in a default installation.
    316316        Configure your <code class="filename">smb.conf</code> file, then execute the following to start Samba:
Note: See TracChangeset for help on using the changeset viewer.