Repository navigation
Conversation
Builds clangd (jmpfar/clangd-wheel), the LSP server bundled from a from-source LLVM+clang+clang-tools-extra compile, modeled on build-clang-tidy.yml (same scikit-build-core + cibuildwheel + manylinux_riscv64 lineage: clangd-wheel is a fork of clang-tidy-wheel). Preemptively installs lld and caps CMAKE_BUILD_PARALLEL_LEVEL, since build-circt.yml already hit this runner's RAM ceiling linking an unrestricted-LLVM-target binary and clangd-wheel's own CMakeLists.txt leaves LLVM_TARGETS_TO_BUILD at upstream's default (all targets) too.
|
|
The first build of 22.1.1 failed in get_requires_for_build_wheel with "Use build.verbose instead of cmake.verbose for scikit-build-core >= 0.10". clangd-wheel leaves scikit-build-core unpinned and still sets the deprecated cmake.verbose; 0.12.x (what upstream last released 22.1.1 with, in March) only warned about it, but 1.x errors out when minimum-version is unset, so build isolation now resolves 1.1.1 and the build stops before CMake runs. This is not riscv64-specific: any fresh build of the tag hits it. Carry a one-line pyproject.toml patch and apply it before cibuildwheel, checking python-wheels out alongside the upstream tree as the other patched workflows do.
|
The build stopped at cibuildwheel's "Getting build dependencies for wheel..." step, before CMake ran: Root cause. At
So this isn't specific to riscv64: a fresh build of this tag fails the same way on every platform today. I reproduced it locally against
Fix (ede3084).
With the patch applied and scikit-build-core 1.1.1, |
clangd22.1.1Compiles clangd (LLVM/clang/clang-tools-extra) from the official LLVM source release; clangd-wheel always builds it from source regardless of platform. Upstream publishes no riscv64 wheel.
Mirrors upstream's
build.yml.Differs from upstream
CMAKE_BUILD_PARALLEL_LEVEL- build-circt.yml OOM'd linking an unrestricted-target LLVM binary on this runnerTesting
License: OK
Built on cp312 (py2.py3); CI pending.