Purpose:The purpose of this article is to provide instructions on how to install/uninstall/manage products from the Intel Composer XE family, including answers to frequently asked questions and tips on how to troubleshoot known problems.<?xml:namespace prefix = o />
The installation of the product requires a valid license file or a serial number. If you are evaluating the product, you can also choose the “Evaluate this product (no serial number required)” option during installation.
You do not need to uninstall previous versions or updates before installing a newer version; the new version will coexist with older versions.
The default online installation package for Intel® Composer XE now consists of a smaller installation package that dynamically downloads and then installs specific packages you select. This requires a working internet connection and may also require a proxy setting if you are behind an internet firewall. Full packages are provided alongside where you download this online install package if a working internet connection is not available.
If you received your product on DVD, insert the first product DVD in your computer’s DVD drive; the installation should start automatically. If it does not, open the top-level folder of the DVD drive in Windows Explorer and double-click on setup.exe.
If you received your product as a downloadable file, double-click on the executable file (.EXE) to begin installation. Note that there are several different downloadable files available, each providing different combinations of components. Please read the download web page carefully to determine which file is appropriate for you.
If you received your product on DVD, mount the DVD, change the directory (cd) to the top-level directory of the mounted DVD and begin the installation using the command:
./install.sh
If you received the product as a downloadable file, first unpack it into a writeable directory of your choice using the command:
tar –xzvf name-of-downloaded-file
Then use the “cd” command to change to the directory containing the unpacked files and begin the installation using the command:
./install.sh
You will need to have administrative or “sudo” privileges to install, change or uninstall the product.
If you received the compiler product on DVD, insert the DVD. Locate the disk image file (xxx.dmg) on the DVD and double-click on it. If you received the compiler product as a download, double-click the downloaded file.
The installation of the product performs a lot of configuration changes in addition to installing files to setup the product. So the uninstallation is not a trivial removal of product files from the systems. We recommend using the product uninstallation capabilities always rather than manually removing the product file by file. The product uninstaller knows better what shall be cleaned.
Please go to Add/Remove Program (ARP), select the product and call “Remove” functionality
Please go to the installed product location and call the script
./uninstall.sh
Please go to the installed product location and call the script
./uninstall_cpro[c|f].sh
Silent (non-interactive) installation
For instructions on how to perform single command line installations, as may be required for enterprise level user environments, please take a look at these guides:
· http://software.intel.com/en-us/articles/intel-compilers-for-linux-silent-installation-guides/
· http://software.intel.com/en-us/articles/intel-compilers-for-windows-silent-installation-guides/
Frequently Asked Questions about product installations
A: The product installer requires several top level dependencies to be resolved before the installation start. Missing these prerequisites can result in incorrect installer behavior and/or problems with product functionality. It could possibly even lead to system crashes or loses of user-sensitive data. This is the installer will not proceed until these dependencies are resolved. Please review the list of most critical prerequisites below.
Missing .Net 4.0
To install .NET Framework 4:
1. Find .NET Framework 4 (http://go.microsoft.com/fwlink/?LinkId=177666).
2. Move down to the Files in This Download section, and click Download for the file required for your computer.
3. Run through the installation, and when installation is complete, click Finish to close the wizard.
PATH overflow
On Windows* 7 or 8, if the installation’s additions to the system PATH causes the PATH length to grow to a size of 2000 to 4000 characters, this may cause the Windows command prompt (cmd.exe) to not work until the next reboot.
See this informative article: http://support.microsoft.com/kb/830473/en-us
The Intel SW products add information to PATH, so if the installer detects that the PATH may be potentially overflowed, the installer will request that you clean up this variable before the installation begins.
UAC
The installation requires system administrator privileges.
GLIBC 2.3.4 and higher are supported
RPM version
If the distributive is RPM-based, be aware that legacy RPM tool versions 4.0.2, 4.1, 4.2.1(x64), and 3.0.5 are not supported.
TMP directory shall be configured
The /tmp directory must exist, must have world read/write/execute permissions, must have at least 100 Mb of free disk space.
OS versions older than 10.8 are not supported.
Non-Intel CPUs (PPC architecture) are not supported.
32-bit CPU is not supported.
The installation requires system administrator privileges
Q: What is my serial number / license / expiration date?
A: First please go to https://registrationcenter.intel.com, login and check your“My Products” section. There, you can find the list of Intel products that you can access to. Please select the product and you will find when support expires for that specific product. You can also manage and renew the product license on this page. It probably will require entering serial number for your product, so have that information available.
If you have problems in this area, please file a request for Technical Support (https://premier.intel.com).
Q: I have installed the product but can’t find a number of components. What should I do?
A: Composer XE has a default set of components that does not match to the full set. So if you used the default install scenario the part of components is not installed. To select all components:
1) If you are installing the product, please go to Pre-Install Summary->Customize and select required components
2) If you have already installed the product please go to Add/Remove Programs (Windows), or call the installer again (Linux / Mac OS) and select “Modify” mode.
Symptoms
1) You are not able to find expected files or product functionality.
2) Linking or compilation problems appear during a software build:
$ icpc test.o -O3 -offload-build -no-intel-extensions -mkl -offload-ldopts="-lmkl_core" -lmkl_core -o test.exe
x86_64-k1om-linux-ld: cannot find -lmkl_core
List of optional Vs. default components
Component name | Selection by default |
Intel Performance Primitives | |
single-threaded libraries | Yes |
multi-threaded libraries | No |
performance test application | No |
Performance test application sub-component shall be enabled for selection only if single-threaded libraries or multi-threaded libraries are selected | |
| |
Intel Math Kernel Licenses for Windows and Linux | |
Intel MKL core libraries | Yes |
Intel(R) Xeon Phi(TM) coprocessor support | Yes |
Fortran 95 interfaces for BLAS and LAPACK | Yes |
GNU* Compiler Collection support (Linux only) | Yes |
PGI* compiler support | No |
PGI* and CVF compiler support | No |
SP2DP interface for Intel(R) 64 | No |
Cluster support | No |
'Intel(R) Xeon Phi(TM) coprocessor support', 'Fortran 95 interfaces for BLAS and LAPACK', 'GNU* Compiler Collection support', 'PGI* compiler support', 'PGI* and CVF compiler support', 'SP2DP interface for Intel(R) 64', 'Cluster support' require 'Intel MKL core libraries' to be selected for the installation | |
SP2DP component is Intel64 only, PGU and CVF compiler support is IA32 only, all other components are provided for both ia32/intel64 architectures | |
| |
Intel Math Kernel Licenses for Mac OS | |
Intel MKL core libraries | Yes |
Fortran 95 interfaces for BLAS and LAPACK | Yes |
PGI* compiler support | No |
SP2DP interface | No |
Please find more details in this informative article:
· http://software.intel.com/en-us/articles/intelr-mkl-new-install-option
Q: Integration with Microsoft Visual Studio does not work
A: Please review the use cases, symptoms and workarounds in shown in the external article below. These are focused on Intel Visual Fortran, but they also apply to other products from the Composer XE family.
If this article does not help, please find other workarounds for frequent problems below.
Compiler or libraries disappears from VS when I install some other package
The MSVS integration unit established product integration to all supported versions of MSVS. When a different integration unit is installed it uninstalls the previous integration. In the case where you have selected different MSVS version to integrate with, the integration disappears from other versions.
To work around the problem, please re-install the compiler or libraries package that “disappeared” from MSVS, being sure to select all available MSVS versions to integrate.
This is a known problem; changes in the MSVS are usually not backward compatible.
To work around this problem, please remove all Intel development products and reinstall the required versions in ascending order.
IPP 7.x/8.x linking with MSVS 2010
Symptoms: error LNK1104: cannot open file 'threaded/ippcoremt.lib
VS 2010 wasn't able to recognize Windows 7 System Control Variables (IPPROOT, IPP_LIBRARY and IPP_INCLUDE). To work around please set all paths manually in PATH System Control Variable.
Symptoms: error LNK2019: unresolved external symbol _ippiMalloc_32f_C1@12 referenced in function _main
To work around please add "/D _IPP_SEQUENTIAL_STATIC" to C++, CommandLine, Additional Options
Please try finding other recommendations from Technical Support: http://software.intel.com/en-us/search/site/language/en?query=integration%20visual%20studio
If you did not find the solution above please try these general tips (in order of the system impact) on how to repair the MSVS integration:
1) Go to Add/Remove Programs and select “Modify” of the product. Unselect all available integrations. Re-install the product.
2) Repair MSVS.
3) Repair the product.
4) Uninstall the product. Uninstall MSVS. Re-install MSVS. Re-install the product
If you have tried the suggestions above and things are still not working correctly, please file a request to Technical Support (https://premier.intel.com)
Q: I have file access problems (Windows Installer fails with the error 2203). What do I do?
A: Please review this article for more details:
· http://software.intel.com/en-us/articles/installer-fails-with-error-2203
Q: I can’t uninstall or upgrade the Composer XE for Windows to a newer version. What do I do?
Symptoms: the uninstaller refers to the empty MSI or can’t find “ism.msi” file
A: Please do not use “Add/Remove Programs” capabilities to manage the product content. Please get the initial package; insert the DVD with the package, find the package in the local cache, or download the package from Intel Registration Center (https://registrationcenter.intel.com). Start “Setup.exe” from the package and manage the product (repair, modify or uninstall)
Q: I can’t uninstall Linux products. What do I do?
Q: I lost the product uninstaller for Linux. How can I remove the package manually?
A: The Linux installer uses RPM units as core installation units, or the local database for non-root accounts and non-RPM distributives. How to remove the product manually for Linux:
1) If you have only one Intel package installed to the system, or you would like to remove all Intel packages please call: #> rpm –qa | grep intel- | xargs rpm –e --nodeps --allmatches
2) If you would like to remove some specific package, please obtain the build or “package” number
a. It can be found in the name of the package archive: l_ccompxe_2015_beta.0.005.tgz
b. If you do not have the package available, please visit the Intel Registration Center (https://registrationcenter.intel.com) to get the package number.
3) Command: #> rpm –qa | grep intel- | grep “package_number” | xargs rpm –e --nodeps --allmatches
Non-Root or non-RPM instruction
1) If you have only one Intel package installed on the system, or you would like to remove all Intel packages please use these commands:
#> cd ${HOME}/intel
#> rm –f intel_sdp_products.db
#> ls -a | grep .intel | grep log | xargs rm -f
2) If you would like to remove some specific package, please obtain the build or “package” number
a. It can be found in the name of the package archive: l_ccompxe_2015_beta.0.005.tgz
b. If you do not have the package available, please visit Intel Registration Center (https://registrationcenter.intel.com) to get the package number
3) Commands:
#> cd ${HOME}/intel
#> mv intel_sdp_products.db intel_sdp_products.db_backup
#> cat intel_sdp_products.db_backup | grep -v “package_number” > intel_sdp_products.db
#> ls -a | grep .intel | grep log | grep "006" | xargs rm –f
What if none of this works? How do I contact Technical Support?
A: If none of the above methods help to resolve your problem, please file a request with Technical Support (https://premier.intel.com).
Please provide the following information to help the support team resolve your problem:
1) OS version, architecture, an available disk space
2) Intel product name and full version that you try to install
3) Intel products names and versions installed on the system (navigate Add/Remove Programs)
4) MSVS versions
5) Detailed instruction on how to reproduce the problem (a screenshot or a screen-log is highly appreciated)
6) Install log file: %temp%\ComposerXE*.Log
7) The build log file if the problem appears during a software build. Open Tools.Options dialog and set property "Projects and Solutions -> Build and Run -> MSBuild project build log file verbosity" to "Diagnostic". Then rebuild your project. Find the log file in your intermediate build directory (Debug or Release), it's a file with the same name as your project and log extension
8) Compiler integration version. You can find it in “Help-->About” MSVS dialog. Open the dialog and navigate to the product entry in the list of installed products and copy “Product Details” from the box
1) OS version: #> cat /etc/*issue
Architecture: #> uname -a
Partition/disk space: #> df –h
2) Intel product name and full version that you try to install
3) Intel products names and versions installed to the system: #> rpm –qa | grep intel
4) Detailed instruction how to reproduce the problem (a screenshot or a screen-log is highly appreciated)
5) Install log file:
/tmp/intel.pset.UID***.log
/tmp/intel.issa.UID***.log
1) OS version, architecture: #> sw_vers
Partition/disk space: #> df –h
2) Intel product name and full version that you try to install
3) Intel products names and versions installed to the system: #> pkgutil --pkgs | grep intel
4) XCode version: Launch Xcode, menu: Xcode > About Xcode OR
# xcodebuild –version
5) Installed SDKs:
# xcode-elect - - print-path OR
# xcodebuild -showsdks
6) Detailed instruction how to reproduce the problem (a screenshot or a screen-log is highly appreciated)
7) Install log file: /var/log/install.log, /var/log/system.log