This document explains how to install and configure for use the Intel® C++ Compiler 9.0 for Linux* product. Installation is a multi-step process. Please read this document in its entirety before beginning and follow the steps in sequence. For information about the product contents, including new and changed features, please refer to the separate Release Notes.
If you have a previous (lower numbered) version of the Intel C++ Compiler for Linux installed, you do not need to uninstall it before installing this version. If you choose to uninstall the older version, you may do so before or after installing this version. If you have version 9.0 installed, you can choose to replace the existing install or install to an alternate location.
Intel compilers support three platforms: general combinations of processor and operating system type. This section explains the terms that Intel uses to describe the platforms in its documentation, installation procedures and support site.
The term "native" refers to building an application on a platform type the same as the one on which it will be run, for example, building on IA-32 to run on IA-32. The term "cross-platform" or "cross-compilation" refers to building an application on a platform type different from the one on which it will be run, for example, building on IA-32 to run on Intel Itanium®. Not all combinations of cross-platform development are supported and some combinations may require installation of optional tools and libraries.
The following list describes the supported combinations of compilation host (system on which you build the application) and application target (system on which the application runs).
Note: Development for a target different from the host may require optional library components to be installed from your Linux Distribution.
Note: The requirement for the 32-bit (IA-32) libraries is due to the compiler and other tools being 32-bit applications that dynamically link to these libraries. If these libraries are not installed, the following error may be displayed when the compiler is invoked:
error while loading shared libraries: libstdc++.so.5: cannot open shared
object file: No such file or directory
The error message is confusing as it does not indicate that the IA-32 version of libstdc++.so.5 is required. To avoid this problem, be sure that the 32-bit (IA-32) versions of these libraries are installed. Most, but not all, Linux distributions for Intel EM64T will install these by default. Consult the documentation that came with your Linux distribution for instructions on how to install the 32-bit libraries, typically in packages named libstdc++ and libc. If you still have problems, please contact Intel® Premier Support for further assistance.
We recommend using binutils 2.14 or later, especially if using shared libraries as there are known issues with binutils 2.11.
-openmp, may require substantially larger amounts of RAM.
Before installing the compiler and tools, you should check the File Downloads section of Intel® Premier Support to see if a newer version or update is available. The version on CD or as listed in your electronic download license letter may not be the most current. In order to download and install a compiler from Intel® Premier Support, you will first have to register for support as described below in the topic Obtaining Technical Support.
If you encounter difficulty with the initial installation or registration process, please visit https://registrationcenter.intel.com/support to request help from Intel.
Perform the following steps to install the compiler.
> tar -xvf l_cc_c_9.0.xxx.tar
> tar -zxvf l_cc_c_9.0.xxx.tar.gz
> cd l_cc_c_9.0.xxx
ignore- the last says to install as not root. Use the not-root install if you want to install to a private area.
1and press enter to begin the compiler installation.
1and press enter.
acceptand press enter. If you reject the license, type
rejectand press enter to end the install.
xand press enter to exit.
RPM 4.0.2 cannot install to a non-default directory. This has been resolved in RPM 4.0.3. RPM 4.1 cannot install to a non-default directory. This has been resolved in RPM 4.11 to 4.2.
Version 9.0 of the Intel C++ Compiler for IA-32 optionally installs the Eclipse* Integrated Development Environment (IDE) version 3.0.1 with C/C++ Development Tools (CDT) version 2.1.1, a Java* Runtime Environment (JRE) and the Intel C++ 9.0 compiler integration, which is required to use the Intel C++ Compiler within Eclipse. If you wish to use the Intel C++ compiler integration with your own instance of Eclipse, CDT and/or a JRE, you can. However, note that it is your responsibility to ensure that you are using the supported versions of Eclipse and CDT as well as a compatible JRE.
To use your own version of the JRE (rather than the JRE supplied in the 9.0 Intel C++ compiler kit) with the other Eclipse components supplied in the kit, do the following:
OTHER_JVM_BINDIRto the full path of the folder of the java file from the JRE installed on your system. If you are using the bash shell, make sure that you export this environment variable.
To determine if a JRE is compatible with a particular version of Eclipse, refer to the website www.eclipse.org . There you will find references to JRE kits that are supported with a particular version of Eclipse, as well as links to websites where JRE kits can be downloaded. Note that Intel has only tested the JRE supplied in the Intel C++ compiler kit.
Note: The Sun* JRE does not work with Eclipse and the Intel Eclipse integration on Itanium-based systems. JREs from JRockit* and IBM* are suggested alternatives.
To use your own instances of Eclipse, CDT and a JRE, you will need to create
appropriate files and folders so that the Intel C++ compiler integration gets
plugged into your pre-installed Eclipse environment. If you want to use the
<install-dir>/bin/iccec file (
<install-dir> is the location where the Intel C++ Compiler is
installed), you will need to make the following changes in the
Intel C++ Compiler for 32-bit applicationsand the
Plugins/Features for Integration into Eclipse*. When you choose
Plugins/Features for Integration into Eclipse*, the Intel C++ Compiler features and plugins for integration into Eclipse* CDT development environment will be installed automatically. After the installation of these plugins and features, in the next screen, you can choose the option
Integrate Intel(R) C++ Compiler Version 9.0 into Eclipse* installed at different location. You will be asked to provide the location where Eclipse is installed. Provide the location and exit the installation.
OTHER_JVM_BINDIRto the full path of the folder of the java file from the JRE installed on your system, as described above.
OTHER_ECLIPSE_BINto the full path of the
eclipsebinary in the Eclipse installation folder. If you are using the
bashshell, make sure that you export this environment variable. For example, if you have installed Eclipse in
OTHER_ECLIPSE_BINshould be set to
/opt/intel/eclipse/eclipse. (Make sure that this file exists.)
LD_LIBRARY_PATHto include the appropriate folder in which Eclipse is installed
If you have a floating, counted or node-locked license, the license must be
installed in conjunction with the FLEXlm* license server for Intel software
(Intel License Server), which is available for many popular platforms. The
server may be installed on any supported platform accessible on your local
network. The compiler CD contains license servers for several Linux distributions.
If you do not have the CD, or need a license server for an additional platform,
you can find all available license servers in the File Downloads section
of your Intel® Premier Support account
- select product
Intel SW Dev Tools License Servers to find the
server for your platform.
If you will be installing the Intel License Server on an SGI* Altix* system running SGI ProPack* 3, please follow these alternate instructions to ensure correct operation in the partitioned cluster environment:
Obtain the appropriate license server from Intel® Premier Support
File Downloads at https://premier.intel.com/.
On the File Downloads page, select product
Intel SW Dev Tools License
Servers. The file to use is
Install the license server following the instructions in the
file in the compiler package.
To determine the host ID, required to retrieve the license file, log in
to the partition from which the license server is to be run, set default
cd) to the directory where the Intel License Server is installed
/opt/intel/flexlm) and perform the following command:
The programs in the Intel C++ Compiler 9.0 for Linux product rely on the environment
LD_LIBRARY_PATH. The installation script
compiler environment script files
set these variables. It is strongly recommended that you add those script files
into your login script (
.login file). Once the variables are set
".login" file there is no need to run the script
files for each session.
source the script to setup the compiler environment:
> source <install-dir>/bin/iccvars.sh(.csh)
> source <install-dir>/bin/idbvars.sh(.csh)
The installation program also creates compiler configuration files named
contain common settings for all compilations. You can edit these files to add
additional default options. Note,
if you install a compiler update package, you need to save the configuration
file, if you have modified it, to another filename so that the installation
doesn't overwrite your modified file.
If you have not already done so, please register for support after you install this product. See the topic Obtaining Technical Support below for registration instructions.
Please follow the steps below to uninstall the Intel Compiler and Debugger.
root, you will need to log in as
/opt/intel/cce/9.0/bin/uninstall.shon Intel EM64T-based systems
/opt/intel/idbe/9.0/bin/uninstall.shon Intel EM64T-based systems
Note: If your distributor provides technical support for this product, please contact them for support rather than Intel.
For information about the Intel C++ Compiler Users Forums, FAQ's, tips and tricks, and other support information, please visit: http://support.intel.com/support/performancetools/c/linux/. For general support information please visit http://www.intel.com/software/products/support/.
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS.
NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL
PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S
TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY
WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO
SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING
TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY
PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. Intel products are
not intended for use in medical, life saving, life sustaining, critical control
or safety systems, or in nuclear facility applications.
Intel may make changes to specifications and product descriptions at any time, without notice.
Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them.
The software described in this document may contain software defects which may cause the product to deviate from published specifications. Current characterized software defects are available on request.
BunnyPeople, Celeron, Centrino, Centrino logo, Chips, Dialogic, EtherExpress, ETOX, FlashFile, i386, i486, i960, iCOMP, InstantIP, Intel, Intel logo, Intel386, Intel486, Intel740, IntelDX2, IntelDX4, IntelSX2, Intel Inside, Intel Inside logo, Intel NetBurst, Intel NetMerge, Intel NetStructure, Intel SingleDriver, Intel SpeedStep, Intel StrataFlash, Intel Viiv, Intel XScale, IPLink, Itanium, MCS, MMX, MMX logo, Optimizer logo, OverDrive, Paragon, PDCharm, Pentium, Pentium II Xeon, Pentium III Xeon, Performance at Your Command, skoool, Sound Mark, The Computer Inside., The Journey Inside, VTune, Xeon, and Xircom are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Intel's trademarks may be used publicly with permission only from Intel. Fair use of Intel's trademarks in advertising and promotion of Intel products requires proper acknowledgement.
*Other names and brands may be claimed as the property of others.
Copyright © 2006, Intel Corporation.