This document explains how to install and configure for use the Intel® C++ Compiler 10.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 an older 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.
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 that will run on the same platform that it was built on, 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 IA-64. 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: Intel® Cluster OpenMP* is a separately licensed feature and has different system requirements from that of the compilers. Please refer to the Intel Cluster OpenMP documentation for further details.
compat-libstdc++ providing libstdc++.so.5 compat-libstdc++ providing libstdc++.so.5 compat-libstdc++ providing libstdc++.so.5
The Intel compilers are tested with a number of different Linux distributions, with different versions of gcc. If you are using any of gcc 3.2.3, 3.3.3, 3.3, 3.2, 3.4, 4.0, 4.1, you can expect to be successful. However the version of binutils can impact your experience: later ones are generally better and we recommend using at least 2.14. Some Linux distributions may contain header files different from those we have tested, which may cause problems. The version of glibc you use must be consistent with the version of gcc in use.
Notes:
-O3, -ipo and -openmp,
may require substantially larger amounts of RAM.On systems where these browsers are not installed by default or available otherwise, such as on a SGI Propack4 system, an alternate browser, e.g. Konqueror, can be used in the Eclipse Integrated Development environment. Within Eclipse, set it as the browser to be used by selecting Windows->Preferences->General->Web Browser and entering it as the external Web Browser. Note that such a browser cannot be designated as the internal Web Browser within Eclipse, and thus there will be no support available for internal web browsing with this configuration.
Before installing the compiler and tools, you should check the Product Downloads section of the Intel® Registration Center 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 under Technical Support.
At the Intel Registration Center, the compiler is provided in several different packages to meet your needs. The filenames and descriptions of the packages are:
If you encounter difficulty with the initial installation or registration process, please visit https://registrationcenter.intel.com/support to request help from Intel.
The default installation directories, referred to elsewhere in this document
as <install-dir> and <idb-install-dir>,
are:
/opt/intel/cc/10.0.xxx (for IA-32 and IA-64)
/opt/intel/cce/10.0.xxx (for Intel® 64)
/opt/intel/idb/10.0.xxx (for IA-32 and IA-64)
/opt/intel/idbe/10.0.xxx (for Intel® 64) Note that the path includes the full version number including update number. This means you can keep multiple versions of the compiler installed on the system.
If you are installing both the Intel C++ Compiler and the Intel Fortran Compiler, they each provide the Intel Debugger. If the update numbers are different between the C++ and Fortran installations, the Intel Debugger update numbers will also differ. If you are installing compilers for both languages which were released at the same time, we recommend that you choose a Custom Install for the Fortran compiler and don't install the Intel Debugger a second time, as the debuggers will be the same. Installing the debugger from the Intel C++ package provides Eclipse* integration.
Perform the following steps to install the compiler.
> tar -xvf l_cc_b_10.0.xxx.tar > tar -zxvf l_cc_b_10.0.xxx.tar.gz
> cd l_cc_b_10.0.xxx
> ./install.sh install as current user option if you want to
install to a private area.
1 and
press enter to begin the compiler installation.
1 and press enter.
accept and press enter. If you reject the
license, type
reject and press enter to end the install.
x and
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.
The 10.0 versions of the Intel C++ Compiler for IA-32 and the Intel C++ Compiler for Intel Itanium(R) installs an Eclipse feature and associated plugins (the Intel C++ Eclipse Product Extension) which provide support for the Intel C++ compiler when added as an Eclipse product extension site to an existing instance of the Eclipse* Integrated Development Environment (IDE). With this feature, you will be able to use the Intel C++ compiler from within the Eclipse integrated development environment to develop your applications. The Intel provided Eclipse product extension resides in <install-dir>/eclipse in your compiler installation directory area.
Use of the Intel feature provided in the 10.0 release requires Eclipse Platform version 3.2.x, Eclipse C/C++ Development Tools (CDT) version 3.1.x and a functional Java Runtime Environment (JRE). If you already have the proper versions of Eclipse, CDT and a functional JRE installed and configured in your environment, then you can install the Intel C++ Eclipse Product Extension in your Eclipse Platform, as described in the section, below, entitled "How to Install the Intel C++ Eclipse Product Extension in Your Eclipse Platform." Otherwise, you will first need to obtain and install Eclipse, CDT and a JRE, as described in the section, below, entitled "How To Obtain and Install Eclipse, CDT and a JRE" and then install the Intel C++ Eclipse Product Extension.
To add the Intel C++ product extension to your existing Eclipse configuration, follow these steps, from within Eclipse. Open the "Product Configuration" page by selecting:
Help > Software Updates > Manage Configuration
Under "Available Tasks," select "Add An Extension Location." A directory browser will open. Browse to select the eclipse directory in your Intel C++ compiler installation. For example, if you installed the compiler as root to the default directory, you would browse to /opt/intel/cc/10.0.xxx/eclipse. When asked to restart Eclipse, select "Yes." When Eclipse restarts, you will be able to create and work with CDT projects that use the Intel C++ compiler. See the Intel C++ Compiler documentation for more information.
If you also installed the Intel idb debugger product extension along with the idb Eclipse product extension, and would like to use idb within Eclipse, you should add the idb product extension site to your Eclipse configuration in the same way. For example, if you installed the idb kit as root to the default directory, you would find the idb Eclipse product extension site at /opt/intel/idb/10.0.xxx/eclipse.
If you do not have Eclipse and CDT already, you can download the required components from the eclipse.org website. You will also need a Java Runtime Environment (JRE) if you do not already have one.
First, you will need to download the Eclipse "Platform Runtime Binary" for each platform (x86 and/or Itanium) that you want to run Eclipse on. The current released version for 3.2.x is 3.2.1. From within your web browser, visit the following url:
http://download.eclipse.org/eclipse/downloads/drops/R-3.2.1-200609210945/index.php
Scroll down to the section on that page titled "Platform Runtime Binary." In the list of available downloads, you will see a download for the x86 platform, "Linux (x86/GTK 2)," with file eclipse-platform-3.2.1-linux-gtk.tar.gz. Download this file if you want to use Eclipse on the x86 platform. In the same list, you will see a download for the Itanium platform, "Linux (ia64/gtk)", with file eclipse-platform-3.2.1-linux-gtk-ia64.tar.gz. Download this file if you want to use Eclipse on the Itanium platform.
Next, you will need to download the latest release of the Eclipse C/C++ Development Tools (CDT), CDT Runtime Feature, version 3.1.x. The most recent release of CDT 3.1.x is version 3.1.1. In your browser, visit the following url:
http://download.eclipse.org/tools/cdt/releases/callisto/dist/3.1.1/
In the list of available "CDT Runtime Feature" downloads, you will see a download for the x86 platform, "Linux/x86", with file org.eclipse.cdt-3.1.1-linux.x86.tar.gz. Download this file if you want to use Eclipse on the x86 platform. In the same list, you will see a download for the Itanium platform, "Linux/ia64," with file org.eclipse.cdt-3.1.1-linux.ia64.tar.gz. Download this file if you want to use Eclipse on the Itanium platform.
Finally, Eclipse is a Java application and therefore requires a Java Runtime Environment (JRE) to execute. The 3.2.x version of the Eclipse platform will run with a version 1.4.2 or later JRE. Intel recommends the JRockit 5.0 JRE from BEA Systems Inc., although other comparable JREs should work as well. Both the x86 and Itanium versions of the JRockit 5.0 JRE are available at this url:
http://commerce.bea.com/products/weblogicjrockit/5.0/jr_50.jsp
Once you have downloaded the appropriate files for Eclipse, CDT, and a JRE, you can install them as follows:
tar -zxvf eclipse-platform-3.2.1-linux-gtk.tar.gz
tar -zxvf org.eclipse.cdt-3.1.1-linux.x86.tar.gzYou are now ready to launch Eclipse. After you start Eclipse, you can add the Intel C++ product extension to your Eclipse configuration as described in the section, "How to Install the Intel C++ Eclipse Product Extension in Your Eclipse Platform." If you need help with launching Eclipse for the first time, please read the next section.
If you have not already set your LANG environment variable, you will need to do so. For example,
setenv LANG en_US
Setup Intel C++ compiler related environment variables by executing the iccvars.sh (or .csh) script prior to starting Eclipse:
source /opt/intel/cc/10.0.xxx/bin/iccvars.sh
(where "xxx" is the version number)
If you installed the Intel idb debugger integration into Eclipse, and would like to use idb within Eclipse, you should setup the Intel idb environment variables, in a similar fashion, by invoking the idbvars.sh (or .csh) script.
Since Eclipse requires a JRE to execute, you must ensure that an appropriate JRE is available to Eclipse prior to its invocation. You can set the PATH environment variable to the full path of the folder of the java file from the JRE installed on your system or reference the full path of the java executable from the JRE installed on your system in the -vm parameter of the Eclipse command, e.g.:
eclipse -vm /JRE folder/bin/java
Invoke the Eclipse executable directly from the directory where it has been installed. For example:
<eclipse-install-dir>/eclipse/eclipse
If the Intel C++ Compiler for Linux is installed
on an IA-32 Fedora Core system as a "local" installation, i.e.
not installed as root, the installation may fail to properly execute the Eclipse
graphical user interfaces to the compiler or debugger.
The failure mechanism will typically be displayed as a JVM Terminated error.
The error condition can also occur if the software is installed from the root
account at the system level, but executed by less privileged user accounts.
The cause for this failure is that a more granular level of security has been implemented on Fedora Core 4, but this new security capability can adversely affect access to system resources, such as dynamic libraries. This new SELinux security capability may require adjustment by your system administrator in order for the compiler installation to work for regular users.
Note that this issue affects IA32 systems only, as Fedora Core is not available on IA-64 systems and the Intel C/C++ Compiler integration into Eclipse is not currently supported on Intel® 64-based systems.
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, license managers can be downloaded from Intel® Premier Support. Please note that the Intel License Server is not available for all platforms on which the compiler itself is supported.
If you will be installing the Intel License Server on an SGI* Altix* system running SGI ProPack*, please follow these alternate instructions to ensure correct operation in the partitioned cluster environment:
Obtain the appropriate license server from Intel® Premier Support. The
file to use is flexlm.Linux.ia64.EL3_SGIAltix.tar.Z.
Install the license server following the instructions in the flexlm_ug.pdf documentation
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
(default is /opt/intel/flexlm) and perform the following command:
./lmhostid
The programs in the Intel C++ Compiler 10.0 for Linux product rely on the environment
variables PATH and LD_LIBRARY_PATH. The installation script (install.sh) creates
compiler environment script files (iccvars.sh/idbvars.sh) that
set these variables. It is strongly recommended that you add those script files
into your login script (.login file). Once the variables are set
in the ".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 <idb-install-dir>/bin/idbvars.sh(.csh) The installation program also creates compiler configuration files named <install-dir>/bin/icc.cfg that
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 root
<install-dir>/bin/uninstall.sh /opt/intel/cc/10.0.xxx/bin/uninstall.sh or/opt/intel/cce/10.0.xxx/bin/uninstall.sh on Intel® 64-based systems
<idb-install-dir>/bin/uninstall.sh /opt/intel/idb/10.0.xxx/bin/uninstall.sh or/opt/intel/idbe/10.0.xxx/bin/uninstall.sh on Intel® 64-based
systems Your feedback is very important to us. To receive technical support for the tools provided in this product and for technical information including FAQ's and product updates, please visit http://www.intel.com/software/products/support .
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.
Developers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." Improper use of reserved or undefined features or instructions may cause unpredictable behavior or failure in developer’s software code when running on an Intel processor. Intel reserves these features or instructions for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from their unauthorized use.
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.
This document as well as the software described in it is furnished under license and may only be used or copied in accordance with the terms of the license. The information in this document is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Intel Corporation. Intel Corporation assumes no responsibility or liability for any errors or inaccuracies that may appear in this document or any software that may be provided in association with this document. Except as permitted by such license, no part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means without the express written consent of Intel Corporation.
BunnyPeople, Celeron, Celeron Inside, Centrino, Centrino logo, Core Inside, FlashFile, i960, InstantIP, Intel, Intel logo, Intel386, Intel486, Intel740, IntelDX2, IntelDX4, IntelSX2, Intel Core, Intel Inside, Intel Inside logo, Intel. Leap ahead., Intel. Leap ahead. logo, Intel NetBurst, Intel NetMerge, Intel NetStructure, Intel SingleDriver, Intel SpeedStep, Intel StrataFlash, Intel Viiv, Intel vPro, Intel XScale, IPLink, Itanium, Itanium Inside, MCS, MMX, Oplus, OverDrive, PDCharm, Pentium, Pentium Inside, skoool, Sound Mark, The Journey Inside, VTune, Xeon, and Xeon Inside are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
* Other names and brands may be claimed as the property of others.
Copyright (C) 2007, Intel Corporation.