Open
Description
We're running into glibc linking errors for Alloy on RHEL 8, after updating from 1.3.1 to 1.9.2. Here are the details of the issue I've been able to dig up:
- The glibc version that RHEL 8 supports is 2.28. (reference)
- Applications compiled linking glibc 2.28 should be compatible with later glibc versions.
- Recent versions of Alloy on Linux require CGo to be enabled, as it is required by godror, so building without CGo enabled results in build failures for godror. (reference)
- The alloy-build-image available on DockerHub is built upon on Debian Bullseye, which ships with glibc 2.31. (
cat /etc/-os-release
from within running container)
While updating glibc is technically an option generally, it is not an option in our case.
Is there a recommended way to build the latest version(s) of Alloy so that they are compatible with glibc 2.28?
Metadata
Metadata
Assignees
Labels
No labels