IntelOneapi¶
Spack can install and use the Intel oneAPI products. You may either use Spack to install the oneAPI tools or use the Intel installers. After installation, you may use the tools directly, or use Spack to build packages with the tools.
The Spack Python class IntelOneapiPackage is a base class that is used by IntelOneapiCompilers, IntelOneapiMkl, IntelOneapiTbb and other classes to implement the oneAPI packages.
Search for oneAPI at packages.spack.io for the full list of available oneAPI packages, or use:
$ spack list -d oneAPI
For more information on a specific package, do:
$ spack info --all <package-name>
Building a Package With icx¶
In this example, we build patchelf with icc and icx.
The compilers are installed with Spack.
Install the oneAPI compilers:
$ spack install intel-oneapi-compilers
To build the patchelf Spack package with icx, do:
$ spack install patchelf%oneapi
Using oneAPI Spack environment¶
In this example, we build LAMMPS with icx using Spack environment for oneAPI packages created by Intel.
The compilers are installed with Spack like in example above.
Install the oneAPI compilers:
$ spack install intel-oneapi-compilers
Clone spack-configs repo and activate Intel oneAPI CPU environment:
$ git clone https://github.com/spack/spack-configs
$ spack env activate spack-configs/INTEL/CPU
$ spack concretize -f
Intel oneAPI CPU environment contains applications tested and validated by Intel. This list is constantly extended. Currently, it supports:
To build LAMMPS with oneAPI compiler from this environment just run:
$ spack install lammps
Compiled binaries can be found using:
$ spack cd -i lammps
You can do the same for all other applications from this environment.
Using oneAPI MPI to Satisfy a Virtual Dependence¶
The hdf5 package works with any compatible MPI implementation.
To build hdf5 with Intel oneAPI MPI do:
$ spack install hdf5 +mpi ^intel-oneapi-mpi
Using Externally Installed oneAPI Tools¶
Spack can also use oneAPI tools that are manually installed with Intel Installers. The procedures for configuring Spack to use external compilers and libraries are different.
Compilers¶
To use the compilers, add some information about the installation to packages.yaml.
For most users, it is sufficient to do:
$ spack compiler add /opt/intel/oneapi/compiler/latest/bin
Adapt the paths above if you did not install the tools in the default location.
After adding the compilers, using them is the same as if you had installed the intel-oneapi-compilers package.
Another option is to manually add the configuration to packages.yaml as described in Compiler configuration.
Before 2024, the directory structure was different:
$ spack compiler add /opt/intel/oneapi/compiler/latest/linux/bin/intel64
$ spack compiler add /opt/intel/oneapi/compiler/latest/linux/bin
Libraries¶
If you want Spack to use oneMKL that you have installed without Spack in the default location, then add the following to ~/.spack/packages.yaml, adjusting the version as appropriate:
intel-oneapi-mkl:
externals:
- spec: intel-oneapi-mkl@2021.1.1
prefix: /opt/intel/oneapi/
Using oneAPI Tools Installed by Spack¶
Spack can be a convenient way to install and configure compilers and libraries, even if you do not intend to build a Spack package. If you want to build a Makefile project using Spack-installed oneAPI compilers, then use Spack to configure your environment:
$ spack load intel-oneapi-compilers
And then you can build with:
$ CXX=icpx make
You can also use Spack-installed libraries. For example:
$ spack load intel-oneapi-mkl
This updates your environment CPATH, LIBRARY_PATH, and other environment variables for building an application with oneMKL.