About NCSA    Projects    User Info    News     

University of Illinois
at Urbana-Champaign

FLAIM Logo
About
LAIM WG Home
License
Download
Installation
Documentation
Support

NSF
Logo
ONRLogo

Research is funded in part or whole by the National Science Foundation and the Office of Naval Research.


Valid HTML 4.01 Strict
Valid CSS!

Installing FLAIM

  1. Install any missing dependencies.

    FLAIM has been tested on Linux 2.6, Mac OS 10.4-5, FreeBSD 6.1, OpenBSD 3.9 and NetBSD 3.0.1. FLAIM has dependencies on the following libraries.

    • LIBXML:

      Libxml is an open source C library for parsing and validating XML files. It is available on most Linux and BSD systems. It can be downloaded from http://xmlsoft.org/. Note that you may need both the binary library as well as the development files to compile FLAIM. For binary packages, you do not need the developer's package.

    • LIBXSLT:

      Libxslt is a open source C library for parsing XSLT style-sheets. It is available on most Linux and BSD systems. It can be downloaded from http://xmlsoft.org/XSLT/. Note that you may need both the binary library as well as the development files to compile FLAIM. For binary packages, you do not need the developer's package.

    • OPENSSL:

      Openssl is a open source C library for creating encrypted SSL tunnels which also provides many cryptographic functions. It is available on almost all Linux and BSD systems. It can be downloaded from http://www.openssl.org/. Note that you may need both the binary library as well as the development files to compile FLAIM. For binary packages, you do not need the developer's package.

  2. Download FLAIM-Core and at least one I/O module.

    You can find FLAIM and its supported modules on the Download page. Download FLAIM-Core and the modules corresponding to the types of logs you would like to process.

  3. Install FLAIM-Core

    You must unpack the tarball, run the config script, and make the package. An example follows.

    [yoursystem]:$ tar zxf flaim-core-<version>.tgz
    [yoursystem]:$ cd flaim-core-<version>
    [yoursystem]:$ ./configure
    .... lots of output here ......
    [yoursystem]:$ make
    [yoursystem]:$ make install

  4. Install a FLAIM Module

    You must unpack the tarball, run the config script, and make the package. An example follows.

    [yoursystem]:$ tar zxf flaim-module-<modulename>-<version>.tgz
    [yoursystem]:$ cd flaim-module-<modulename>-<version>
    [yoursystem]:$ ./configure
    .... lots of output here ......
    [yoursystem]:$ make
    [yoursystem]:$ make install

Important Note on RPMs and Debian packages

We compile binaries on Debian 4.0 (Etch) and use the alien package to generate RPMs and Debian packages from binary tarballs. As a consequence, you may have an issue using an RPM on a very old or very new Linux distribution because of differences in the major versions of critical libraries. For example, Fedora Core 6 (but not Core 4) uses libstdc++ version 6 as opposed to version 5 in Debian Sarge, and hence it would not (at one time) install our RPM because of a dependency issue. In this case, and similar situations, one can simply download the source and compile FLAIM just fine.

Installing in Non-Standard Locations

The default installation behavior is to create /usr/local/flaim and place all the libraries and configuration files there. In addition, a symbolic link is made to /usr/bin/flaim. One must normally be root to install in these directories, or to install the man page.

To install FLAIM in a different location, one can pass an option to the configure script. The option to set is prefix. The default value for this variable is /usr/local. FLAIM then installs to $(prefix)/flaim, i.e. /usr/local/flaim. Say, instead, a user wants to install FLAIM into /usr/flaim. He would then pass the option to the configure script as follows:

[yoursystem]:$ ./configure --prefix=/usr

If the installation directory is changed for FLAIM-Core, it must be changed in the same way when modules are installed. Again, this can be done with the same options for their configure scripts.


©2005–2008 Board of Trustees of the University of Illinois.