Modulefile Conflicts

Some modulefiles should not be loaded while certain other modulefiles are currently loaded. This is especially true of modulefiles for different versions of the same software. For example, the Intel C/C++ Version 8.0 compiler modulefile should not be loaded while the Intel C/C++ Version 8.1 compiler modulefile is loaded. A modulefile conflict occurs in this situation.

The system displays an error message when you attempt to load a modulefile that conflicts with one or more currently loaded modulefiles. For example:

$ module load ifort/8.0
ifort/8.0(19):ERROR:150: Module 'ifort/8.0' conflicts with the 
currently loaded module(s) 'ifort/8.1'

ifort/8.0(19):ERROR:102: Tcl command execution failed:
conflict ifort/8.1

In this example, a user attempted to load the ifort/8.0 modulefile. After the user issued the command to load the modulefile, an error message occurred, indicating a conflict between this modulefile and the ifort/8.1 modulefile, which is already loaded.

When a modulefile conflict occurs, unload the conflicting modulefile before loading the new modulefile. In the previous example, you should unload the ifort/8.0 modulefile before loading the ifort/8.1 modulefile. For information about unloading a modulefile, see Unloading a Modulefile.

	Note: To avoid problems, HP recommends that you always unload one version of a modulefile before loading another version.