Package Dependencies Required to Build Samba: Difference between revisions

From SambaWiki
(Reformatted page. Rewrote os-indepentend section and introduction text)
Line 1: Line 1:
= OS independent =
= Operating System-independent Overview =


Depending on your distribution, the package name of the following libraries and programs may differ. Typically they are labled with lib*-dev or lib*-devel. See [[#Distribution_specific_package_installation|Distribution specific package installation]].
The following is an operating system-independent list of libraries and utilities required to build and install Samba. Depending on your distribution, the name of packages can differ. Usually library packages are named "lib*-devel" or "lib*-dev". For a list of distribution specific package installation commands, see [[#Distribution-specific_Package_Installation|Distribution-specific Package Installation]].


<u>Required:</u>


* python
:A good portion of Samba is written using python, including the build system itself (waf).


== Mandatory ==
* perl


{| class="wikitable"
<u>(Recommended) Optional:</u>
!Libraries and utilities
!Required for
|-
|python
|Several utilities, such as "samba-tool" and the build system ([[Waf|Waf]]), are written in Python.
|-
|perl
|
|-
|acl
|Required only on [[Active_Directory_Domain_Controller|Samba Active Directory domain controllers]] and member servers using [[Shares_with_Windows_ACLs|Windows ACLs]].
|-
|xattr
|Required only on [[Active_Directory_Domain_Controller|Samba Active Directory domain controllers]] and member servers using [[Shares_with_Windows_ACLs|Windows ACLs]].
|-
|python-crypto
|Samba AD DC only. Required by "samba-tool", for example, to establish trusts.
|}


* acl
:Required for a successfull Samba AD DC deployment! On Member Servers it is required to use the complete set of Windows ACLs.


* xattr
:Required for a successfull Samba AD DC deployment! On Member Servers it is required to use the complete set of Windows ACLs.


== Optional ==
* python-crypto
:Required by samba-tool, e. g. for creating trusts.


{| class="wikitable"
* blkid
!Libraries and utilities
!Required for
|-
|blkid
|
|-
|gnutls
|
|-
|readline
|
|-
|bsd or setproctitle
|Process title updating support.
|-
|xsltproc or docbook
|Man pages and other documentation.
|-
|pam-devel
|PAM support. For example, to [[Setup_Samba_as_an_AD_Domain_Member#Authenticating_Domain_Users_Using_PAM|authenticate domain users using PAM]].
|-
|cups
|[[Setup_a_Samba_print_server#CUPS|CUPS printer sharing support]].
|-
|openldap
|[[NT4_Domains|NT4_Domains]] support, including the [[Migrating_a_Samba_NT4_domain_to_a_Samba_AD_domain_(classic_upgrade)|Samba NT4 to AD migration (Classic Upgrade)]] migration
|}


* gnutls


* readline


* cups
:Required for CUPS printer sharing support.


* bsd or setproctitle
:Required for process title updating support.


= Distribution-specific Package Installation =
* xsltproc / docbook
:Required for building man pages and other documentation.


The following list of commands is neither provided no actively verified by the Samba team.
* pam-devel or libpam0g-dev
:Required to [[Setup_Samba_as_an_AD_Domain_Member#Authenticating_Domain_users_via_PAM|authenticate Domain users via PAM]]


If you see any missing packages or incorrect package names, please update the command or send the information to the [https://lists.samba.org/mailman/listinfo/samba Samba mailing list].
* openldap
:Required to build the Samba NT4-style PDC components with LDAP support and Active Directory Member Server support. Also required for the [[Migrating_a_Samba_NT4_domain_to_a_Samba_AD_domain_(classic_upgrade)|Samba classicupgrade]].






== Samba Active Directory Domain Controller ==


The following installation commands include the BIND DNS server. If you are using the Samba internal DNS server, omit the BIND package(s). However, you require the package containing the "nsupdate" utility to enable dynamic DNS support.

= Distribution specific package installation =

== For a Samba Active Directory Domain Controller ==

The following examples will cover all of the required libraries and programs. It will also cover BIND, kerberos and file system tools. If you plan to use the internal DNS server, you do not need BIND, but you do still need the package that contains the „nsupdate“ binary.




Line 65: Line 89:
xsltproc zlib1g-dev
xsltproc zlib1g-dev


Notes:
Notes:
libgnutls-dev has been replace by libgnutls28-dev on Debian 8 Jessie and Ubuntu >=14.04
* libgnutls-dev has been replace by libgnutls28-dev on Debian 8 Jessie and Ubuntu >=14.04
If you are building Samba on a system that uses systemd, you will also require the libsystemd-dev package
* If you are building Samba on a system that uses systemd, you will also require the libsystemd-dev package
If you are building Samba >= 4.5.0, you will also require libgpgme11-dev python-gpgme python-m2crypto
* If you are building Samba >= 4.5.0, you will also require libgpgme11-dev python-gpgme python-m2crypto





Line 180: Line 203:




== Samba Domain Member ==


== For a Samba Member Server ==


=== Red Hat Enterprise Linux / CentOS / Scientific Linux ===
=== Red Hat Enterprise Linux / CentOS / Scientific Linux ===
Line 192: Line 213:




== Samba NT4 PDC ==


No information provided yet.

== For a Samba NT4 PDC ==

Please add content or send the information to the [https://lists.samba.org/mailman/listinfo/samba Samba mailing list]

Revision as of 12:28, 3 October 2016

Operating System-independent Overview

The following is an operating system-independent list of libraries and utilities required to build and install Samba. Depending on your distribution, the name of packages can differ. Usually library packages are named "lib*-devel" or "lib*-dev". For a list of distribution specific package installation commands, see Distribution-specific Package Installation.


Mandatory

Libraries and utilities Required for
python Several utilities, such as "samba-tool" and the build system (Waf), are written in Python.
perl
acl Required only on Samba Active Directory domain controllers and member servers using Windows ACLs.
xattr Required only on Samba Active Directory domain controllers and member servers using Windows ACLs.
python-crypto Samba AD DC only. Required by "samba-tool", for example, to establish trusts.


Optional

Libraries and utilities Required for
blkid
gnutls
readline
bsd or setproctitle Process title updating support.
xsltproc or docbook Man pages and other documentation.
pam-devel PAM support. For example, to authenticate domain users using PAM.
cups CUPS printer sharing support.
openldap NT4_Domains support, including the Samba NT4 to AD migration (Classic Upgrade) migration



Distribution-specific Package Installation

The following list of commands is neither provided no actively verified by the Samba team.

If you see any missing packages or incorrect package names, please update the command or send the information to the Samba mailing list.


Samba Active Directory Domain Controller

The following installation commands include the BIND DNS server. If you are using the Samba internal DNS server, omit the BIND package(s). However, you require the package containing the "nsupdate" utility to enable dynamic DNS support.


Debian / Ubuntu

# apt-get install acl attr autoconf bison build-essential \
  debhelper dnsutils docbook-xml docbook-xsl flex gdb krb5-user \
  libacl1-dev libaio-dev libattr1-dev libblkid-dev libbsd-dev \
  libcap-dev libcups2-dev libgnutls-dev libjson-perl \
  libldap2-dev libncurses5-dev libpam0g-dev libparse-yapp-perl \
  libpopt-dev libreadline-dev perl perl-modules pkg-config \
  python-all-dev python-dev python-dnspython python-crypto \
  xsltproc zlib1g-dev

Notes:

  • libgnutls-dev has been replace by libgnutls28-dev on Debian 8 Jessie and Ubuntu >=14.04
  • If you are building Samba on a system that uses systemd, you will also require the libsystemd-dev package
  • If you are building Samba >= 4.5.0, you will also require libgpgme11-dev python-gpgme python-m2crypto


Fedora

# yum install libacl-devel libblkid-devel gnutls-devel \
   readline-devel python-devel gdb pkgconfig libattr-devel \
   krb5-workstation python-crypto docbook-style-xsl openldap-devel


Red Hat Enterprise Linux / CentOS / Scientific Linux

 # yum install perl gcc attr libacl-devel libblkid-devel \
    gnutls-devel readline-devel python-devel gdb pkgconfig \
    krb5-workstation zlib-devel setroubleshoot-server libaio-devel \
    setroubleshoot-plugins policycoreutils-python \
    libsemanage-python perl-ExtUtils-MakeMaker perl-Parse-Yapp \
    perl-Test-Base popt-devel libxml2-devel libattr-devel \
    keyutils-libs-devel cups-devel bind-utils libxslt \
    docbook-style-xsl openldap-devel autoconf python-crypto pam-devel


openSUSE

# zypper install libacl-devel python-selinux autoconf make \
    python-devel gdb sqlite3-devel libgnutls-devel binutils \
    policycoreutils-python setools-libs selinux-policy \
    setools-libs popt-devel libpcap-devel keyutils-devel \
    libidn-devel libxml2-devel libacl-devel libsepol-devel \
    libattr-devel zlib-devel cyrus-sasl-devel gcc \
    krb5-client openldap2-devel libopenssl-devel\
    bind-utils bind-lib


Gentoo

Please note that the following sections assume at least an intermediate understanding of the Gentoo packaging system.


Python

Gentoo uses Python 3 as the default python interpreter, but at this time Samba requires Python 2 (2.4.2 or later). The following set of commands will install and set up Python 2 as the default python interpreter.

# emerge --ask --noreplace '<dev-lang/python-3'
# eselect python set python2.7
# python-updater


Kerberos

On Gentoo, you have two choices for a kerberos implementation, app-crypt/mit-krb5 and app-crypt/heimdal. Unfortunately the two implementations can not be installed at the same time. Currently, the Samba only supports app-crypt/heimdal. So you must first uninstall app-crypt/mit-krb5, if installed. Then install app-crypt/heimdal and rebuild any packages that were using the previous kerberos implementation.

# emerge --unmerge --ask app-crypt/mit-krb5
# emerge --ask app-crypt/heimdal
# revdep-rebuild -- -ask


BIND

To enable automatic zone management, net-dns/bind and net-dns/bind-tools should be emerged with the USE flags for berkdb, dlz and gssapi set. To enable them permanently, add the following to /etc/package.use:

net-dns/bind berkdb dlz gssapi
net-dns/bind-tools gssapi

Then, emerge net-dns/bind:

# emerge --ask  net-dns/bind net-dns/bind-tools


Samba-supplied Libraries (tdb/ldb/tevent)

There are a few Samba libraries that need to be installed. Note that these packages might be keyworded as unstable, so you might need to add the following to your /etc/package.keywords:

~sys-libs/tevent-0.9.17
~sys-libs/tdb-1.2.10
~sys-libs/ldb-1.1.12
~sys-libs/talloc-2.0.7

Additionally, Samba requires sys-libs/tdb and sys-libs/talloc to be emerged with the USE flag python set. To enable this permanently, add the following to /etc/package.use:

sys-libs/tdb python
sys-libs/talloc python

Note: In new(er) installations of Gentoo, the above files will be located in /etc/portage/, i.e. /etc/portage/package.keywords and /etc/portage/package.use. They may be symlinked to /etc for backward compatibility.

Now, emerge the packages:

# emerge --ask '=sys-libs/talloc-2.0.7' '=sys-libs/tdb-1.2.10' '=sys-libs/tevent-0.9.17' '=sys-libs/ldb-1.1.12'

Note that ebuilds for the required versions of the above packages might not be availiable in the portage tree. In this case, check Gentoo's Bugzilla for updated ebuilds.


Other Misc. Build/Run Dependencies

To ensure a successful Samba 4 installation, there are a few other packages that should be installed, as shown below:

# emerge --ask net-libs/gnutls sys-apps/acl dev-libs/cyrus-sasl dev-python/subunit dev-python/dnspython net-dns/libidn 

FIXME: Are dev-python/dnspython net-dns/libidn still required?


Samba Domain Member

Red Hat Enterprise Linux / CentOS / Scientific Linux

# yum install autoconf automake gcc gdb krb5-devel krb5-workstation \
   openldap-devel make pam-devel python-devel docbook-style-xsl \
   libacl-devel libattr-devel libxslt 


Samba NT4 PDC

No information provided yet.