openssl "no version information available"-优快云博客

本文提供了一种解决libssl.so.1.0.0和libcrypto.so.1.0.0无版本信息警告/错误的方法。通过在openssl源代码目录下创建名为openssl.ld的文件并配置特定参数，可以重新编译openssl库，解决DebianWheezy32位和64位系统中遇到的问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

错误：/usr/local/lib/libcrypto.so.1.0.0: no version information available

I suppose I should get right to the point...

Problem: libssl.so.1.0.0 and libcrypto.so.1.0.0 no version information available warning/error.

I SOLVED IT!!! YAY!!! (Fireworks should be going off and stuff.)

After much research, time and effort, (took weeks), here's what I finally ended up doing...

In the directory where you ended up extracting the source code for your version of openssl 1.0.1h (Should work for other versions too.) I create a file called openssl.ld

In this file put this...

Answer

OPENSSL_1.0.0 {
    global:
    *;
};

save it. Now type in...

make clean (Just to be sure we are starting fresh.)

Now for the really mind boggling part...

./config --prefix=/usr/local --openssldir=/usr/local/openssl shared -Wl,--version-script=openssl.ld -Wl,-Bsymbolic-functions

Then...

make

make test

make install

ldconfig

And that should do it. (It's so simple. No patching required.)

I have applied this solution to Debian Wheezy both 32 and 64 bit versions. And have made an observation. The 64 bit version automatically defaults to the new libssl.so.1.0.0 and libcrypto.so.1.0.0 files that are created in the /usr/local/lib directory. The 32 bit version does not. Which is why I had thought at first that the 32 bit version of Debian Wheezy didn't suffer from this problem, but it does once you get the 32 bit version to use the new openssl libraries in the /usr/local/lib dir.

Using the ldd command to test what libraries the binaries are using was invaluable in figuring this out too.

Have a nice day.

Mr. E. Dude

转载于:https://my.oschina.net/xiiyan/blog/403277