Registry / data / intel-cmplr-lib-rt

intel-cmplr-lib-rt

library2025.3.3pypypiunverified

The `intel-cmplr-lib-rt` package provides shared common runtime libraries essential for deploying executables compiled with Intel® oneAPI development Toolkits on systems without the full toolkits installed. It is a low-level runtime component, not a Python library with a direct Python API. Its current version is 2025.3.3, with releases generally tied to Intel oneAPI toolkit updates.

data

pip install intel-cmplr-lib-rt

package ↗homepage ↗

INSTALL

IMPORT

SIG · INTEL-CMPLR-LIB-RT

intel-cmplr-lib-rt

datapythonv2025.3.3

harness data pending

Install & Compatibility

Where this runs

No compatibility data collected yet for this library.

Code

Verified usage

The `intel-cmplr-lib-rt` library does not offer a direct Python API for application development. It serves as a runtime dependency for executables, particularly those compiled with Intel's C++ or DPC++ compilers. Its inclusion in a Python environment usually signifies that a higher-level Python package depends on the underlying Intel runtime components. The `quickstart.code` block above illustrates how it might be used in a C++ compilation and execution flow, emphasizing the critical role of environment variables for linking and runtime library discovery.

# The intel-cmplr-lib-rt package does not expose a direct Python API for end-user applications. # It provides runtime components primarily for executables compiled with Intel C++ or DPC++ compilers. # Its presence in a Python environment is typically as a dependency for other Python packages # that wrap or utilize Intel-compiled native code (e.g., Intel Extension for PyTorch). # There are no standard Python import statements or direct usage patterns for this library. # For C++ applications, linking and runtime environment setup are crucial: # For compilation (example, requires Intel C++ compiler environment): # export LIBRARY_PATH=/path/to/intel/oneapi/compiler/latest/lib:$LIBRARY_PATH # icpx -o my_app my_app.cpp -L/path/to/intel/oneapi/compiler/latest/lib -lintel-cmplr-lib-rt # For execution, ensure runtime libraries are discoverable: # export LD_LIBRARY_PATH=/path/to/intel/oneapi/compiler/latest/lib:$LD_LIBRARY_PATH # ./my_app

Debug

Known issues

gotchaThis library does not provide a direct Python API. It is a collection of native runtime libraries for executables compiled with Intel oneAPI compilers. Expecting Python-level imports or functionality will lead to confusion.

fix

Understand its purpose as a runtime dependency for compiled code, not a Python-callable library. Its Python package exists for dependency management within Python ecosystems that leverage Intel-optimized native binaries.

affects: All versions

gotchaProper environment variable setup (e.g., `LD_LIBRARY_PATH` on Linux, `PATH` on Windows) is crucial for applications to find these runtime libraries at execution. Failing to set these can result in 'library not found' errors, even if the package is installed via pip.

fix

Ensure that the directories containing the Intel runtime libraries are correctly added to the system's dynamic linker search paths (`LD_LIBRARY_PATH` or `PATH`) before running applications that depend on them. Intel oneAPI's `setvars.sh` (or `.bat`) scripts typically handle this.

affects: All versions

breakingBreaking changes in the underlying Intel compilers or oneAPI toolkits (e.g., deprecated compiler flags, removal of support for older hardware like Intel Xeon Phi) can indirectly affect executables that depend on `intel-cmplr-lib-rt`. Users might encounter issues if their applications were built with older compiler versions or target deprecated hardware features.

fix

Refer to the release notes for the specific Intel oneAPI compiler used to build the dependent application. Recompile applications with newer compilers and adjust flags or code as necessary to align with current best practices and supported features.

affects: 2025.x and newer (e.g., removal of -fsycl-link-huge-device-code in 2025.3.3)

gotchaThis package is often a component of a larger Intel oneAPI installation. For a complete and correctly configured runtime environment, it should typically be installed alongside `intel-cmplr-lic-rt` and one or more compiler-specific runtime packages (e.g., `intel-sycl-rt`). Missing these companion packages can lead to incomplete runtime environments.

fix

Ensure all necessary Intel oneAPI runtime components are installed. When using `pip`, consider the dependency requirements of higher-level packages (like `intel-extension-for-pytorch`) which might explicitly list these associated runtime dependencies.

affects: All versions

Errors

Common errors & fixes

error while loading shared libraries: <library_name>.so: cannot open shared object file: No such file or directory

The system's dynamic linker cannot find one of the required Intel runtime shared libraries (e.g., libimf.so, libsvml.so, libintlc.so.5) at execution time on Linux.

fix

Ensure the Intel oneAPI runtime libraries are installed; then, source the `setvars.sh` script from your Intel oneAPI installation (e.g., `source /opt/intel/oneapi/setvars.sh`) or manually add the directory containing the missing `.so` file to the `LD_LIBRARY_PATH` environment variable. If the library is missing entirely, install the appropriate Intel oneAPI runtime package (e.g., `intel-oneapi-runtime-libs`).

missing DLL (libmmd.dll)

On Windows, applications compiled with Intel compilers require specific Intel runtime DLLs which are not found in the system's `PATH` environment variable or the application's directory.

fix

Run the `setvars.bat` script from your Intel oneAPI installation before executing the application, or manually add the directory containing the Intel runtime DLLs (e.g., `C:\Program Files (x86)\Intel\oneAPI\compiler\<version>\redist\intel64_win\compiler`) to your system's `PATH` environment variable.

undefined reference to `__some_symbol`

During compilation, the linker cannot find the definition for a required symbol because the necessary Intel runtime library (e.g., from intel-cmplr-lib-rt) is not included in the linking command or its path is not specified.

fix

Ensure that you are linking against the correct Intel runtime libraries (e.g., `-limf`, `-lsvml`, `-lintlc`) and that the compiler's environment is properly sourced (e.g., `source setvars.sh` on Linux, `setvars.bat` on Windows) before compilation and linking. You might also need to explicitly add library paths using `-L` and specify libraries with `-l` in your build command.

ERROR: Cannot install <package_A> and <package_B> because these package versions have conflicting dependencies. The conflict is caused by: <package_X> depends on intel-cmplr-lib-rt==X.Y.Z <package_Y> depends on intel-cmplr-lib-rt==A.B.C

When installing Python packages that rely on `intel-cmplr-lib-rt` via pip, a version conflict occurs because different dependent packages require incompatible versions of `intel-cmplr-lib-rt`.

fix

Attempt to loosen the version constraints of the conflicting packages if possible, or try to find a combination of package versions that are mutually compatible. This often involves installing a specific version of `intel-cmplr-lib-rt` that satisfies all dependencies, or using a specific PyPI index (e.g., `pip install --index-url https://pypi.anaconda.org/intel/simple ...`).

Upgrade

Version history

2025.3.3latest on PyPI · released Mar 24, 2026

Audit

Dependencies

intel-cmplr-lic-rtrequiredRequired for third-party program files and EULA; typically installed alongside common libraries.

compiler-specific runtimesrequiredOften needs one or more compiler-specific runtime packages depending on the compiled application's origin (e.g., `intel-sycl-rt`, `dpcpp-cpp-rt`).

Agent activity

8 hits · last 30 days

node

Resources

packagehttps://pypi.org/project/intel-cmplr-lib-rt/ ↗

homepagehttps://www.intel.com/content/www/us/en/developer/tools/oneapi/base-toolkit.html ↗