Page 1 of 1

OpenSUSE 42.3 "bzip2-libs" I can't find it!

Posted: Fri Sep 01, 2017 6:35 pm
by GPU timpster
Hey, I'd love to CPU fold on OpenSUSE in a VM but currently I'm just slowing down my windows folding by trying to get this to work, so any performance advantage will take a long time to overtake my native windows performance if I ever get this working. I'm trying the beta 7.4.16.

I've installed "bzip2" but NOT the libs that it's asking for because I can't find it anywhere, I'm trying breaking the installation using it w/o the libs. So far I'm not able to access "folding@home" (not the web interface) because it's not listed in the menu anywhere. I tried the web interface but it couldn't find my client, and I tried finding the bin file for FAHClient but it didn't seem to load at all.

Any help would be appreciated because I'd like to install a big folding system with several CPUs to efficiently (and cheaply) fold on Linux.

Re: OpenSUSE 42.3 "bzip2-libs" I can't find it!

Posted: Fri Sep 01, 2017 9:08 pm
by GPU timpster
Addition, I've run "FAHClient" in a terminal and this is the output I recieved:

Code: Select all

FAHCleint: Error while loading shared libraries: libssl.so.10: cannot open shared object file: No such file or directory

Re: OpenSUSE 42.3 "bzip2-libs" I can't find it!

Posted: Sun Sep 03, 2017 3:40 am
by GPU timpster
Last and final update, as I have no further information to help with this so far: (WITHOUT any updates) OpenSUSE 42.1 stock, will run FAHClient (non beta 7.4.4) with the new 7.4.16, because I wanted to test it, without issue, and WITHOUT bzip2-libs.

Re: OpenSUSE 42.3 "bzip2-libs" I can't find it!

Posted: Mon Sep 04, 2017 3:14 am
by bruce
I don't have any specific information about OpenSUSE or other unsupported versions of Linux, but as a general rule, many libraries are version specific (in your case, FAH is looking for revision 10 of libssl.so). If your system happens to have either revision 9 or revision 11, it's likely that either might work (and there's a slim chance that whatever change prompted the revision will NOT work) but you'd need to try it by setting a link for revision 10 in addition to whatever link is provided by your distro ... and then see whether it works or not.

The Version 10 specific reference was created by the compiler used to generate FAH's code and your distro probably supports a different compiler version -- and hence a different library version.

Re: OpenSUSE 42.3 "bzip2-libs" I can't find it!

Posted: Thu Sep 14, 2017 12:19 am
by v00d00
Had a quick look on google and came up with this thread for OpenSuse.

https://forums.opensuse.org/showthread. ... ypto-so-10

You could try symlinking the libraries as suggested in the thread. That may get you up and running on the client.

On the topic of bzip2-libs. Do you have bzip2 installed? If not.

https://software.opensuse.org/package/bzip2

The bzip2 libs.

https://opensuse.pkgs.org/42.3/opensuse ... 4.rpm.html
or
https://opensuse.pkgs.org/42.3/opensuse ... 4.rpm.html

I haven't used Suse in about 16 years, so YMMV (as ever). But those seem to be what you are lacking. It may also be that you need to fudge it with some symlinks if it requires a specific version.

To find out what else you need to install, you can run ldd against the program. So for instance on my system if i run ldd against FAHclient, I would get.

Code: Select all

# ldd fahclient 
        linux-vdso.so.1 (0x00007fff7cf28000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f7cf8dc8000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f7cf8bb0000)
        libbz2.so.1.0 => /lib64/libbz2.so.1.0 (0x00007f7cf89a0000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f7cf8780000)
        libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f7cf8478000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f7cf8170000)
        libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007f7cf7f58000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f7cf7b88000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f7cf9000000)
If anything is missing it will let you know, then put the name of the shared object into google and put opensuse after it.