libgit2 / libgit2/libgit2sharp
NativeMethods. Version GLIBC_2.25' not found
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
Description
Hi!
I test my LibGit2Sharp application on old Linux platform and stuck with error, after some research i execute ldd command inside terminal:
ldd libgit2-a418d9d.so
Output:
version GLIBC_2.25' not found (required by /usr/lib/versioncontrol/libgit2-a418d9d.so)
It seems that this is the real cause of the load DLL error.
How can I embed this dependency directly into the application so that it doesn't try to look for it in the system?
Currently, GLIBC_2.24 is installed on the machine. Updating GLIBC to a newer version, like 2.25, is not possible due to company policies.
Reproduction steps
Start application and execute "pull" command through LibGit2Sharp.
Expected behavior
Execute of "pull" command successfully finished.
Actual behavior
Error on application "Pull" command:
The type initializer for 'LibGit2Sharp.Core.NativeMethods' threw an exception.
InnerException = {"Unable to load DLL 'git2-a418d9d' or one of its dependencies: }
Version of LibGit2Sharp (release number or SHA1)
0.30.0
Operating system(s) tested; .NET runtime tested
Astra Linux 1.6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the pull command failure on Astra Linux 1.6 with LibGit2Sharp 0.30.0, then inspect the ldd output for libgit2-a418d9d.so and the NativeMethods type-initializer exception. Determine whether the GLIBC_2.25 dependency can be addressed within the application; done means the pull command completes on a system with GLIBC_2.24 without the DLL load error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100