dante   Frontpage - Dante - Download - Status - Support - Modules - Docs - Links - Survey
 

Compilation and Installation

This document covers compilation and installation of Dante, starting with the Dante source code.

This document covers the basic steps needed to compile and install Dante. Depending on the operating system, dependencies and Dante modules to be included in the build, there might be additional steps needed, such as Kerberos installation, which is not covered in this document.

Dante server compilation

  1. Unless you have been provided with a private source code archive by Inferno Nettverk A/S, first download the source code from the Dante download page.

  2. To compile Dante, a compiler and basic header files must be installed. On some platforms these are parts of the base system, on others they must be installed (e.g., the gcc and glibc-headers packages).

    Some of the functionality in Dante also requires additional packages.

    E.g., for RedHat, the following packages may have to be installed if you want to use the Dante LDAP module:

    • PAM: pam-devel
    • GSSAPI: krb5-devel
    • LDAP module: openldap-devel cyrus-sasl-devel
  3. Extract the Dante source code (replace x below with the latest version minor number):

          $ tar zxvf dante-1.3.x.tar.gz
        
  4. Enter the source code directory:

          $ cd dante-1.3.x
        
  5. If also installing a Dante module, extract the module files in the source code directory:

          $ tar zxvf <module archive>.tar.gz
        

    Then apply any patches:

          $ for file in patches/*.patch; do patch -p1 < $file; done
        
  6. To build the default configuration, run configure without any arguments:
          $ ./configure
        

    This will configure the build for installation under /usr/local. To change the installation prefix, use the --prefix option to specify a different directory prefix.

    For a full overview of the options available, use the --help configure option.

  7. If configure runs successfully, it will print a status summary before exiting. If functionality with external dependencies is required, verify that these have been detected correctly before starting compilation.

    External dependencies that have been detected are marked as "Enabled", while not correctly detected dependencies and functionality is marked as "Not found/disabled".

    It is not a problem if dependencies for functionality that is not needed are not found; it will only mean that Dante will be built with code for these parts disabled.

    The status output might look like the following:

                         Configure status:
    
    Preloading:        Enabled
    GSSAPI:            Enabled
    KRB5:              Enabled
    LDAP:              Enabled
    SASL:              Enabled
    UPNP:              Not found/disabled
    
                         Modules:
    
    redirect:          Not found
    bandwidth:         Not found
    session:           Not found
    ldap:              Not found
    

    If all required dependencies are found, continue with the next step to compile Dante. If dependencies are missing, consult the more detailed output from configure that precedes the status summary, or if that fails, the config.log file generated by configure. This will hopefully provide some information as to why the dependencies were not found.

  8. To build and install Dante, run these commands:
          $ make
          # make install
         

    This will by default result in Dante being installed under /usr/local, with the server binary being located in /usr/local/sbin/sockd.

    To verify that the compiled binary starts, run it with the -v option:

          $ /usr/local/sbin/sockd -v
    

    This should cause Dante to print the version number and exit, for example:

    sockd: dante v1.3.2
    
  9. The next step is to configure the server. For details, consult the server configuration page.

Copyright © 1998-2017 Inferno Nettverk A/S