We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, Team,
I try to run seafowl under CentOS 8-Stream lab environment but failed.
[root@seafowl-single ~]# cat /etc/*release CentOS Stream release 8 NAME="CentOS Stream" VERSION="8" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="8" PLATFORM_ID="platform:el8" PRETTY_NAME="CentOS Stream 8" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:8" HOME_URL="https://centos.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 8" REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream" CentOS Stream release 8 CentOS Stream release 8 [root@seafowl-single ~]# tar -xvf seafowl-v0.5.7-x86_64-unknown-linux-gnu.tar.gz seafowl [root@seafowl-single ~]# chmod +x ./seafowl [root@seafowl-single ~]# ./seafowl --version ./seafowl: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by ./seafowl) [root@seafowl-single ~]#
It seems that for RHEL series, only RHEL 9.x provides glibc that can satisfy the ABI requirement of the current build.
glibc
Is it possible to make seafowl to support RHEL 8 series (i.e. glibc-v2.28)? Or this is an official support OS version requirement (glibc >= v2.29)?
Best Regards.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi, Team,
I try to run seafowl under CentOS 8-Stream lab environment but failed.
It seems that for RHEL series, only RHEL 9.x provides
glibc
that can satisfy the ABI requirement of the current build.Is it possible to make seafowl to support RHEL 8 series (i.e. glibc-v2.28)?
Or this is an official support OS version requirement (glibc >= v2.29)?
Best Regards.
The text was updated successfully, but these errors were encountered: