evso98
August 18, 2025, 5:02am
1
I wanted to install llvmlite locally based on an existing llvm 20. I used the following: LLVM_CONFIG=/usr/lib/llvm-20/bin/llvm-config CXXFLAGS=-fPIC LLVMLITE_SKIP_LLVM_VERSION_CHECK=1 pip3 install --no-binary :all: llvmlite
As error: Building wheel for llvmlite (pyproject.toml) … error
error: subprocess-exited-with-error
Building wheel for llvmlite (pyproject.toml) did not run successfully.
I also used unsuccessfully the following PR: GitHub - yashssh/llvmlite at yashwants/llvm19
Any hint?
esc
August 18, 2025, 8:58am
2
llvmlite via main is currently not compatible with LLVM 20.
This is being worked on and should become available with the next release of llvmlite– you can track the release candidate here:
opened 02:35PM - 11 Aug 25 UTC
Task
## llvmlite 0.45.0-rc1
* [ ] Merge to `main`.
* [ ] "remaining Pull-Request… s from milestone": https://github.com/numba/llvmlite/milestone/27
* In case of an LLVM upgrade:
* [ ] Check if the compatability matrix in the `README.rst` needs updating.
* [ ] Check if the inter-sphinx link in `llvmlite/docs/source/conf.py`
needs an update.
* [ ] produce suitable `llvmdev` packages for all architectures
* [ ] Create X.Y release branch `release0.45`
* [ ] Update `CHANGE_LOG` in a PR targeting the release branch.
* [ ] Follow the format of previous `CHANGE_LOG` entries.
* [ ] Get the change-log-PR reviewed and merged.
* [ ] Test `HEAD` of release branch on buildfarm (pre-tag testing):
* [ ] conda package build and test.
* [ ] wheel build.
* [ ] Test `HEAD` of release branch on conda-forge
* [ ] Annotated tag `v0.45.0-rc1` on release branch (`llvmlite` tags DO have a `v` prefix).
* [ ] Build and upload conda packages on buildfarm (check "upload").
* [ ] Build wheels and sdist on the buildfarm (check "upload").
* [ ] Verify packages uploaded to Anaconda Cloud and copy to `numba/label/main`.
* [ ] Upload wheels and sdist to PyPI. (upload from `ci_artifacts`).
* [ ] Verify wheels for all platforms arrived on PyPi.
* [ ] Initialize and verify ReadTheDocs build.
* [ ] Send RC announcement email / post announcement to discourse group.
* [ ] Post link to X and Mastodon and anywhere else that is appropriate.
### Post Release:
* [ ] Clean up `ci_artifacts` by moving files to subdirectories
* [ ] Tag 0.46.0dev0 to start new development cycle on `main`.
* [ ] Update release checklist template with any additional bullet points that
may have arisen during the release.
* [ ] Close milestone (and then close this release issue).
1 Like