Installing Intel® oneAPI Toolkits via YUM (DNF)

This page provides general installation and support notes about the Intel oneAPI toolkits distributed via YUM (DNF) repository.

LEGAL NOTICE: By downloading and using these packages and the included software, you agree to the terms and conditions of the software license agreements located at the End User License Agreements page.

By proceeding you acknowledge that you have read the EULA and agree to the terms and conditions of this agreement.

Important: If you have an existing installation of Intel^® oneAPI Beta, you should remove it before installing the Gold version.

Note: The YUM (DNF) repository is a public repository on the general Internet. If you are on a company intranet behind a firewall you may need to set environment variables https_proxy and http_proxy to your company's proxy server and port. Please contact your local network or system administrators for assistance if you are unfamiliar with using proxy servers.

List of Intel® oneAPI Packages

Toolkit Packages

The following toolkits and associated versions are available
THE REPOSITORIES ALWAYS CONTAIN THE LATEST RELEASED VERSION
 

intel-basekit

intel-basekit-32bit

intel-hpckit

intel-hpckit-32bit

intel-iotkit

intel-iotkit-32bit

 intel-dlfdkit

 intel-dlfdkit-32bit

 intel-aikit

 intel-aikit-32bit

intel-renderkit

intel-renderkit-32bit

intel-oneapi-intelfpgadpcpp-a10gx-s10sx

intel-oneapi-intelfpgadpcpp-custom-platforms-quartus19.4

intel-oneapi-intelfpgadpcpp-custom-platforms-quartus20.2

intel-oneapi-intelfpgadpcpp-custom-platforms-quartus20.3

Runtime Library Packages

The oneAPI repository provides runtime library packages. These packages can be installed on systems that will host oneAPI applications: hosts where you do not want to install the oneAPI Development Toolkits. These are hosts where you run applications but do not do development, compilation, or runtime profiling. The following runtime library packages are available:

•  oneAPI runtime libraries package, which is a superset of all runtimes for oneAPI components:
  • 64-bit: intel-oneapi-runtime-libs
  • 32-bit: intel-oneapi-runtime-libs-32bit
• Component runtime library packages. For instructions on how to get the list of all availbale standalone runtime packages, refer to the List Standalone Runtime Library Packages section of the Appendix.

Installation of Intel^® oneAPI Toolkits on a supported Linux system requires the following steps:

1. If you have an existing Intel oneAPI Beta installation, remove it before installing Intel oneAPI Gold. After removing your Beta installation you can skip to Step 5.
2. Make sure your OS is supported. The OS version can be found using one of these commands in a terminal window:

   # Redhat, Fedora, CentOS and related
   more /etc/redhat-release
   
   # Ubuntu, Debian, others
   more /etc/lsb-release
   

   • Look for supported OSes in the System Requirements section in the appropriate Intel® oneAPI Toolkits product pages.
3. Install the required drivers If this is your first installation of Intel oneAPI.
4. Set up your package manager to use the Intel repository as described below.
5. Determine which Intel oneAPI toolkit package or packages you require using the Table of Packages. Write down or copy your package name and follow the installation instructions.
6. (Optional) If you also want to integrate tools into the Eclipse* IDE, Open Eclipse and verify that a menu titled “Intel” is present. If the menu is not present read this guide to Installing Eclipse* Plugins from the IDE.
7. What's Next? Get Started with the Intel® oneAPI Toolkits for Linux*.

Install Intel oneAPI Packages

Intel provides access to all of its oneAPI toolkits and packages through a public YUM (DNF) repository. The yum or dnf command is the primary tool for getting, installing, deleting, querying, and otherwise managing Red Hat* Enterprise Linux* RPM software packages. See below for instructions on how to pull the latest versions of the Intel tools. For more information, visit the official yum command cheat sheet.

1. If you have an existing oneAPI Beta installation, use {yum|dnf} autoremove <packages> to remove it. For example:

   # YUM:
   sudo -E yum autoremove intel-hpckit intel-basekit
   
   # DNF:
   sudo -E dnf autoremove intel-hpckit intel-basekit

   Once the Beta installation is removed you may skip to Step 4 below to install your Toolkit(s).

2. Setup the oneAPI repository. First, make sure you have write permissions to /tmp.
   Next, create the YUM (DNF) repo file in the /tmp directory as a normal user:

   tee > /tmp/oneAPI.repo << EOF
   [oneAPI]
   name=Intel(R) oneAPI repository
   baseurl=https://yum.repos.intel.com/oneapi
   enabled=1
   gpgcheck=1
   repo_gpgcheck=1
   gpgkey=https://yum.repos.intel.com/intel-gpg-keys/GPG-PUB-KEY-INTEL-SW-PRODUCTS.PUB
   EOF
   

    

3. Move the newly created oneAPI.repo file to the YUM (DNF) repo configuration directory /etc/yum.repos.d

   sudo mv /tmp/oneAPI.repo /etc/yum.repos.d
   

    

4. Install the desired package. Determine which Intel^® oneAPI Toolkit package or packages you require using the Table of Packages provided earlier in this document. If you are on a company intranet or behind a firewall make sure to set environment variables http_proxy and https_proxy appropriate to allow yum access the repository servers using https protocol.
   To install a toolkit, for example the Intel^® oneAPI Base Toolkit, which meta package name is intel-basekit, use the following command:

   When installing on a machine with no internet access, or in the case of a large distributed installation on a cluster, YUM (DNF) supports downloading a package without installing it. See here for more details.
    

   # YUM:
   sudo yum install intel-basekit
   
   # DNF:
   sudo dnf install intel-basekit

    

5. Set up user environment. After oneAPI tools are installed, before accessing the tools, you must set up environment variables to access the tools.

   • See the Before You Begin page for setting up environment. Then proceed to Run a Sample Project Using the Command Line to confirm correct installation.
   • Next, you might consider adding the 'source' of 'setvars.sh' to your ~/.bash_profile startup script. If you manage a multi-user system, consider how to source this script for all login users, such as adding to your /etc/profile startup script or add it to user tools environment using modulefiles or similar.
6. (Optional) If you also want to integrate tools into the Eclipse* IDE, Open Eclipse and verify that a menu titled “Intel” is present. If the menu is not present read this guide to Installing Eclipse* Plugins from the IDE.
7. Installation complete! What's next? Get Started with the Intel^® oneAPI Toolkits for Linux*.

Note: If you have applications with long-running GPU compute workloads in native environments, you must disable the hangcheck timeout period to avoid terminating workloads.

Upgrade Intel oneAPI Toolkit/Component

You can upgrade toolkit or component package to the latest version using the following instructions:

• Toolkit: {yum|dnf} upgrade <toolkit package>
  For example, to upgrade the Intel oneAPI Base Toolkit package to the latest version, use the following command:

  # YUM:
  yum upgrade intel-basekit
  
  # DNF:
  dnf upgrade intel-basekit

   

• Component: {yum|dnf} upgrade <component package>
  For example, to upgrade the Intel Distribution for GDB* package, use the following command:

  # YUM:
  yum upgrade intel-oneapi-dpcpp-debugger
  
  # DNF:
  dnf upgrade intel-oneapi-dpcpp-debugger

   

Install Intel GPU Drivers

If you are using a discrete Intel GPU, you will need to install the latest drivers because they are not included in oneAPI toolkit installation package.

• Driver installation instructions

Disable Hangcheck

This section applies only to applications with long-running GPU compute workloads in native environments. Not recommended for virtualizations or other standard usages of GPU, such as gaming.

A workload that takes more than four seconds for GPU hardware to execute is a long running workload. By default, individual threads that qualify as long-running workloads are considered hung and are terminated. Disabling the hangcheck timeout period avoids this problem.

Note: If the system is rebooted, hangcheck is automatically enabled. You must disable hangcheck again after every reboot or follow the directions below to disable hangcheck persistently (across multiple reboots).

To disable hangcheck until the next reboot:

sudo sh -c "echo N> /sys/module/i915/parameters/enable_hangcheck"

To disable hangcheck across multiple reboots:

1. Open a terminal and run this command:

   Append i915.enable_hangcheck=0 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub
   Run sudo update-grub
   

    

2. Reboot the system. Hangcheck will remain disabled.

Appendix: Listing Available Toolkits, Components, and Runtime Library Packages

Use the queries provided below to find and install specific toolkits, standalone components, standalone runtime library packages, or simply to see all available packages in oneAPI repository.

List Toolkit Packages

To query the YUM (DNF) repository for available toolkit packages, use the following command:

# YUM:
sudo -E yum --disablerepo="*" --enablerepo="oneAPI" list available | grep kit | grep -v runtime

# DNF:
sudo -E dnf --disablerepo="*" --enablerepo="oneAPI" list available | grep kit | grep -v runtime

List Standalone Components

The oneAPI repository also contains standalone components, which are packages that provide a specific tool for cases where you do not need an entire toolkit. For these packages, if there is a <component>-runtime package, make sure to get and install both the component package and its runtime package. Not all standalone components need an additional runtime package. If you do not see a runtime package for your standalone component, then you do not need one. 
To query the YUM (DNF) repository for available standalone components and their runtime packages, use the following command:

# YUM:
sudo -E yum --disablerepo="*" --enablerepo="oneAPI" list available | grep intel-oneapi | grep -v intel-oneapi-runtime

# DNF:
sudo -E dnf --disablerepo="*" --enablerepo="oneAPI" list available | grep intel-oneapi | grep -v intel-oneapi-runtime

List Standalone Runtime Library Packages

The oneAPI repository provides standalone runtime library packages. These packages can be installed on systems that will host oneAPI applications: hosts where you do not want to install the oneAPI development toolkits. These are hosts where you run applications but do not do development, compilation, or runtime profiling. In this case, you only need the shared libraries dynamically linked to by executables, provided by these packages.   
To query the YUM repository for available component runtime libraries, use the following command:

# YUM:
sudo -E yum --disablerepo="*" --enablerepo="oneAPI" list available | grep intel-oneapi-runtime

# DNF:
sudo -E dnf --disablerepo="*" --enablerepo="oneAPI" list available | grep intel-oneapi-runtime

List All Packages

To query all available Intel® oneAPI packages provided in the repository, use the following command:

# YUM:
sudo -E yum --disablerepo="*" --enablerepo="oneAPI" list available

# DNF:
sudo -E dnf --disablerepo="*" --enablerepo="oneAPI" list available

Have Questions?

Check out the FAQ
See our Get Help page for your support options.

Notices and Disclaimers

Intel technologies may require enabled hardware, software or service activation.

No product or component can be absolutely secure.

Your costs and results may vary.

© Intel Corporation. Intel, the Intel logo, and other Intel marks are trademarks of Intel Corporation or its subsidiaries. Other names and brands may be claimed as the property of others.

No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document.

The products described may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request.

Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.