转自:http://my.oschina.net/moooofly/blog/506466

问题场景:

  1. 动态库 librabbitmq_r.so 内部依赖动态库 libevent_core.so 和 libevent_pthreads.so ;
  2. 可执行程序 sa 依赖动态库 librabbitmq_r.so ;
  3. 在链接生成 sa 的时候希望只指定 librabbitmq_r.so 而不指定 libevent_core.so 和 libevent_pthreads.so 。

错误信息:

...
g++ ../source/authorisecfg.o ../source/bmcinst.o ../source/config.o ../source/lgsinst.o ../source/logicsrv.o ../source/logicsrvinst.o ../source/logicsrvmodulelistcfg.o ../source/main.o ../source/moduleinst.o ../source/print.o ../source/routingkeycfg.o ../source/sautils.o ../source/structself.o ../source/../../../common/source/bossutils.o
../source/../../../common/source/bossversion.o -o sa -m32 -L../../../../-common/lib/release/linux -lrt -lwatchdogclient -lfiletransfer -losp -lkprop -ljsonconvert -ljsoncpp -ldeploycfg -lnosectionini -lrabbitmq_r -lmqwrapper -lreadwritelock -lcaptureexception -lnetconfig /usr/bin/ld: warning: libevent_core.so, needed by ../../../../-common/lib/release/linux/librabbitmq_r.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libevent_pthreads.so, needed by ../../../../-common/lib/release/linux/librabbitmq_r.so, not found (try using -rpath or -rpath-link) ../../../../-common/lib/release/linux/librabbitmq_r.so: undefined reference to `event_base_free'
../../../../-common/lib/release/linux/librabbitmq_r.so: undefined reference to `evthread_use_pthreads'
../../../../-common/lib/release/linux/librabbitmq_r.so: undefined reference to `event_assign'
../../../../-common/lib/release/linux/librabbitmq_r.so: undefined reference to `event_base_dispatch'
../../../../-common/lib/release/linux/librabbitmq_r.so: undefined reference to `event_base_loopbreak'
../../../../-common/lib/release/linux/librabbitmq_r.so: undefined reference to `event_del'
../../../../-common/lib/release/linux/librabbitmq_r.so: undefined reference to `event_add'
../../../../-common/lib/release/linux/librabbitmq_r.so: undefined reference to `event_base_new'
collect2: ld returned exit status
make: *** [sa] Error

由错误信息可以看出,未找到的符号均属于 libevent_core.so 和 libevent_pthreads.so 内部。但这两个库确实存在于 -L../../../../10-common/lib/release/linux 路径下,但为什么链接器仍旧无法找到对应的库和符号呢?

下面的文章讨论了这个问题(下面给出部分摘录)

Why does ld need -rpath-link when linking an executable against a so that needs another so?

...


You
system, through ld.so.conf, ld.so.conf.d, and the system environment,
LD_LIBRARY_PATH, etc.., provides the system-wide library search paths
which are supplemented by installed libraries through pkg-config
information and the like when you build against standard libraries. 



...


There
is no standard run-time library search path for custom shared libraries
you create yourself. You specify the search path to your libraries
through the -L/path/to/lib designation during compile and link. For
libraries in non-standard locations, the library search path can be
optionally placed in the header of your executable (ELF header) at
compile-time so that your executable can find the needed libraries.



...


rpath
provides a way of embedding your custom run-time library search path in
the ELF header so that your custom libraries can be found as well
without having to specify the search path each time it is used. This
applies to libraries that depend on libraries as well. As you have
found, not only is the order you specify the libraries on the command
line important, you also must provide the run-time library search path,
or rpath, information for each dependent library you are linking against
as well so that the header contains the location of all libraries
needed to run.



...


back
to the semantics of ld. In order to produce a "good link", ld must be
able to locate all dependent libraries. ld cannot insure a good link
otherwise. The runtime linker must find and load, not just to find the
shared libraries needed by a program. ld cannot guarantee that will
happen unless ld itself can locate all needed shared libraries at the
time the progam is linked.



...

结论就是,像这种 a.so 依赖 b.so ,而 c 依赖 a.so 的情况,在链接过程中需要通过 -rpath-link 指定所需 .so 的位置,而不能仅仅使用 -L 指定。

示例如下:

[root@Betty include_test]# ll
总用量
-rw-r--r-- root root 9月 : main.c
-rw-r--r-- root root 9月 : say_hello.c
-rw-r--r-- root root 9月 : say_hello.h
-rw-r--r-- root root 9月 : time_print.c
-rw-r--r-- root root 9月 : time_print.h
[root@Betty include_test]#

【say_hello.c】

// g++ -o say_hello.so -fpic -shared say_hello.c

#include <stdio.h>
void say_hello()
{
printf( "Hello World!\n" );
}

【say_hello.h】

void say_hello();

【time_print.c】

// g++ -o time_print.so -fpic -shared -I. -L. time_print.c say_hello.so 

#include <time_print.h>
#include <stdio.h>
#include <say_hello.h> int time_print( time_t tmp )
{
int off = ;
time_t t;
char buf[] = {}; t = time( NULL );
off = strftime( buf, sizeof(buf), "%d %b %H:%M:%S", localtime( &t ) );
fprintf( stderr, "current timestamp = %s\n", buf ); say_hello(); return ;
}

【time_print.h】

#include <time.h>
int time_print( time_t t );

【main.c 】

// g++ -o main main.c time_print.so -I. -Wl,-rpath-link,.

#include <time_print.h>

int main()
{
time_t t;
time_print( t );
return ;
}

生成两个 .so 库

[root@Betty include_test]# g++ -o say_hello.so -fpic -shared say_hello.c
[root@Betty include_test]# ll
总用量
-rw-r--r-- root root 9月 : main.c
-rw-r--r-- root root 9月 : say_hello.c
-rw-r--r-- root root 9月 : say_hello.h
-rwxr-xr-x root root 9月 : say_hello.so
-rw-r--r-- root root 9月 : time_print.c
-rw-r--r-- root root 9月 : time_print.h
[root@Betty include_test]#
[root@Betty include_test]# g++ -o time_print.so -fpic -shared -I. -L. time_print.c say_hello.so
[root@Betty include_test]# ll
总用量
-rw-r--r-- root root 9月 : main.c
-rw-r--r-- root root 9月 : say_hello.c
-rw-r--r-- root root 9月 : say_hello.h
-rwxr-xr-x root root 9月 : say_hello.so
-rw-r--r-- root root 9月 : time_print.c
-rw-r--r-- root root 9月 : time_print.h
-rwxr-xr-x root root 9月 : time_print.so
[root@Betty include_test]#

若不指定 -rpath-link 选项,则链接失败

[root@Betty include_test]# g++ -o main main.c time_print.so -I. -L.
/usr/bin/ld: warning: say_hello.so, needed by time_print.so, not found (try using -rpath or -rpath-link)
time_print.so: undefined reference to `say_hello()'
collect2: ld 返回
[root@Betty include_test]#

若指定 -rpath-link 选项,则可以成功链接

[root@Betty include_test]# g++ -o main main.c time_print.so -I. -L. -Wl,-rpath-link,.
[root@Betty include_test]# ll
总用量
-rwxr-xr-x root root 9月 : main
-rw-r--r-- root root 9月 : main.c
-rw-r--r-- root root 9月 : say_hello.c
-rw-r--r-- root root 9月 : say_hello.h
-rwxr-xr-x root root 9月 : say_hello.so
-rw-r--r-- root root 9月 : time_print.c
-rw-r--r-- root root 9月 : time_print.h
-rwxr-xr-x root root 9月 : time_print.so
[root@Betty include_test]#

查看一下共享库依赖关系

[root@Betty include_test]# ldd say_hello.so
linux-vdso.so. => (0x00007fffb53ff000)
libstdc++.so. => /usr/lib64/libstdc++.so. (0x00007f56915d4000)
libm.so. => /lib64/libm.so. (0x00007f5691350000)
libgcc_s.so. => /lib64/libgcc_s.so. (0x00007f5691139000)
libc.so. => /lib64/libc.so. (0x00007f5690da5000)
/lib64/ld-linux-x86-.so. (0x000000388c400000)
[root@Betty include_test]#
[root@Betty include_test]# ldd time_print.so
linux-vdso.so. => (0x00007fff50cfa000)
say_hello.so => not found
libstdc++.so. => /usr/lib64/libstdc++.so. (0x00007ff0f7829000)
libm.so. => /lib64/libm.so. (0x00007ff0f75a5000)
libgcc_s.so. => /lib64/libgcc_s.so. (0x00007ff0f738f000)
libc.so. => /lib64/libc.so. (0x00007ff0f6ffa000)
/lib64/ld-linux-x86-.so. (0x000000388c400000)
[root@Betty include_test]#
[root@Betty include_test]# ldd main
linux-vdso.so. => (0x00007fffc55ff000)
time_print.so => not found
libstdc++.so. => /usr/lib64/libstdc++.so. (0x0000003899800000)
libm.so. => /lib64/libm.so. (0x000000388dc00000)
libgcc_s.so. => /lib64/libgcc_s.so. (0x0000003898000000)
libc.so. => /lib64/libc.so. (0x000000388c800000)
/lib64/ld-linux-x86-.so. (0x000000388c400000)
[root@Betty include_test]#

执行程序

[root@Betty include_test]# ./main
./main: error while loading shared libraries: time_print.so: cannot open shared object file: No such file or directory
[root@Betty include_test]#
[root@Betty include_test]# LD_LIBRARY_PATH=. ./main
current timestamp = Sep ::
Hello World!
[root@Betty include_test]#

最后给出一个 rpath 递归问题的讨论: 《Resursive linking with rpath

Linux下共享库嵌套依赖问题 (转载)的更多相关文章

  1. 转:linux下共享库的注意点之-fpic

    转: http://www.cnblogs.com/leo0000/p/5691483.html linux下共享库的注意点之-fpic 在编译共享库必须加上-fpic.这是为什么呢? 首先看一个简单 ...

  2. linux下共享库的注意点之-fpic

    在编译共享库必须加上-fpic.这是为什么呢? 首先看一个简单的例子: #include <stdio.h> int fun1() { printf("fun1\n") ...

  3. linux下静态库和动态库一些东西

    http://www.cnblogs.com/changefuture/archive/2011/12/22/2297460.html Linux  动态链接库和静态库示例 文件预览 文件目录树如下, ...

  4. 谈谈Linux下动态库查找路径的问题 ldconfig LD_LIBRARY_PATH PKG_CONFIG_PATH

    谈谈Linux下动态库查找路径的问题 ldconfig LD_LIBRARY_PATH  PKG_CONFIG_PATH 转载自:http://blog.chinaunix.net/xmlrpc.ph ...

  5. LINUX下动态库及版本号控制

    针对同一动态组件的不同版本链接和加载. 一.概念                  DLL HELL字面意思是DLL"灾难",是由于com组件(动态库)升级引起的程序不能运行的情况 ...

  6. LINUX总结第13篇:LINUX下动态库及版本号控制

    感觉讲得挺详细 注: ln 命令用法 ln –s 源文件 目标文件 (目标文件即为软链接文件) 可用ls -l查看软链接文件具体指向哪个文件 目录[-] 1. File libhello.c 2. F ...

  7. Linux下的库操作工具-nm、ar、ldd、ldconfig和ld.so

    Linux下的库操作工具-nm.ar.ldd.ldconfig和ld.so .nm [options] file 列出file中的所有符号 [option] -c 将符号转化为用户级的名字 -s 当用 ...

  8. 深入理解LINUX下动态库链接器/加载器ld-linux.so.2

    [ld-linux-x86-64.so.2] 最近在Linux 环境下开发,搞了好几天 Compiler 和 linker,觉得有必要来写一篇关于Linux环境下 ld.so的文章了,google上搜 ...

  9. Linux下MiniGUI库的安装

    Linux下MiniGUI库的安装 今天试了下安装MiniGUI的库 先仿照官网的教程安装 传送门:MiniGUI官网 一.配置依赖环境 安装构建工具 apt install binutils aut ...

随机推荐

  1. FALSE_IT

    本文讲一个实用的语法糖(suger),很不错,攻克了我实际工作中的问题. 如果你写了这样一个类: class Executor { int step1(); void step2(); int ste ...

  2. About me --- Connecting the dots

    在这个难以入眠的夜里,乔布斯年在斯坦福的演讲里说的“Connecting the dots”又萦绕耳际,即当我们往回看,就清楚了 自己曾经的生活和现在甚至将来是串联在一起的,这些经历决定了我们事业.生 ...

  3. Active Directory虚拟机搭建域控服务器环境

    前言 还是和上一章一样,痛苦过后还是记录下给后来人提供便利为妙. 虚拟机选择:建议Hyper-V或者VMware 系统选择:建议WIindows Server 2003及以上 我这里是使用VMware ...

  4. 模式匹配之尺度空间---scale space

    转载:http://www.cnblogs.com/cfantaisie/archive/2011/06/14/2080917.html   主要步骤  1).尺度空间的生成:     2).检测尺度 ...

  5. POJ 1195 Mobile phones (二维树状数组)

    Description Suppose that the fourth generation mobile phone base stations in the Tampere area operat ...

  6. 网络直播流媒体协议的选择讨论,RTSP,RTMP,HTTP,私有协议?

    最近有不少人在EasyDarwin的交流群里面问关于花椒.映客手机直播技术的问题,还有RTSP.RTMP协议选择的问题,这里个人谈一下自己的愚见. 1.不管是RTSP/RTP.RTMP.HTTP,亦或 ...

  7. EasyDarwin流媒体云平台架构

    EasyDarwin目前正在做的开源流媒体云平台架构:

  8. EasyDarwin流媒体服务器高性能优化方向

    我们在EasyDarwin开源流媒体服务器上做了很多的优化,包括前面说到的<EasyDarwin开源流媒体服务器将select改为epoll的方法>.<EasyDarwin开源流媒体 ...

  9. 九度OJ 1118:数制转换 (进制转换)

    时间限制:1 秒 内存限制:32 兆 特殊判题:否 提交:3873 解决:1494 题目描述: 求任意两个不同进制非负整数的转换(2进制-16进制),所给整数在long所能表达的范围之内.     不 ...

  10. ElasticSearch(十二)批量查询mget

    1.批量查询的好处 就是一条一条的查询,比如说要查询100条数据,那么就要发送100次网络请求,这个开销还是很大的如果进行批量查询的话,查询100条数据,就只要发送1次网络请求,网络请求的性能开销缩减 ...