yihua opened a new pull request, #757:
URL: https://github.com/apache/hudi-rs/pull/757
## Description
closes #756
Stacked on #751, review that one first; this branch shows its commits until
it merges. Targeting 0.6.0: the 0.5.0 release ships from `manylinux2014` via
#751, so the wheel floor does not change mid-release.
The 2014 (CentOS 7) base predates every native toolchain need this project
has grown: its protoc is 2.5.0, it carries no libclang, and the newest clang
its software collections offer is LLVM 7, which bindgen only tolerates with the
library path and builtin-header include handed over explicitly. On the 2_28
(AlmaLinux 8) base the distro `clang-devel` is clang 21 and bindgen needs
nothing handed in, so the dependency script shrinks to a `dnf install` plus the
pinned protoc download (the 8.x distro protoc is 3.5, still older than
prost-build needs), and the aarch64 `-D__ARM_ARCH=8` ring workaround goes away,
as its own comment promised.
The trade is the wheel floor moving from glibc 2.17 to 2.28, which drops
CentOS 7, Ubuntu 18.04, and Amazon Linux 2, all past end of life. In practice
nothing is lost: pyarrow, numpy, and the datafusion python package, the
packages hudi wheels run alongside, ship `manylinux_2_28` wheels only, so any
environment the new floor excludes already cannot install the surrounding
stack. Worth a line in the 0.6.0 release notes all the same.
## How are the changes test-covered
- [ ] N/A
- [x] Automated tests (unit and/or integration tests)
- [x] Manual tests
- [x] Details are described below
The `manylinux-wheel-build` CI job from #751 builds both targets in the
container this change pins, so the switch is exercised on this PR.
Manually, in `quay.io/pypa/manylinux_2_28` with the new script and no CFLAGS
workaround:
| step | result |
| --- | --- |
| distro `clang-devel` | clang 21.1.8, `/usr/lib64/libclang.so` present |
| pinned protoc, sha256 verified | `libprotoc 36.1` |
| `cargo build` of `lance-encoding` 11.0.0, `librocksdb-sys` 0.16.0, `ring`
0.17.14 | finished, exit 0 |
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
