“没有可用的版本信息”在centos6上启动pypy时出现警告
我已经为此苦苦挣扎了几个小时，不知道如何摆脱它（或者它是否会给我带来任何问题），但是当我在 centos6 上启动 pypy 时，我不断收到以下警告
[root@domU-123 bin]# ./pypy
./pypy: /usr/lib64/libssl.so.0.9.8: no version information available (required by ./pypy)
./pypy: /usr/lib64/libcrypto.so.0.9.8: no version information available (required by ./pypy)
Python 2.7.2 (0e28b379d8b3, Feb 09 2012, 19:41:03)
[PyPy 1.8.0 with GCC 4.4.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
And now for something completely different: ``"Let's go." - "We can't" - "Why
not?" - "We're waiting for a Translation." - (despairingly) "Ah!"''
>>>>
：我的安装脚本（我将其安装在新的 centos 系统上）：
#install pypy
wget https://bitbucket.org/pypy/pypy/downloads/pypy-1.8-linux64.tar.bz2
tar xvf pypy*
yum -y install openssl098e
ln -s /usr/lib64/libssl.so.0.9.8e /usr/lib64/libssl.so.0.9.8
ln -s /usr/lib64/libcrypto.so.0.9.8e /usr/lib64/libcrypto.so.0.9.8
ln -s /lib64/libbz2.so.1.0.4 /lib64/libbz2.so.1.0
任何人都可以建议如何修复它吗？我是否缺少软件包或者需要配置什么？
I've been struggling with this for a few hours and not sure how to get rid of it(or if it'll cause any problems for me) but I keep getting the following warnings when I start pypy on centos6:
[root@domU-123 bin]# ./pypy
./pypy: /usr/lib64/libssl.so.0.9.8: no version information available (required by ./pypy)
./pypy: /usr/lib64/libcrypto.so.0.9.8: no version information available (required by ./pypy)
Python 2.7.2 (0e28b379d8b3, Feb 09 2012, 19:41:03)
[PyPy 1.8.0 with GCC 4.4.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
And now for something completely different: ``"Let's go." - "We can't" - "Why
not?" - "We're waiting for a Translation." - (despairingly) "Ah!"''
>>>>
Here's a copy of my install script(I install this on a fresh centos system):
#install pypy
wget https://bitbucket.org/pypy/pypy/downloads/pypy-1.8-linux64.tar.bz2
tar xvf pypy*
yum -y install openssl098e
ln -s /usr/lib64/libssl.so.0.9.8e /usr/lib64/libssl.so.0.9.8
ln -s /usr/lib64/libcrypto.so.0.9.8e /usr/lib64/libcrypto.so.0.9.8
ln -s /lib64/libbz2.so.1.0.4 /lib64/libbz2.so.1.0
Can anyone suggest how to fix it? Am I missing a package or does something need to be configured?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这就是与 Linux 可怕的二进制兼容性问题
如果你没有与构建服务器相同的发行版/版本， ，
您可以假设它可能会由于
最近版本的发行版政策和库而损坏，它可能会在任何不相似的情况下损坏
构建服务器上的内容（运行最近的 ubuntu）
（在它是 debian 之前，但定期以奇怪的方式破坏 openssl），
因为发行版似乎定期破坏一般的二进制兼容性，
这不是 pypy 核心团队会花更多时间在
外部维护人员身上的事情
this is the dreaded binary compatibility problem with linux
basically if you don’t have the same distro/version as the build server,
you can assume it may break due to distro policies wrt libs
for recent builds, its likely broken on anything that’s not similar
to whats on the build server (which runs a recent ubuntu)
(before it was a debian, but that broke openssl in strange ways on a regular basis)
since distros seem break general binary compatibility on regular basis,
this is not something that the pypy core team will spend more time on
external maintainers wanted