当文件位于正确路径时，dlopen 失败并找不到文件
我有一个使用 libtool 构建的库，它安装到包的库目录 /usr/local/lib/myprog/libmylib.so 中。我使用 libltdl 在代码中动态加载该库。当我尝试在一台机器上加载这个库时，它工作得很好。另一方面，在相同的版本和安装在同一位置的库的情况下，我收到“文件未找到”错误。
如果我直接在 lt_dlopenext （我用来加载库）之前调用 lt_dlforeachfile ，那么我可以通过打印文件名来看到我需要的库已在搜索中找到小路。但紧接着，加载失败并出现“文件未找到”错误。有什么建议吗？
更新
我尝试切换到使用dlopen并显式指定库的绝对路径。这在某些系统上仍然有效，但在其他系统上则无效。
I have a library built using libtool which is install into the package's library directory, /usr/local/lib/myprog/libmylib.so. I'm dynamically loading the library in my code with libltdl. When I try to load this library on one machine, it works just fine. On another, with the same build and the library installed on the same location, I get a "file not found" error.
If I call lt_dlforeachfile directly before lt_dlopenext (which I use to load the library), then I can see by printing out filenames that the library I need has been found in the search path. But then immediately after, loading it fails with a "file not found" error. Any suggestions?
UPDATE
I have tried switching to using dlopen and explicitly specifying the absolute path to the library. This still works on some systems and not on the other.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
事实证明 libltdl 隐藏了真正的错误。 “找不到文件”来自我正在加载的库所依赖的另一个库。我在使用 dlerror() 打印错误消息时发现了这一点。安装缺少的库后，一切都很好！
It turned out that libltdl was hiding the real error. the "file not found" was from another library that the library I was loading depended on. I discovered this when using
dlerror()to print the error messages. After installing the missing library, all is well!