LCLint Home Page

LCLint Home


Windows 95/NT


User's Guide
       HTML Online

Other Sources

Mailing Lists


Source Code Installation

LCLint should compile effortlessly on standard Unix systems, and with a bit of effort on non-Unix platforms. If you produce a port for a non-Unix platform, please let me know.

To build LCLint you need:

  • a (hopefully ANSI-conforming) C compiler. GNU gcc is recommended, but most modern C compilers should work.
  • make, the GNU make utility. If you don't have make installed on your system, download it from
  • standard Unix tools: gzip, tar


  1. Enter your email address here to be added to the lclint-announce mailing list. This is optional, but highly recommended. The list is only used to announce new lclint releases.
  2. Download

    Copy this package to the directory where you want to build LCLint. When the tar file is extracted, it will create an lclint-2.4b subdirectory.

  3. Uncompress the package: gzip -d lclint-2.4b.src.tar.gz

  4. Extract files from the tar archive: tar xf lclint-2.4b.src.tar

  5. Run: configure
    This will create a Makefile with settings for your system. If you want to install LCLint or associated libraries different directories, edit the Makefile.

  6. Run: gmake
    It is best to do this in an emacs shell or a buffered terminal, so you can scroll through the output.
  7. Set environment variables:
    LARCH_PATH - path to search for lclint libraries and initializations files. If you are using the standard directories, this should be ".:base-directory/lclint-2.4b/lib".

    LCLIMPORTDIR - directory containing lcl imports files. If you are using the standard directories, this is base-directory/lclint-2.4b/imports.

    Put the commands to set these variables (the actual commands will depend on the shell you are using) in one of your initialization dotfiles (usually ~/.environment).

    Set up your PATH to include the directory containing lclint-2.4b/bin/lclint, or move the binary to a directory on your command path.

  8. Run: gmake test
    Examine the test output. If there are errors, send a bug report to

David Evans
Software Devices and Systems