-
Epic
-
Resolution: Done
-
Undefined
-
None
-
llvmlite: use static linking for llvm-libs
-
False
-
-
False
-
Done
-
0% To Do, 0% In Progress, 100% Done
Our llvmlite downstream builds are dynamically linked with libLLVM-14.so from llvm14-libs package. llvm14-libs has to be installed in all applications images and our internal LLVM 14 builds are exposed.
Upstream llvmlite uses static linking to avoid runtime dependencies on libLLVM. We should also use static linking. This will allow us to make LLVM 14 / 15 an internal, builder-only package.
- patch https://github.com/numba/llvmlite/blob/v0.43.0/ffi/build.py#L184 to run "llvm-config-14" with option "--link-static".
- verify that the new wheel does not have runtime dependency on libLLVM.
- update runtime images and applications images to no longer install "llvm14-libs"
- work with upstream to add an option to force static / dynamic linking, see https://github.com/numba/llvmlite/issues/1027 for more information. Perhaps add "-
link-shared" when env var "LLVMLITE_SHARED" is set, otherwise add "-link-static".
We can either do this now or wait until we can build llvmlite 0.44 with LLVM 15.
- is related to
-
RHELAI-3073 Constrain numba and llvmite for requirements-pipeline
-
- Closed
-