|Help for Alpine - Compiling|
|You are in Home > Compiling|
Building Alpine is not difficult. There are several advantages about building Aline that you can not get if you only get a precompiled version. For example, you can fix a bug as soon as a patch is available. The price that you must pay in order to receive the advantages of compiling your own source code is usually minimal and we will try to explain how to build Alpine from scratch.
The source code of Alpine is available only for recent versions. The source code of Alpine is not available for versions 2.00 or earlier, as the University of Washington closed its ftp server.
Version 2.01 of Alpine was never officially released by the University of Washington, but its source code is available in this site at http://alpine.x10host.com/alpine/patches/alpine-2.01/alpine-2.01.clean.tar.lzma.
Versions beyond 2.01 can be obtained from http://alpine.x10host.com/alpine/release/
You can also download the most recent bits in the development of Alpine from its git repository at http://repo.or.cz/alpine.git.
A few other software is included when you build Alpine from source code. Here is a list:
./configure ; make
There are many configuration options that can be passed to the configure script or the make command to build Alpine. A list of all configuration options can be obtained with the command
we will look at the most popular options you might want to configure separately in this document.
In order to build successfully Alpine besides a compiler and autotools, which normally are minimum requirements for building any software, you will need the PAM library to build c-client. OpenSSL is not required, but without it Alpine will not be able to connect securely to a server, which may have serious security implications for you. Current versions of Alpine require that you use a version above 1.0.0c of OpenSSL. Alpine also compiles with LibreSSL.
If you want to connect to a LDAP server, you need to have the ldap library installed in your system. Alpine will build without LDAP support. In order to write to the screen Alpine needs the ncurses library. This is necessary so that Alpine can write in bold, or reverse. The ncurses library is not and optional requirement.
Building Alpine with kerberos support is also optional. In order to build WebAlpine you need to install TCL.
On the other hand, debug parameters such as what is the debug default level of recording by Alpine, the number of files that are kept for recording debug and the default name for this file. The parameters that control these values are --with-debug-level=VALUE, --with-debug-files=VALUE and --with-debug-file=VALUE.
A password file allows users to save their passwords in a file, so that they do not have to enter them every time that they connect to their e-mail server.
You can only enable password file support when you build Alpine. This is not binding, in the sense that even if you enable it you must still create the password file in order to be able to use it. To define a password file add the option
--with-passfile=FILENAMEwhere FILENAME can be anything, such as, ".pine-passfile".
Alpine encrypts slightly its password file, using a weak encryption based on character substitution. A stronger encryption is possible in Alpine-2.10 using S/MIME. In order to use the stronger encryption one must configure a password file as above and later configure S/MIME on a personal basis. The private certificate of the user is used to encrypt the password file. If the password file needs a password to be unlocked, then Alpine will request the password to unlock the file before decrypting it and reading the passwords from it.
Alpine tries to find the location of OpenSSL or LibreSSL in your system, based on the default location of these libraries in your system. If for any reason these files are not installed in their default locations, you can specify them during compilation. Here are the options.
|You are in Home > Compiling|