modules  5.0.0
About: The Environment Modules package provides for the dynamic modification of a user’s environment via modulefiles.
  Fossies Dox: modules-5.0.0.tar.bz2  ("unofficial" and yet experimental doxygen-generated source code documentation)  

modules Documentation

Some Fossies usage hints in advance:

  1. To see the Doxygen generated documentation please click on one of the items in the steelblue colored "quick index" bar above or use the side panel at the left which displays a hierarchical tree-like index structure and is adjustable in width.
  2. If you want to search for something by keyword rather than browse for it you can use the client side search facility (using Javascript and DHTML) that provides live searching, i.e. the search results are presented and adapted as you type in the Search input field at the top right.
  3. Doxygen doesn't incorporate all member files but just a definable subset (basically the main project source code files that are written in a supported language). So to search and browse all member files you may visit the Fossies modules-5.0.0.tar.bz2 contents page and use the Fossies standard member browsing features (also with source code highlighting and additionally with optional code folding).


Linux Build Status Windows Build Status FreeBSD/OS X/Linux Build Status Coverage Status Documentation Status Packaging status Twitter

Modules, provides dynamic modification of a user's environment

The Modules package is a tool that simplify shell initialization and lets users easily modify their environment during the session with modulefiles.

Each modulefile contains the information needed to configure the shell for an application. Once the Modules package is initialized, the environment can be modified on a per-module basis using the module command which interprets modulefiles. Typically modulefiles instruct the module command to alter or set shell environment variables such as PATH, MANPATH, etc. modulefiles may be shared by many users on a system and users may have their own collection to supplement or replace the shared modulefiles.

Modules can be loaded and unloaded dynamically and atomically, in an clean fashion. All popular shells are supported, including bash, ksh, zsh, sh, csh, tcsh, fish, as well as some scripting languages such as tcl, perl, python, ruby, cmake and r.

Modules are useful in managing different versions of applications. Modules can also be bundled into metamodules that will load an entire suite of different applications.

Quick examples

Here is an example of loading a module on a Linux machine under bash.

$ module load gcc/9.4.0
$ which gcc
$ /usr/local/gcc/9.4.0/linux-x86_64/bin/gcc

Now we'll switch to a different version of the module

$ module switch gcc gcc/10
$ which gcc

And now we'll unload the module altogether

$ module unload gcc
$ which gcc
gcc not found

Now we'll log into a different machine, using a different shell (tcsh).

% module load gcc/10.3
% which gcc

Note that the command line is exactly the same, but the path has automatically configured to the correct architecture.

Getting things running

The simplest way to build and install Modules on a Unix system is:

$ ./configure
$ make
$ make install

To learn the details on how to install modules see INSTALL.txt for Unix system or INSTALL-win.txt for Windows.


  • Tcl >= 8.5


Modules is distributed under the GNU General Public License, either version 2 or (at your option) any later version (GPL v2+). Read the file COPYING.GPLv2 for details.


See MIGRATING to get an overlook of the new functionalities introduced by each released versions. NEWS provides the full list of changes added in each version. The Changes document gives an in-depth view of the modified behaviors and new features between major versions. You may also look at the ChangeLog for the technical development details.

The doc directory contains both the paper and man pages describing the user's and the module writer's usage. To generate the documentation files, like the man pages (you need Sphinx >= 1.0 to build the documentation), just type:

$ ./configure
$ make -C doc all

The following man pages are provided:

module(1), ml(1), modulefile(4)

Test suite

Regression testing scripts are available in the testsuite directory (you need dejagnu to run the test suite):

$ ./configure
$ make test

Once modules is installed after running make install, you have the ability to test this installation with:

$ make testinstall

Web site:

Online documentation:

GitHub source respository:

GitHub Issue tracking system:

SourceForge project page:


Current core developer and maintainer is:

  • Xavier Delaruelle <xavier.delaruelle AT>

The following people have notably contributed to Modules and Modules would not be what it is without their contributions:

  • R.K. Owen
  • Kent Mein
  • Mark Lakata
  • Harlan Stenn
  • Leo Butler
  • Robert Minsk
  • Jens Hamisch
  • Peter W. Osel
  • John L. Furlani