Specifying the Location of Compiler Components with compilervars

Linux* and OS X*:

Set the environment variables before using the compiler by sourcing the shell script compilervars.sh or compilervars.csh. Depending on the shell you use, you can use either the source command or a . (dot) to source the shell script, according to the following rules:

• .csh script: Use the source command.

• .sh script:

  • Bash: Use either the source command or . (dot space).

  • Dash or other POSIX-compliant shell: Use . (dot space).

//# Bash shell: 
source /<install-dir>/bin/compilervars.sh <arg> 
. /<install-dir>/bin/compilervars.sh <arg>

//# examples: (assuming <install-dir> is /installed/compiler/)
prompt> source /installed/compiler/bin/compilervars.sh ia32
prompt> . /installed/compiler/bin/compilervars.sh ia32

// OR

//# C shell: 
source /<install-dir>/bin/compilervars.csh <arg> 

//# example: (assuming <install-dir> is /installed/compiler/)
prompt> source /installed/compiler/bin/compilervars.csh ia32

// OR

//# Dash or other POSIX-compliant shell: 
. /<install-dir>/bin/compilervars.sh <arg> 

//# example: (assuming <install-dir> is /installed/compiler/)
prompt> . /installed/compiler/bin/compilervars.sh ia32

The environment script file requires a target architecture argument <arg>:

• ia32: Compiler and libraries for IA-32 architecture-based targets only.
• intel64: Compiler and libraries for Intel® 64 architecture-based targets only.

The default install path is /opt/intel/bin/<version>/ if the installation was conducted by the root user, where <version> is the version of the compiler you wish to set the environment for.

If you want the script to run automatically, add the same command to the end of your startup file.

Sample .bash_profile entry for compilervars.sh for IA-32 architecture targets only:

# set environment vars for Intel®  Fortran  Compiler 
source <install-dir>/bin/compilervars.sh ia32

If the proper environment variables are not set, an error similar to the following will appear when attempting to execute a compiled program:

./a.out: error while loading shared libraries: 
libimf.so: cannot open shared object file: No such file or directory

Windows*:

Under normal circumstances, you do not need to run the compilervars.bat batch file. The Intel® Fortran command-line window sets these variables for you automatically.

For information on using the command-line window see Using the Intel® Command-Line Window.

The batch file inserts the directories used by the Intel® Fortran Compiler at the beginning of the existing paths. Because these directories appear first, they are searched before any directories in the path lists provided by Windows*. This is especially important if the existing path includes directories with files having the same names as those needed by the Intel® Fortran Compiler.

If needed, you can run compilervars.bat each time you begin a session on Windows* systems by specifying it as the initialization file with the PIF Editor.

The batch file takes two arguments:

 <install-dir>\bin\compilervars.bat <arg1> [<arg2>]

where <arg1> is one of the following:

 <install-dir>\bin\compilervars.bat <arg1> [<arg2>]

• intel64: Compiler and libraries for Intel® 64 architecture only (host and target)

• ia32: Compiler and libraries for IA-32 architecture only (host and target)

• ia32_intel64: Compiler running on IA-32 architecture (host) that generates code for Intel® 64 architecture (target) using Intel® 64 architecture libraries

<arg2>, is optional. If specified, is one of the following:

• vs2015: Microsoft Visual Studio* 2015

• vs2013: Microsoft Visual Studio* 2013

• vs2012: Microsoft Visual Studio* 2012

• vs2013shell: Microsoft Visual Studio* Shell 2013