Import of libdl failing with newer libc
See original GitHub issueThere are various DllImport("libdl")
directives in this repository, however versions of glibc since 2.3.4 have removed libdl as a shared object (i.e. they no longer provide a libdl.so
), which causes this to fail to load.
Notes from glibc 2.3.4: https://sourceware.org/pipermail/libc-alpha/2021-August/129718.html
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top Results From Across the Web
apt - Unable to load shared library 'libdl.so' or one of its ...
I'm trying to compile a project and the compilation fails due to a missing library. ... I've been searching for known solutions in...
Read more >Importing Python module from .so file fails on target system ...
Assume that I cannot globally install a newer GLIBC version on the target system, nor install GCC 4.9 and compile the C++ libraries...
Read more >Program won't run because of small difference in version ...
I have a program that I compiled on one x64 (Ubuntu) system that won't run on another x64 (Debian) system. I'd like to...
Read more >apt-get upgrade failure with libc
First of all go here /lib/x86_64-linux-gnu move these files to /root : libc-2.17.so libdl-2.17.so libm-2.17.so libpthread-2.17.so ...
Read more >Solving The “Cannot Open Shared Object File: No Such ...
Learn what causes the "cannot open shared object file: No such file or directory" error in Linux, and how to fix it.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m afraid that I’m not able to comment on the solution here as I haven’t seen it in operation. I think an alternative was to wrap the load such that if it threw an exception then it could be caught and another attempt to load from a different DLL (libc) could be attempted, but I’m not sure of the relative merits of the two approaches.
fwiw; I was facing this issue and after upgrading from 7.4.x to 7.5.x it’s working again. Thanks !