How to Uninstall the Intel Compilers for Linux
STEP 0: Use 'uninstall.sh' script if possible
To uninstall the Intel compilers for Linux, the best and recommended method is to use the uninstall.sh script in the /bin directory under your compiler installation, typically /opt/intel/composer_xe_<version>.<update>.<build>/bin/uninstall.sh
Help finding 'uninstall.sh': if you are unsure where to find uninstall.sh scripts (one per version), use the linux 'find' command to help:
find <install dir> -name uninstall.sh
for example, <install dir> defaults to /opt/intel:
find /opt/intel -name uninstall.sh
If for some reason the uninstall.sh is not found, not working ( compiler was removed with 'rm' accidentially, moved, corrupted, etc) it is possible to remove the Intel compiler using RPM. Most linux distributions either use RPM natively for package management or provide RPM for compatibility. Intel Intel compiler installation will use RPM to install the compiler. The RPM database ON THE HOST USED FOR THE INSTALLATION will keep rpm database records of this installation.
STEP 1: determine if your installation host has RPM records for the installation(s)
login to the installation host system as root, or if you have sudo priviledge, do this:
followed by entering your sudo user password. If you don't have root priviledge, no sudo permissions, and you did the installation as a regular user skip to STEP 2 below.
next, check to see if there are Intel compiler RPM entries:
rpm -qa | grep intel-
The Intel compiler installs dozens of RPM packages. They can be identified by names such as:
12.x, 13.x, 14.x era compilers: intel-compilerpro*. Look for versioning information such as
intel-compilerpro-*-<build>-<major version>.<minor version>-<update number>
as an example: intel-compilerpro-common-192-13.1-5 where the build is 192, major version 13, minor version 1, update 5
11.x era compilers: intel-cpro<package><build>-<major version>.<minor version>-<update>.<architecture>
and example: intel-cproc038-11.1-1.i486 - Intel C++ Professional version 11.1 update 1 for IA32 architecture.
If you don't see any "intel-compxe" or "intel-cpro" or "intel-fpro" or any other packages obviously related to the compiler, skip to STEP 2 below
Find your build number, such as "192" or "038" in the names above as an example. We will use that build number to remove all RPMs for that compiler build.
Execute the following command to remove all RPMS associated with your compiler build number:
rpm -e --allmatches `rpm -qa | grep intel- | grep <build>`
note the back quote character "`" and NOT single quote. Again, <build> will be the build number you wish to remove. In our examples:
rpm -e --allmatches `rpm -qa | grep intel- | grep 192`
rpm -e --allmatches `rpm -qa | grep intel- | grep 032`
Verify your work with
rpm -qa | grep intel
to confirm that all Intel compiler RPMs are removed from the RPM database.
Here is an example of the RPMs installed by the C++ and Fortran compilers, Composer XE 2013 SP1 Update 5. The number of RPMs, names, versions, etc. change over time. This is just a representative list of compiler RPMs from summer 2013:
rpm -qa | grep intel- | grep 192
STEP 2: remove Intel compiler files left over in the installation directory (if any)
If there are any left over Intel Compiler files in the installation directory, /opt/intel by default or wherever you installed the compiler, remove all of those EXCEPT FOR the licenses directory, typically /opt/intel/licenses. Licenses kept in the <installation dir>/licenses should be kept, do not delete that directory.
Use 'rm -Rf <install dir>/<subdirs>' to remove all directories in <install dir> except for the licenses/ directory. Remove all symbolic links in <install dir>
STEP 3: remove ~/intel directory (if it exists)
Non-root installations will create a ~/intel (your home directory/intel ) subdirectory by default. Here, the installer will keep track of files installed by the Intel compiler installer. Remove this directory as it can contain past history of the non-root compiler installation.
After all 3 steps, your system should be clean of any past installations. If for some reason this does not clear up your issues with the Intel compiler, please contact us on our Linux User Forums: