Troubleshooting
Problem
How do I setup environment using module file for intel C/C++ compilers?
Resolving The Problem
How do I setup environment using module file for intel C/C++ compilers?
Please find attached module file for the intel C/C++ compilers, version 9.1.
Below is the procedure proposed to use :
1- Create the module :
sudo cp ompi112-i2 icc-9.1
sudo vim icc-9.1
sudo vim icc-9.1
2- Publish the module (frontend):
sudo mkdir /opt/modules/modulefiles/intel
sudo ln -s /share/apps/modulefiles.custom/icc-9.1 /opt/modules/modulefiles/intel/icc-9.1
sudo ln -s /share/apps/modulefiles.custom/icc-9.1 /opt/modules/modulefiles/intel/icc-9.1
3- Test the module file :
Please find below the procedure I used in order to test this module file :
3.1- Check the availability of this new module :
--------------------------------------------------------------
[toor3@frontend modulefiles.custom]$ module avail intel
---------------------------------------------------------------- /opt/modules//modulefiles ----------------------------------------------------------------
intel/icc-9.1
intel/icc-9.1
--------------------------------------------------------------
3.2- Load the module and check the output :
--------------------------------------------------------------
[toor3@frontend modulefiles.custom]$ module load intel/icc-9.1
intel C/C++ compilers ver. 9.1 build 047 module
****************************************************
****************************************************
This module sets up the following environment
variables for intel C/C++ compilers ver. 9.1, build 047
assumption : INTEL_LICENSE_FILE env. is already setup
PATH
LD_LIBRARY_PATH
MANPATH
variables for intel C/C++ compilers ver. 9.1, build 047
assumption : INTEL_LICENSE_FILE env. is already setup
PATH
LD_LIBRARY_PATH
MANPATH
Version 3.1.6
****************************************************
--------------------------------------------------------------
3.3- Check the environment :
3.3.1- PATH :
--------------------------------------------
[toor3@frontend ~]$ echo $PATH
/share/apps/intel/cce/9.1.047/bin:.:/share/apps/openmpi-1.1.2-ifort2/bin:/opt/intel/fce/9.0/bin:/opt/lava/6.1/linux2.6-glibc2.3-ia32e/bin:/opt/lava/6.1/linux2.6-glibc2.3-ia32e/etc:/usr/kerberos/bin:/opt/intel/itc60/bin:/opt/intel/ita60/bin:/opt/intel/fce/9.0/bin:/opt/intel/idbe/9.0/bin:/opt/intel/cce/9.0/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/opt/modules/current/bin/:/opt/modules/bin/:/opt/ganglia/bin:/opt/lam/gnu/bin:/opt/rocks/bin:/opt/rocks/sbin:/home/toor3/bin
/share/apps/intel/cce/9.1.047/bin:.:/share/apps/openmpi-1.1.2-ifort2/bin:/opt/intel/fce/9.0/bin:/opt/lava/6.1/linux2.6-glibc2.3-ia32e/bin:/opt/lava/6.1/linux2.6-glibc2.3-ia32e/etc:/usr/kerberos/bin:/opt/intel/itc60/bin:/opt/intel/ita60/bin:/opt/intel/fce/9.0/bin:/opt/intel/idbe/9.0/bin:/opt/intel/cce/9.0/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/opt/modules/current/bin/:/opt/modules/bin/:/opt/ganglia/bin:/opt/lam/gnu/bin:/opt/rocks/bin:/opt/rocks/sbin:/home/toor3/bin
--------------------------------------------
Please note that if you load only this module file, you will get the 9.0 version for the fortran compiler. This is because the environment setup for this version is done through /etc/profile.d
3.3.2- LD_LIBRARY_PATH :
--------------------------------------------
[toor3@frontend ~]$ echo $LD_LIBRARY_PATH
/share/apps/intel/cce/9.1.047/lib:/share/apps/openmpi-1.1.2-ifort2/lib:/opt/intel/fce/9.0/lib:/opt/intel/cce/9.0/lib:/opt/intel/cmkl/8.0/lib/em64t:/opt/lava/6.1/linux2.6-glibc2.3-ia32e/lib:/opt/intel/itc60/slib:/opt/intel/ipp41/em64t/sharedlib:/opt/intel/fce/9.0/lib:/opt/intel/cce/9.0/lib
[toor3@frontend ~]$ echo $LD_LIBRARY_PATH
/share/apps/intel/cce/9.1.047/lib:/share/apps/openmpi-1.1.2-ifort2/lib:/opt/intel/fce/9.0/lib:/opt/intel/cce/9.0/lib:/opt/intel/cmkl/8.0/lib/em64t:/opt/lava/6.1/linux2.6-glibc2.3-ia32e/lib:/opt/intel/itc60/slib:/opt/intel/ipp41/em64t/sharedlib:/opt/intel/fce/9.0/lib:/opt/intel/cce/9.0/lib
--------------------------------------------
3.3.3- MANPATH
--------------------------------------------
[toor3@frontend ~]$ echo $MANPATH
/share/apps/intel/cce/9.1.047/man:/share/apps/openmpi-1.1.2-ifort2/man:/opt/intel/fce/9.0/man:/opt/intel/cce/9.0/man:/opt/lava/6.1/man:/opt/intel/itc60/man:/opt/intel/fce/9.0/man:/opt/intel/idbe/9.0/man:/opt/intel/cce/9.0/man:/opt/modules/current/man:/opt/modules/man:/usr/local/share/man:/usr/share/man:/usr/X11R6/man:/opt/rocks/man:/opt/mpich/gnu/man:/opt/lam/gnu/man:/opt/ganglia/man:/opt/lava/6.1/man
[toor3@frontend ~]$ echo $MANPATH
/share/apps/intel/cce/9.1.047/man:/share/apps/openmpi-1.1.2-ifort2/man:/opt/intel/fce/9.0/man:/opt/intel/cce/9.0/man:/opt/lava/6.1/man:/opt/intel/itc60/man:/opt/intel/fce/9.0/man:/opt/intel/idbe/9.0/man:/opt/intel/cce/9.0/man:/opt/modules/current/man:/opt/modules/man:/usr/local/share/man:/usr/share/man:/usr/X11R6/man:/opt/rocks/man:/opt/mpich/gnu/man:/opt/lam/gnu/man:/opt/ganglia/man:/opt/lava/6.1/man
--------------------------------------------
3.4- Check the compilers versions :
--------------------------------------------
[toor3@frontend ~]$ icc -V
Intel(R) C Compiler for Intel(R) EM64T-based applications, Version 9.1 Build 20070215 Package ID: l_cc_c_9.1.047
Copyright (C) 1985-2007 Intel Corporation. All rights reserved.
Intel(R) C Compiler for Intel(R) EM64T-based applications, Version 9.1 Build 20070215 Package ID: l_cc_c_9.1.047
Copyright (C) 1985-2007 Intel Corporation. All rights reserved.
[toor3@frontend ~]$ icpc -V
Intel(R) C++ Compiler for Intel(R) EM64T-based applications, Version 9.1 Build 20070215 Package ID: l_cc_c_9.1.047
Copyright (C) 1985-2007 Intel Corporation. All rights reserved.
4- Propagation (compute nodes) :
4.1- Create the appropriate directory on the compute nodes :
sudo cluster-fork "mkdir /opt/modules/modulefiles/intel"
4.2- Propagate the module using symbolic link :
sudo cluster-fork "ln -s /share/apps/modulefiles.custom/icc-9.1 /opt/modules/modulefiles/intel/icc-9.1"
Please note that (as usual) this is a "non-persistent" operation.
So if you want to reimage a node or if a node crashes and then get reinstalled, this symlink will be lost.
You can either disable the automatic reinstall after crash or do a persistent modification (using rocks-compute for example to modify the default image that will be installed on the nodes).
[{"Product":{"code":"SSZUCA","label":"IBM Spectrum Cluster Foundation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.1.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Product":{"code":"SSZUCA","label":"IBM Spectrum Cluster Foundation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":null,"Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
18 September 2018
UID
isg3T1014315