Skip to content
New issue

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

GLIBC 2.18 requirement causes incompatibility with CentOS 7 #34

Closed
sfc-gh-pbennes opened this issue Aug 16, 2022 · 3 comments · Fixed by #38
Closed

GLIBC 2.18 requirement causes incompatibility with CentOS 7 #34

sfc-gh-pbennes opened this issue Aug 16, 2022 · 3 comments · Fixed by #38
Assignees

Comments

@sfc-gh-pbennes
Copy link

Greetings!

It appears that the Linux build of ripgrep for VSCode is happening in an environment with GLIBC 2.18. This results in a binary incompatible with operating systems with a lower GLIBC version. CentOS 7 ships with GLIBC 2.17 and is one such incompatible OS.

This causes issues with vscode features that rely on ripgrep funcitonality: microsoft/vscode-remote-release#6930. Specifically microsoft/vscode-remote-release#6930 (comment).

Can the build be moved to an environment with a GLIBC version 2.17 or lower to support CentOS 7?

@chrmarti
Copy link

@roblourens https://stackoverflow.com/a/47239631/7857763 suggests to use an older Rust toolchain that only supports GLIBC 2.17. (We currently list GLIBC 2.17 and CentOS 7 as supported in https://code.visualstudio.com/docs/supporting/requirements.)

@mshijie
Copy link

mshijie commented Mar 8, 2023

I was wondering if there have been any developments on this issue.

@andreamah
Copy link
Contributor

I was wondering if there have been any developments on this issue.

Yup! I'm currently trying to get a new build of ripgrep-prebuilt so that I can release a new vscode-ripgrep with some fixes to remove the GLIBC requirement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants