KushShriv opened a new pull request, #12757:
URL: https://github.com/apache/gluten/pull/12757

   ## What changes are proposed in this pull request?
   Fixes #12412 (1)
   
   CentOS 7 (glibc 2.17) is increasingly difficult to maintain as a vcpkg build 
base due to Velox's growing dependency on modern Folly/FBThrift/MVFST versions. 
This PR adds the AlmaLinux 8 (glibc 2.28) Docker image — a 1:1 RHEL 
8-compatible rebuild of the EOL CentOS 8 — as the new vcpkg static build base, 
in preparation for migrating the x86/arm native lib CI jobs.
   
   Add AlmaLinux 8 vcpkg static build CI image:
   
   - Add `dev/docker/Dockerfile.almalinux8-gcc13-static-build` to produce 
`apache/gluten:vcpkg-almalinux-8-gcc13`, modelled on the existing 
`Dockerfile.centos7-gcc13-static-build`. 
   Uses `FROM almalinux:8` (live repos, no mirror fixups needed) with GCC 13 
via `gcc-toolset-13` and a pinned CMake 3.31.12.
   - Add dev/ci-velox-buildstatic-centos-8-enhanced-features.sh — the CentOS 8 
equivalent of the existing ci-velox-buildstatic-centos-7-enhanced-features.sh, 
omitting the socket.h workaround required on CentOS 7.
   - Add build-vcpkg-almalinux-8-gcc13 and merge-almalinux-8-gcc13 jobs to 
docker_image.yml to build and publish the multi-arch image.
   
   ## How was this patch tested?
   The Dockerfile.almalinux8-gcc13-static-build follows the same structure as 
the existing Dockerfile.centos8-gcc13-static-build. The docker_image.yml 
workflow will publish the image to Docker Hub on merge.
   
   ## Was this patch authored or co-authored using generative AI tooling?
   Generated-by: Claude Sonnet 4.5


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to