no version information available
2013-04-01 21:27
435 查看
The "no version information available" means that the library version number is lower on the shared object. For example, if your major.minor.patch number is 7.15.5 on the machine where you build the binary, and the major.minor.patch number
is 7.12.1 on the installation machine,ld will print the warning.
You can fix this by compiling with a library (headers and shared objects) that matches the shared object version shipped with your target OS. E.g., if you are going to install to RedHat 3.4.6-9 you don't want to compile on Debian 4.1.1-21. This is one of the
reasons that most distributions ship for specific linux distro numbers.
Otherwise, you can statically link. However, you don't want to do this with something like PAM, so you want to actually install a development environment that matches your client's production environment (or at least install and link against the correct library
versions.)
Advice you get to rename the .so files (padding them with version numbers,) stems from a time when shared object libraries did not use versioned symbols. So don't expect that playing with the .so.n.n.n naming scheme is going to help (much - it might help if
you system has been trashed.)
You last option will be compiling with a library with a different minor version number, using a custom linking script: http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/gnu-linker/scripts.html
To do this, you'll need to write a custom script, and you'll need a custom installer that runs ld against your client's shared objects, using the custom script. This requires that your client have gcc or ld on their production system.
原帖:http://hi.baidu.com/ligh0721/item/4013e6804cf2daceee083df3
is 7.12.1 on the installation machine,ld will print the warning.
You can fix this by compiling with a library (headers and shared objects) that matches the shared object version shipped with your target OS. E.g., if you are going to install to RedHat 3.4.6-9 you don't want to compile on Debian 4.1.1-21. This is one of the
reasons that most distributions ship for specific linux distro numbers.
Otherwise, you can statically link. However, you don't want to do this with something like PAM, so you want to actually install a development environment that matches your client's production environment (or at least install and link against the correct library
versions.)
Advice you get to rename the .so files (padding them with version numbers,) stems from a time when shared object libraries did not use versioned symbols. So don't expect that playing with the .so.n.n.n naming scheme is going to help (much - it might help if
you system has been trashed.)
You last option will be compiling with a library with a different minor version number, using a custom linking script: http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/gnu-linker/scripts.html
To do this, you'll need to write a custom script, and you'll need a custom installer that runs ld against your client's shared objects, using the custom script. This requires that your client have gcc or ld on their production system.
原帖:http://hi.baidu.com/ligh0721/item/4013e6804cf2daceee083df3
相关文章推荐
- libjpeg.so.62: no version information available (required
- /mongod: /usr/lib64/libssl.so.10: no version information available (required by ./mongod)
- no version information available
- Linux启动报/lib/libblkid.so.1:no version information available解决办法
- svn /lib64/libz.so.1: no version information available
- /usr/lib64/libssl.so.10: no version information available (required by ./mongod)
- linux下执行aapt时,提示/usr/lib/libz.so.1 no version information available
- libxml2.so.2 No version information available
- 安装gid12.0.4linux-x64l后启动报错/liblzma.so.5: no version information available 的解决办法
- libxml2.so.2 No version information available
- /usr/local/lib/libxml2.so.2: no version information available errors
- caffe安装:cmake: /home/shree/anaconda2/lib/libcurl.so.4: no version information available
- The POM for XXX:jar:${com.ld.base.service.version} is missing, no dependency information available
- no version information available 动态链接库出错
- 异常提示:编译软件出现没有可用的版本信息 no version information available
- php: /usr/local/lib/libxml2.so.2: no version information available (required by php)
- ccmake: /root/anaconda2/lib/libcrypto.so.1.0.0: no version information available
- no version information available
- linux aapt出现/lib/libz.so.1: no version information available解决方案
- linux下交叉编译提示/lib/libz.so.1: no version information available