This document explains how to install and configure for use the Intel® Fortran 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 Fortran 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.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.
If you have licensed Intel® Fortran Compiler Professional Edition, download and installation of the Intel® Math Kernel Library is separate. Please refer to the Installation Guide and/or Release Notes of that component for details.
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/fc/10.0.xxx
(for IA-32 and IA-64)
/opt/intel/fce/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 do not want to keep multiple versions, you can delete the older directories before or after installing the new version.
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_fc_p_10.0.xxx.tar
> tar -zxvf l_fc_p_10.0.xxx.tar.gz
> cd l_fc_p_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.
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 Fortran 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 (ifortvars.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/ifortvars.sh(.csh)
> source <idb-install-dir>/bin/idbvars.sh(.csh)
The installation program also creates compiler configuration files named <install-dir>/bin/ifort.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 any problems running the compiler, please make sure a valid license
file (*.lic) is located in the license directory. By default this is /opt/intel/licenses
.
The compiler uses the environment variable INTEL_LICENSE_FILE
to
locate the license file. If you still have problems, please submit an issue
to Intel® Premier Support. See the Technical Support section of this document
for details.
If you have not already done so, please register for support after you install this product. See 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/fc/10.0.xxx/bin/uninstall.sh
or/opt/intel/fce/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 Fortran Compiler Users Forums, FAQ's, tips and tricks, and other support information, please visit: http://support.intel.com/support/performancetools/fortran/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 of Intel Corporation in the United States and other countries.
* Other names and brands may be claimed as the property of others.
Copyright (C) 2007, Intel Corporation.