Workaround for build failures when glibc version is lower than 2.26#217
Open
cuzperf wants to merge 1 commit into
Open
Workaround for build failures when glibc version is lower than 2.26#217cuzperf wants to merge 1 commit into
cuzperf wants to merge 1 commit into
Conversation
Author
|
I also test in Debian12 with glibc2.36 which workfine. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While watching tsoding's YouTube channel, I noticed that he uses a tool called
gfand found its debugging interface quite impressive. So I tried it on an old CentOS 7.9 system, but encountered the following error, which I then attempted to fix.