Installing Linux Software From Source Code

  1. Why install from source?
    1. Availability: a package for your distribution may not be available
    2. Optimization: the software can be compiled to take best advantage of your hardware
    3. Features: extra features can be enabled during the build process
  2. Download the source code "tarball". These archive files usually end with .tar.gz or tar.bz2 suffixes.
    1. freshmeat.net
    2. sourceforge.net
  3. Unpack the source
    1. Using tar
      • for *.tar.gz files: tar xzvf
      • for *.tar.bz2 files: tar xjvf
    2. Using KDE: KDE's Ark utility is a graphical front-end for managing archives such as source tarballs
  4. Enter the source directory, using the cd command
  5. Read the Instructions: instructions are usually contained in the files named INSTALL and README inside the unpacked source directory
  6. Run ./configure
    1. ./configure --help to list the myriad available build options
    2. troubleshooting dependencies: the configure script will sometimes reveal the need for another piece of software, such as a library, which must be installed first
  7. Run make
  8. Run make install
    1. Superuser privegeles are required to install system-wide. Regular users can install programs to their own home directories
    2. uninstalling
      1. make uninstall: some source code comes with an uninstall target for the make command. This is often, but not always the case, and requires that you keep the source code, or at least the Makefile.
      2. manual removal: if the software doesn't have an uninstall target, then it must be removed manually. This method is prone to error, and can result in cruft being left behind.
  9. Build a package
    1. Easy updating and removal: By making your package management system aware of the software you install from source code, packages and source installs can be seamlessly integrated.
    2. Using checkinstall: checkinstall is a handy program that turns source code (or any other) installation into a package for your system. It knows how to make RPMs, debs, Slackpacks, and possibly other package types.