Message boards : Questions and problems : libssl on 6.12 builds mageia
Message board moderation
Author | Message |
---|---|
Send message Joined: 17 Oct 11 Posts: 1 ![]() |
Hi! I've been running mageia linux for a while now, and saw an update message in my BOINC messages. Downloading 6.12.34 and installing went fine, but when I tried running the manager, I got the error: libssl.so.0.9....not found. Mageia comes with libopenssl 1.0.0d. Can we ensure the client works with current distros? Thanks! |
Send message Joined: 17 Oct 11 Posts: 2 ![]() |
May I suggest making both a statically and a dynamically linked version. This is easy and may mean that I would be able to upgrade the software. Especially when libssl has undergone a major upgrade, that should be taken into account. Just pretending version 0.9.8 is 1.0.0d is simply not working. I tried it. |
Send message Joined: 17 Oct 11 Posts: 2 ![]() |
I am also wondering why two versions of libssl and libcrypto are used in the same program. -rwxr-xr-x 1 1000 1000 3015712 28 jul 22:15 boincmgr boincmgr: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory ldd boincmgr libssl.so.0.9.8 => not found libcrypto.so.0.9.8 => not found libssl.so.10 => /usr/lib64/libssl.so.10 (0x0000003195800000) libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x0000003192800000) |
![]() ![]() Send message Joined: 29 Aug 05 Posts: 15655 ![]() |
I asked the developer about this (I don't build them either), he said this is fixed in 6.13.8 and it'll be back-ported to a new 6.12 coming to a place near you very soon. ;-) |
![]() ![]() Send message Joined: 29 Aug 05 Posts: 15655 ![]() |
|
Send message Joined: 10 Dec 11 Posts: 2 ![]() |
Sometimes you can get away with a symbolic link if the library is mature enough to have been built with updates in mind (the header.c files need to remain in the same order and new functions added "after"). glibc is a good example of a well maintained library that is usable by old or newer binaries. For Mageia 1 (32bit), this seemed to work okay in getting the boinc manager working. Start a command line shell and insert two symlinks as seen below: cd /usr/lib su password: ******** ln -s libcrypto.so.1.0.0 libcrypto.so.0.9.8 ln -s libssl.so.1.0.0 libssl.so.0.9.8 ls -l libssl* lrwxrwxrwx 1 root root 15 Dec 9 22:22 libssl.so.0.9.8 -> libssl.so.1.0.0* -rwxr-xr-x 1 root root 365308 May 15 2011 libssl.so.1.0.0* [root@localhost lib]# ls -l libcrypto.* lrwxrwxrwx 1 root root 18 Dec 9 22:24 libcrypto.so.0.9.8 -> libcrypto.so.1.0.0* -rwxr-xr-x 1 root root 1871792 May 15 2011 libcrypto.so.1.0.0* exit The 64bit version is likely going to be in directory /usr/lib64/ instead of /usr/lib/ I only did the above minutes ago and the boinc manager seemed okay in loading 4 projects. |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.