Setting up your environment for the Intel C++ compiler

The Intel C++ Compiler is installed on ariadne, and accessible from all other workstations via /usr/local. Before you can use this compiler, you must adjust your environment. This step, which has to be done only once, is outlined below for bash and (t)csh users.
On the clusters (elektra and hera), this has been added to the global profile. Thus, bash users do not have to do anything on these machines.

• bash: add the following line at the end of your ~/.bashrc file (don't forget the leading period):
  . /usr/local/intel/cc/9.1/bin/iccvars.sh
• (t)csh: add the following line at the end of your ~/.cshrc file:
  source /usr/local/intel/cc/9.1/bin/iccvars.csh

Now, open a new shell and try the command "icc -V". This command should be recognized and report version "9.1".
If you still wish to use the old (version 8.1) compilers, then use the following line in your ~/.bashrc file instead:
. /usr/local/intel/cc_80/bin/iccvars.sh

The command "icid" (from earlier versions of the Intel Compiler) is no longer available. If you're using (t)csh and you get a complaint saying that no license file can be found, please add the following line to your ~/.cshrc file:
setenv INTEL_FLEXLM_LICENSE /usr/local/intel/licenses

Setting up your environment for the Intel Fortran compiler

If you also wish to use the Intel Fortran compiler, you need to make an additional modification to your environment. Again, no action is needed on the clusters (elektra and hera). On the local machines, add this line to your ~/.bashrc file (don't forget the leading period):
. /usr/local/intel/fc/9.1/bin/ifortvars.sh
(For the version 8.1. compiler, use instead: . /usr/local/intel/fc_80/bin/ifortvars.sh)

Note that the name of the compiler has changed: as of version 8.0 you invoke it as "ifort" rather than "ifc". In a new shell, test your setup via "ifort -V".

Intel Math Kernel Libraries (MKL)

• Add the following line to your ~/.bashrc file (don't forget the leading period):
  . /usr/local/intel/mkl/set_path.sh

  For some cryptic reason, this is enough to execute a program compiled with MKL. However, it is not sufficient for the actual compilation of such a program! For the latter, see the next step:

• Compilation with MKL LAPACK routines:
  On Athlon machines, do:
  icc myprogram.c -L/usr/local/intel/mkl/lib/32 -lmkl_lapack -lmkl_p3 -lguide -lF90
  On Pentium 4 machines (elektra), do:
  icc myprogram.c -L/usr/local/intel/mkl/lib/32 -lmkl_lapack -lmkl_p4 -lguide -lF90