Intel® System Studio 2015 Beta for Linux Hosts Silent Installation Guide

Intel® System Studio 2015 Beta for Linux Hosts "Silent" or non-interactive Installation Instructions


Linux and Mac OS X Compilers Installation Help Center: /en-us/articles/intel-compilers-linux-installation-help

Contents of this document:


Silent Command Line Installations

The Linux installation programs for Intel® System Studio 2015 Beta for Linux* Host are built using the PSET (Program Startup Experience Technologies) 2.0 core.  This PSET core is a framework of tools built by Intel to provide a robust set of installation and licensing features that are consistent across Intel product lines.  A similar PSET core is used for the Windows* and Mac OS* X installation packages as well.

One feature provided in the PSET core is support for the "silent" install.  Historically, "silent" really meant "non-interactive".  At this point, "silent" also means "does not report copious amounts of information", assuming there are no problems during the installation.  The silent install method allows the user to perform a command line installation of an entire package with no need to answer prompts or make product selections.

Silent Install Steps: "From Scratch"

To run the silent install, follow these steps:

  • For reasons outlined below we recommend that a working product license or server license is in place before beginning.  The file should be world-readable and located in a standard Intel license file directory, such as the default linux license directory /opt/intel/licenses.  For more details, keep reading.
  • Create or edit an existing silent install configuration file.  This file controls the behavior of the installation.  Here is an example file.  A similar file can be edited and placed in any directory on the target system.  After this example we explain the configuration file contents.
# silent.cfg 
# Patterns used to check silent configuration file
# anythingpat - any string
# filepat     - the file location pattern (/file/location/to/license.lic)
# lspat       - the license server address pattern (0123@hostname)
# snpat      - the serial number pattern (ABCD-01234567)

# accept EULA, valid values are: {accept, decline}

# install mode for RPM system, valid values are: {RPM, NONRPM}

# optional error behavior, valid values are: {yes, no}

# install location, valid values are: {/opt/intel, filepat}

# continue with overwrite of existing installation directory, valid values are: {yes, no}

# list of components to install, valid values are: {ALL, DEFAULTS, anythingpat}

# installation mode, valid values are: {install, modify, repair, uninstall}

# this one is optional
# directory for non-RPM database, valid values are: {filepat}

# Choose 1 of the 2 activation options - either serial or license
# license is needed if system does not have internet connectivity to Intel
# Serial number, valid values are: {snpat}
# License file or license server, valid values are: {lspat, filepat}
# and based on the above, set the activation type: again, recommend using a license_file.
# exist_lic will look in the normal places for an existing license.
# Activation type, valid values are: {exist_lic, license_server, license_file, trial_lic, serial_number}

# Sampling driver installation type, valid values are: {build, kit}

# Power driver installation type, valid values are: {build, kit}

# Driver access group, valid values are: {anythingpat, vtune}

# Driver access permissions, valid values are: {anythingpat, 666}

# Load driver(s) into the kernel during installation, valid values are: {yes, no}

# Path to C compiler, valid values are: {filepat, auto, none}

# Path to kernel source directory, valid values are: {filepat, auto, none}

# Path to make command, valid values are: {filepat, auto, none}

# Install boot script to automatically reload the driver(s) on system restart, valid values are: {yes, no}

# Enable per-user collection mode for Sampling driver, valid values are: {yes, no}

# Intel(R) Software Improvement Program opt-in, valid values are: {yes, no}

# Perform validation of digital signatures of RPM files, valid values are: {yes, no}

Running the Silent Installation

Once you have created your silent installation configuration file, installation is quite simple.  First, extract the compiler full package tar file in a temporary directory.  For purposes of this example we use /tmp as our temporary directory.  You may use any directory in which you have full file permissions.  Do not untar the package in the directory where you intend to install the compiler, the temporary directory should be disjoint from your final target installation directory.

Untar the compiler package (assumes the package is copied to /tmp).  Your compiler version and package name may differ than that shown below:

  1. cd /tmp
  2. tar -zxvf  l_cembd_b_2015.0.020.tgz 

Now cd to the extracted directory

  1. cd l_cembd_b_2015.0.020

Run  the installer program, passing the full path to your configuration file with the --silent option

  1. ./ --silent /tmp/silent.cfg

where "silent.cfg" is replaced by the name you used to create your silent configuration file.   You may use any name for this file.

DONE.  If your configuration file is accepted the installer will now progress with the installation without further input from you, and no output will appear unless there is an error.


A few comments on the directives inside the silent install configuration file:


  • This directive tells the install program that the invoking user has agreed to the End User License Agreement or EULA.  This is a mandatory option and MUST be set to 'accept'. If this is not present in the configuration file, the installation will not complete.  By using the silent installation program you are accepting the EULA.
  • The EULA is in a plain text file in the same directory as the installer.  It has file name "license".  Read this before proceeding as using the silent installer means you have read and agree to the EULA.  If you have questions, see our Get Help page for your support options.


  • This directive tells the install program that the RPM method should be used to install the software.  This will only work if the install user is "root" or has full root priveleges and your distribution support RPM for package management.  In some cases, where the operating system of the target system does not support RPM or if the install program detects that the version of RPM supported by the operating system is flawed or otherwise incompatible with the install program, the installation will proceed but will switch to non-RPM mode automatically.  This is the case for certain legacy operating systems (e.g. SLES9) and for operating systems that provide an RPM utility, but do not use RPM to store or manage system-installed operating system infrastructure (e.g. Ubuntu, Debian).  THUS, Ubuntu and Debian users set this to INSTALL_MODE=NONRPM.

  • If the you do not want to use RPM, then this line should read "INSTALL_MODE=NONRPM".  In this case, the products will be installed to the same location, but instead of storing product information in the system's RPM database, the Intel product install information will be stored in a flat file called "intel_sdp_products.db", usually stored in /opt/intel (or in $HOME/intel for non-root users).  To override this default, use configuration file directive NONRPM_DB_DIR


  • If INSTALL_MODE=NONRPM the directive NONRPM_DB_DIR can be used to override the default directory for the installation database.  The default is /opt/intel or in $HOME/intel for non-root users.  The format for this directive is:
  • NONRPM_DB_DIR=/path/to/your/db/directory


  • This directive tells the install program to look for an existing license during the install process.  This is the preferred method for silent installs.  Take the time to register your serial number and get a license file (see below).  Having a license file on the system simplifies the process.  In addition, as an administrator it is good practice to know WHERE your licenses are saved on your system.  License files are plain text files with a .lic extension.  By default these are saved in /opt/intel/licenses which is searched by default.  If you save your license elsewhere, perhaps under an NFS folder, set environment variable INTEL_LICENSE_FILE to the full path to your license file prior to starting the installation or use the configuration file directive ACTIVATION_LICENSE_FILE to specify the full pathname to the license file.
  • Options for ACTIVATION are { exist_lic, license_file, server_lic, serial_number, trial_lic }
    • exist_lic directs the installer to search for a valid license on the server.  Searches will utilize the environment variable INTEL_LICENSE_FILE, search the default license directory /opt/intel/licenses, or use the ACTIVATION_LICENSE_FILE directive to find a valid license file.
    • license_file is similar to exist_lic but directs the installer to use ACTIVATION_LICENSE_FILE to find the license file.
    • server_lic is similar to exist_lic and exist_lic but directs the installer that this is a client installation and a floating license server will be contacted to active the product.  This option will contact your floating license server on your network to retrieve the license information.  BEFORE using this option make sure your client is correctly set up for your network including all networking, routing, name service, and firewall configuration.  Insure that your client has direct access to your floating license server and that firewalls are set up to allow TCP/IP access for the 2 license server ports.  server_lic will use INTEL_LICENSE_FILE containing a port@host format OR a client license file.  The formats for these are described here
    • serial_number directs the installer to use directive ACTIVATION_SERIAL_NUMBER for activation.  This method will require the installer to contact an external Intel activation server over the Internet to confirm your serial number.  Due to user and company firewalls, this method is more complex and hence error prone of the available activation methods.  We highly recommend using a license file or license server for activation instead.
    • trial_lic is used only if you do not have an existing license and intend to temporarily evaluate the compiler.  This method creates a temporary trial license in Trusted Storage on your system.
  • No license file but you have a serial number?  If you have only a serial number, please visit to register your serial number.  As part of registration, you will receive email with an attached license file.  If your serial is already registered and you need to retrieve a license file, read this:
  • Save the license file in /opt/intel/licenses/ directory, or in your preferred directory and set INTEL_LICENSE_FILE environment variable to this non-default location.  If you have already registered your serial number but have lost the license file, revisit and click on the hyperlinked product name to get to a screen where you can cut and paste or mail yourself a copy of your registered license file.
  • Still confused about licensing?  Go to our licensing FAQS page


  • This directive instructs the installer where to find your named-user or client license.  The format is:
  • ACTIVATION_LICENSE_FILE=/use/a/path/to/your/licensefile.lic  where licensefile.lic is the name of your license file.


  • This directive controls behavior when the compiler encounters an "optional" error.  These errors are non-fatal errors and will not prevent the installation to proceed if the user has set CONTINUE_WITH_OPTIONAL_ERROR=yes.  Examples of optional errors include an unrecognized or unsupported linux distribution or version or certain prerequisites for a product cannot be found at the time of installation (such as a supported Java runtime or missing 32bit development libraries for 32bit tool installation).   Fatal errors found during installation will cause the installer to abort with appropriate messages printed.
  • CONTINUE_WITH_OPTIONAL_ERROR=yes directs the installer to ignore non-fatal installation issues and continue with the installation.
  • CONTINUE_WITH_OPTIONAL_ERROR=no directs the installer to abort with appropriate warning messages for the non-fatal error found during the installation.


  • This directive specifies the target directory for the installation.  The Intel Compilers default to /opt/intel for installation target.  Set this directive to the root directory for the final compiler installation.


  • Determines the behavior of the installer if the PSET_INSTALL_DIR already contains a existing installation of this specific compiler version. The Intel compiler allows co-existence of multiple versions on a system.  This directive does not affect this behavior, each version of the compiler will have a unique installation structure that does not overwrite other versions.  This directive dictates behavior when the SAME VERSION is already installed in the PSET_INSTALL_DIR.
  • CONTINUE_WITH_INSTALLDIR_OVERWRITE=yes directs the installer to overwrite the existing compiler version of the SAME VERSION
  • CONTINUE_WITH_INSTALLDIR_OVERWRITE=no directs the installer to exit if an existing compiler installation of the SAME VERSION already exists in PSET_INSTALL_DIR


  • A typical compiler package contains multiple sub-packages, such as MKL, IPP, TBB, Debugger, etc.  This directive allows the user to control which sub-packages to install.
  • COMPONENTS=DEFAULTS directs the installer to install the pre-determined default packages for the compiler (recommended setting).  The defaults may not include some sub-packages deemed non-essential or special purpose.  An example is the cluster components of MKL, which are only needed in a distributed memory installation.  If you're not sure of the defaults you can do a trial installation of the compiler in interactive mode and select CUSTOMIZE installation to see and select components.
  • COMPONENTS=ALL directs the installer to install all packages for the compiler.
  • COMPONENTS=<pattern> allows the user to specify which components to install.  The components vary by compiler version and package.  The components should be enclosed in double-quotes and semi-colon separated.  For a list of component, grep for the <Abbr> tags in <installation directory>/uninstall/mediaconfig.xml, such as this :
    • cd <compiler root>/uninstall
    • grep Abbr mediaconfig.xml
    • note that the list may have close to or over 100 components.


  • Sets the installer mode.  The installer can install, remove, modify, or repair an installation.
  • PSET_MODE=install directs the installer to perform an installation
  • PSET_MODE=remove directs the installer to remove a previous installation.  If multiple versions of the compiler are installed, the installer removes the most recent installation.  This information is kept in the RPM database or the non-rpm database depending on the mode used for the installation.
  • PSET_MODE=modify allows the user to redo an installation.  The most common scenario is to overwrite an existing installation with more COMPONENTS set or unset.
  • PSET_MODE=repair directs the installer to retry an installation again, checking for missing or damaged files, directories, and symbolic links, permissions, etc.


  • This directive guides the installer in the user's intent for the optional Intel Software Improvement Program.  This setting determines whether or not the compiler periodically sends customer usage information back to Intel.  The intent is for Intel to gather information on what compiler options are being used, amongst other information.  More information on the Intel Software Improvement Program can be found here:
  • PHONEHOME_SEND_USAGE_DATA=no directs the installer to configure the compiler to not send usage data back to the Intel Software Improvement Program.
  • PHONEHOME_SEND_USAGE_DATA=yes directs the installer to configure the compiler to send usage data back to the Intel Software Improvement Program.  Setting this to YES is your consent to opt-into this program.


  • Sampling driver installation type, valid values are: {build, kit}

  • VTune sampling driver installation control - either install a pre-built kernel module from the package or build the driver on your system. You can use the 'kit' driver if you have a support Linux distribution and version.  See the VTune installation and user guide for details. In order to 'build' you will need to have kernel sources installed on your system.  


  • Power driver installation type, valid values are: {build, kit}

  • VTune driver or kernel module for power sampling.  'kit' means there is a pre-built driver for your OS in the package. You can use the 'kit' driver if you have a support Linux distribution and version.  See the VTune installation and user guide for details. In order to 'build' you will need to have kernel sources installed on your system.  You can use the 'kit' driver if you have a support Linux distribution and version.  See the VTune installation and user guide for details.


  • Driver access group, valid values are: {anythingpat, vtune}

  • The GROUP (GID) to use for the installation.  Allows group access to the VTune drivers.  Typically we recommend setting up a group named 'vtune' with access to those allowed access to the VTune sampling drivers.


  • Driver access permissions, valid values are linux file permissions setting: {anythingpat, 666}


  • Load driver(s) into the kernel during installation, valid values are: {yes, no}


  • Path to C compiler, valid values are: {filepat, auto, none}

  • To use another compiler, give the full path and compiler name such as 'gcc', 'icc', or other.  Default is gcc


  • Used only if you build the VTune drivers from sources.  This gives the path to the kernel sources.
  • Path to kernel source directory, valid values are: {filepat, auto, none}


  • Used only if you build the VTune drivers from sources.  This gives the path to the system 'make' command
  • valid values are: {filepat, auto, none}


  • controls whether a boot script is installed on the system to automatically load the sampling drivers on system boot.
  • valid values are: {yes, no}


  • Enable per-user collection mode for Sampling driver, valid values are: {yes, no}


  • Directs the installer whether or not to check RPM digital signatures.  Checking signatures is recommended.  It allows the installer to find data corruption from such things as incomplete downloads of compiler packages or damaged RPMs.
  • SIGNING_ENABLED=yes directs the installer to check RPM digital signatures.
  • SIGNING_ENABLED=no directs the installer to skip the checking of RPM digital signatures.


Silent Install Steps: "Copy and Repeat" Method for Silent Configuration File Creation

If you need to make the same sort of installation over and over again, one way to get the silent installation configuration file right the first time is to run the installation program once interactively, using the options that meet the local needs, and record these options into a configuration file that can be used to replicate this same install via silent install for future installations.

To do this, the user simply needs to add the "duplicate" option to the script invocation, and run a normal interactive install, as follows:

  • prompt> ./ --duplicate /tmp/silent.cfg

This "dash dash duplicate" option will put the choices made by you into the file specified on the command line.  You can modify this recorded configuration file as appropriate and use it to perform future silent installations. 

RPM Command Line Installations

The files associated the Linux Compiler Professional products are stored in "RPM" files.  RPMs (short for Red Hat Package Manager).  They are grouped according to certain file type guidelines.  Each major product component will consist of one more or of these RPMs.  For non-RPM systems and for users who choose to install the product without using the RPM database of their target systems, an "underneath the hood" utility is embedded inside the installation program tools to extract the contents of the RPM files.

RPM Embedded Installation Functionality

The Linux System Studio 2015 packaging includes RPM files that also contain embedded installation functionality.  This means that key install behaviors such as environment script updating and symbolic link creation, which used to be only in the install program itself, are now embedded in the RPM files.  As a result, the experienced user can make use of the RPM files directly in order to install and remove Intel System Studio 2015 for Linux hosts products.

Warning: this is truly for the experienced, Linux system savvy user.  Most RPM command capabilities require root privileges.  Improper use of rpm commands can corrupt and destroy a working system.


The changes done for the Linux compiler products are intended to ease the job of deploying in enterprise deployments, including cluster environments. 

Product Layout for Intel® System Studio 2015

Here is an example for <tmpdir>/l_cembd_b_2015.0.020/  which is the beta version "_b_" 2015 package update 0, build 020

Top directory contents of a typical package:

  • - CD eject script used by
  • - install script
  • - GUI front-end to the installer using X11. Only used for interactive, graphical installation method.
  • license.txt - end user license agreement
  • support.txt - package version and contents information
  • pset - installation and licensing content directory used by the Intel installers
  • rpm - directory containing all product content in RPM file format, plus the EULA and LPGL license
  • silent.cfg - a sample silent configuration file.  You can use this as a template.

This is an example ISS 2015 Beta rpm directory.  This directory listing is for the Update 0 build 020 ISS 2015 Beta release, your version strings will vary by compiler versions:   NOTE:  this is not intended to be a comprehensive list for every compiler.  RPMs vary by compiler edition, components, and may vary by release.  Please list your 'rpm' directory for a list specific to your compiler.  The following is intended as a representative list:

intel-cembd-common-2015b-020.noarch.rpm                    intel-cembd-mkl-32b-020-11.2-2.noarch.rpm
intel-cembd-common-pset-2015b-020.noarch.rpm               intel-cembd-mkl-64b-020-11.2-2.noarch.rpm
intel-cembd-compilerpro-android-32b-020-15.0-0.noarch.rpm  intel-cembd-mkl-common-020-11.2-2.noarch.rpm
intel-cembd-compilerproc-32b-020-15.0-0.noarch.rpm         intel-cembd-mkl-devel-32b-020-11.2-2.noarch.rpm
intel-cembd-compilerproc-64b-020-15.0-0.noarch.rpm         intel-cembd-mkl-devel-64b-020-11.2-2.noarch.rpm
intel-cembd-compilerproc-common-020-15.0-0.noarch.rpm      intel-cembd-mkl-gnu-32b-020-11.2-2.noarch.rpm
intel-cembd-compilerproc-devel-32b-020-15.0-0.noarch.rpm   intel-cembd-mkl-gnu-64b-020-11.2-2.noarch.rpm
intel-cembd-compilerproc-devel-64b-020-15.0-0.noarch.rpm   intel-cembd-mkl-gnu-devel-32b-020-11.2-2.noarch.rpm
intel-cembd-compilerpro-common-020-15.0-0.noarch.rpm       intel-cembd-mkl-gnu-devel-64b-020-11.2-2.noarch.rpm
intel-cembd-compilerpro-devel-32b-020-15.0-0.noarch.rpm    intel-cembd-mkl-sp2dp-64b-020-11.2-2.noarch.rpm
intel-cembd-compilerpro-devel-64b-020-15.0-0.noarch.rpm    intel-cembd-mkl-sp2dp-devel-64b-020-11.2-2.noarch.rpm
intel-cembd-compilerpro-gfx-64b-020-15.0-0.noarch.rpm      intel-cembd-ocd-020-0.8.0-0.i486.rpm
intel-cembd-compilerpro-vars-020-15.0-0.noarch.rpm         intel-cembd-ocd-020-0.8.0-0.x86_64.rpm
intel-cembd-gdb-common-020-7.7-0.noarch.rpm                intel-cembd-ocd-src-020-0.8.0-0.noarch.rpm
intel-cembd-gdb-core-020-7.7-0.i486.rpm                    intel-cembd-openmp-32b-020-15.0-0.noarch.rpm
intel-cembd-gdb-core-020-7.7-0.x86_64.rpm                  intel-cembd-openmp-64b-020-15.0-0.noarch.rpm
intel-cembd-gdb-python-src-020-7.7-0.noarch.rpm            intel-cembd-openmp-devel-32b-020-15.0-0.noarch.rpm
intel-cembd-gdb-server-32b-020-7.7-0.noarch.rpm            intel-cembd-openmp-devel-64b-020-15.0-0.noarch.rpm
intel-cembd-gdb-server-64b-020-7.7-0.noarch.rpm            intel-cembd-sven-sdk-020-1.0-0.noarch.rpm
intel-cembd-gdb-src-020-7.7-0.noarch.rpm                   intel-cembd-sven-viewer-020-1.0-0.noarch.rpm
intel-cembd-gdb-target-galileo-020-7.7-0.noarch.rpm        intel-cembd-target-2015b-020.noarch.rpm
intel-cembd-ipp-common-020-8.2-0.noarch.rpm                intel-cembd-xdb-020-2015-0.i486.rpm
intel-cembd-ipp-common-devel-32b-020-8.2-0.noarch.rpm      intel-cembd-xdb-020-2015-0.x86_64.rpm
intel-cembd-ipp-common-devel-64b-020-8.2-0.noarch.rpm      intel-cembd-xdb-common-020-2015-0.noarch.rpm
intel-cembd-ipp-mt-devel-32b-020-8.2-0.noarch.rpm          intel-cembd-xdb-dal-020-2015-0.x86_64.rpm
intel-cembd-ipp-mt-devel-64b-020-8.2-0.noarch.rpm          intel-cembd-xdb-eclipse-020-2015-0.i486.rpm
intel-cembd-ipp-st-ac-32b-020-8.2-0.noarch.rpm             intel-cembd-xdb-eclipse-020-2015-0.x86_64.rpm
intel-cembd-ipp-st-ac-64b-020-8.2-0.noarch.rpm             intel-cembd-xdb-kernel-020-2015-0.i486.rpm
intel-cembd-ipp-st-devel-32b-020-8.2-0.noarch.rpm          intel-cembd-xdb-kernel-020-2015-0.x86_64.rpm
intel-cembd-ipp-st-devel-64b-020-8.2-0.noarch.rpm          intel-gpa-14.2.225646-1.i386.rpm
intel-cembd-ipp-st-di-32b-020-8.2-0.noarch.rpm             intel-gpa-14.2.225646-1.x86_64.rpm
intel-cembd-ipp-st-di-64b-020-8.2-0.noarch.rpm             intel-inspector-sys-2015-cli-362926-15.0-2.i486.rpm
intel-cembd-ipp-st-gen-32b-020-8.2-0.noarch.rpm            intel-inspector-sys-2015-cli-362926-15.0-2.x86_64.rpm
intel-cembd-ipp-st-gen-64b-020-8.2-0.noarch.rpm            intel-inspector-sys-2015-cli-common-362926-15.0-2.noarch.rpm
intel-cembd-ipp-st-jp-32b-020-8.2-0.noarch.rpm             intel-inspector-sys-2015-cli-pset-362926-15.0-2.noarch.rpm
intel-cembd-ipp-st-jp-64b-020-8.2-0.noarch.rpm             intel-inspector-sys-2015-doc-362926-15.0-2.noarch.rpm
intel-cembd-ipp-st-mx-32b-020-8.2-0.noarch.rpm             intel-inspector-sys-2015-gui-362926-15.0-2.i486.rpm
intel-cembd-ipp-st-mx-64b-020-8.2-0.noarch.rpm             intel-inspector-sys-2015-gui-362926-15.0-2.x86_64.rpm
intel-cembd-ipp-st-rr-32b-020-8.2-0.noarch.rpm             intel-inspector-sys-2015-gui-common-362926-15.0-2.noarch.rpm
intel-cembd-ipp-st-rr-64b-020-8.2-0.noarch.rpm             intel-vtune-amplifier-sys-2015-common-pset-362999-15.0-0.noarch.rpm
intel-cembd-ipp-st-sc-32b-020-8.2-0.noarch.rpm             intel-vtune-amplifier-sys-2015-gui-362999-15.0-0.i486.rpm
intel-cembd-ipp-st-sc-64b-020-8.2-0.noarch.rpm             intel-vtune-amplifier-sys-2015-gui-362999-15.0-0.x86_64.rpm
intel-cembd-ipp-st-vc-32b-020-8.2-0.noarch.rpm             intel-vtune-amplifier-sys-2015-gui-common-362999-15.0-0.noarch.rpm

Installing Compilers With the RPM Command Line

To install a Linux compiler solution set via RPM command line, you should first ensure that a working license file or other licensing method (such as floating or network-served licenses) is already in place.  There is no license checking performed during RPM installation.  However, if you install without a license file you will get an 'cannot check out license' error when you try to use the compiler.

You are assumed to have complied with the End User License Agreement (EULA) if you are performing an RPM command line installation.  The EULA is present in the parent installation directory ( license or license.txt file).  Please read this license agreement.  It is assumed you agree to this license agreement if you proceed with an rpm installation.

Once a license file or license method is in place, the user can install the products directly with these simple steps:

  • Login as root or 'su' to root
  • ISS 2015:  'cd' to the package/rpm directory ( e.g. /tmp/l_cembd_b_2015.0.020/rpm )
  • Run the RPM install command
    • rpm -i *.rpm

This completes without error in most cases.  If some system-level prerequisites, for required system libraries for example, are not met by the target operating system, a dependency warning may be returned by the rpm install.  There are no embedded detailed dependency checks inside the RPM install capabilities for required commands such as g++ or for optional requirements such as a valid supported operating system or supported JRE.  The embedded requirements are kept simple to ease installation for the general case, with an  exception.  The exception is the requirement for a /usr/lib/ library to exist on the target system, and must match in 64bit or 32bit (there will be 2 copies of this library, one 64bit and one 32bit in 2 separate /lib paths, if you wish to be able to compile in 64bits and 32bits). 

The second requirement is that the target operating system have at least the 3.0 version of "lsb" component installed.  Availability of this LSB component will, in the vast majority of cases, also ensure that other necessary system level libraries are available.  See LSB Support below for more information on getting the 'lsb' capability onto a target system.

If you believe that you have effectively installed the correct requirements on the target system and the dependency failures still persist, there is a fallback option, the "--nodeps" (dash dash nodeps) rpm switch.  Invoking 'rpm -i' with the --nodeps option will allow the rpm installation to succeed in most cases.

  • prompt>  rpm -i --nodeps *.rpm

Again, this will get you past the perceived dependency issues, which may be unique to a particular distribution of Linux and not really a problem for the resulting installation.  But there is no assurance of complete success other than testing the resulting installation.

Other Special RPM Install Cases

If you are installing RPMs using the rpm command line, but using a multi-architecture package (such as the "combo" IA-32 / Intel64 package or a DVD package), you may want to install all of the RPMs that match their specific target machine's architecture.  Or, if you are installing onto an Intel64 system and want to include both the IA-32 and Intel64 components, you may want both of these included.  Here are some example rpm command line invocations:

  • prompt>  rpm  -i  *.noarch.rpm  *.486.rpm
    • ​installs all components needed for operation on IA-32 architecture
  • prompt>  rpm  -i  *.noarch.rpm  *.i486.rpm   *.x86_64.rpm
    • installs all components needed for operation on both IA-32 and Intel 64 architecture

Certain Linux distributions do not like the idea of two RPM files having the same base name.  For example, the rpm versions of certain distros might complain that there is more than one instance of  intel-cproc023-11.1-1 on the command line when installing both the IA-32 and Intel64 RPMs onto the same machine.  For these distros, use the "--force" ( dash dash force ) command line switch:

  • prompt>  rpm  -i  --force  *.noarch.rpm  *.i486.rpm  *.x86_64.rpm

Customizing the RPM Command Line

The rpm command has a long list of available options, including hooks to install from FTP and HTTP RPM repositories, features to examine contents of installed RPM-based programs and uninstalled RPM package files, etc.  Most of these are beyond the scope of this document.  See the Links section for references to external documentation on RPM.  Here are a couple of additional RPM switches, however, which may be routinely useful.

  • prompt>  rpm  -i  --prefix  /my_NFS_dir/intel_compiler_directory/this_version  *.rpm
    • ​instructs rpm to use directory /my_NFS_dir/intel_compiler_directory/this_version as the root installation directory
  • ​prompt>  rpm  -i --replacefiles  *.rpm
    • ​directs rpm to replace any existing files using the new rpm files
  • ​prompt>  rpm  -i --replacepkgs  *.rpm 
    • directs ​rpm to replace any existing package on the system using the new RPM files, even if they are already installed ... this may be useful in test applications where newer versions of a package with the same name are being tested

Uninstallation Using RPM

Since the installation of Intel Linux compiler packages includes in its deliver all of the uninstall scripts, the easiest way to perform a product uninstall is to simply run the uninstall script that is created by the install process.  If you have a need to automate rpm-based uninstalls, however, a couple of "tricks" can be employed to make this simpler.  These should be used with caution, as with any system command performed from a privileged account.

Here is an example command line that will remove all RPM packages from a Linux hosted ISS 2015 package number "020":

  • rpm  -e  --allmatches `rpm -qa | grep intel- | grep 020`
    • ​note use of back-quotes
    • note that this only removes compiler packages.  You may wish to use a similar method to remove intel-mkl, intel-ipp, intel-gdb, intel-openmp and other intel packages

Some Linux distributions will also complain about "multiple matches" during the uninstall process.  In this case, the "--allmatches" switch mentioned above can also be employed here.

A Short Word on Updates

The rpm structure and command set support the application of updates or "patches" to existing installations.  For example a util-1.1-2.rpm package may be issued that adds fixed content to some pre-existing util-1.1-1.rpm.   The existing release process for Linux hosted ISS 2015 includes support for "version co-existence" or multiple installs of separate product versions.  So each new iteration of the product is unique from the previous version.  This means that Intel compiler packages are not available in "patch" form.  All product releases are stand-alone versions.  So use of the 'rpm -U' upgrade capability is not supported by our product delivery model at this time. 


LSB Support

LSB, or Linux Standard Base, is an effort sponsored by the Linux Foundation ( to improve the interoperability of Linux operating systems and application software.  Intel is a major participant in Linux Foundation activities and has embraced LSB as a viable means of improving our products and our customers' use of those products.  To that end, we have included establishing LSB compliance as a part of our goals for our products and software packages in the future.

For the purposes of the Intel System Studio 2015 for Linux Hosts our primary objective is to product packages that adhere to LSB packaging requirements.  Most of the RPM changes mentioned above were done for this purpose.  To be specific, however, we should draw a distinction between product compliance and package compliance.  Because our compiler products must support a vast array of legacy constructs, the applications themselves may or may not be "certifiable" within the LSB guidelines, but our packages, i.e. our RPMs and install programs should be.  This is the primary reason for inclusion of the "lsb >= 3.0" embedded requirements being added to our RPMs.

Some of these Linux distributions come with LSB support already included in the operating system by default (e.g. SLES11).  For others, an external or optional package must be installed.  If supporting an environment that is using RPM command line installation and want to enable that site / system / systems to be able to install without using the dreaded "--nodeps" option, the best best is to acquire and install the companion LSB solution for that operating system.

The Linux Foundation website contains links to download resources for LSB, as to many of the vendor-specific support sites.  Check out these sites for information on adding LSB support to an existing operating system.

For RPM-based systems, a user can check on the status of LSB for their system, using a command like this:

  • prompt>  rpm -q --provides lsb

This will tell if an 'lsb' RPM package is already installed and, if so, what version.

For our non-RPM supported operating systems, Ubuntu and Debian, the privileged user can use the Debian 'apt-get' facility to easily install the latest version of LSB supported by the specific distribution:

  • prompt> apt-get install lsb

Uninstall Instructions

As mentioned above, a standard uninstall script is included with each product installation, regardless of whether the install was performed using menu installs, RPM command line installs, or "silent" installs.  In all cases, using the provided uninstall script should work and is the usual preferred method of removing installed product..  There is one uninstall feature, however, that is undocumented and can be used to make life a little easier.  Here's an example invocation of that feature:

  • prompt>  /opt/intel/composer_xe_2015.<update>.<build>/bin/  --default

This "--default" ( dash dash default ) option tells the uninstall script to use the "remove all" option and remove any compiler components associated with the specific package (in this case all  components, including C/C++, Fortran, IDB, MKL, TBB, and IPP, if installed).  There is no uninstall program interaction when this switch is used.

Uninstallation Using RPM

Since the installation of Intel Linux compiler packages includes in its deliver all of the uninstall scripts, the easiest way to perform a product uninstall is to simply run the uninstall script that is created by the install process.  If you have a need to automate rpm-based uninstalls, however, a couple of "tricks" can be employed to make this simpler.  These should be used with caution, as with any system command performed from a privileged account.

Here is an example command line that will remove all RPM packages from a Linux hosted ISS 2015 package number "020":

  • rpm  -e  --allmatches `rpm -qa | grep intel- | grep 020`
    • ​note use of back-quotes
    • note that this only removes compiler packages.  You may wish to use a similar method to remove intel-mkl, intel-ipp, intel-gdb, intel-openmp and other intel packages

Some Linux distributions will also complain about "multiple matches" during the uninstall process.  In this case, the "--allmatches" switch mentioned above can also be employed here.



As noted in the Intel® Software Development Product End User License Agreement, the Intel® Software Development Product you install will send Intel the product’s serial number and other system information to help Intel improve the product and validate license compliance. No personal information will be transmitted.

Links of Interest

The following links are provided for reference information.

Excellent on-line resource for understanding RPMs and their usage.


For more complete information about compiler optimizations, see our Optimization Notice.

For more complete information about compiler optimizations, see our Optimization Notice.