climateprediction.net home page
shared library problem

shared library problem

Questions and Answers : Unix/Linux : shared library problem
Message board moderation

To post messages, you must log in.

AuthorMessage
old_user378

Send message
Joined: 7 Aug 04
Posts: 1
Credit: 591,739
RAC: 0
Message 276 - Posted: 7 Aug 2004, 4:55:02 UTC

I ran into the problem on an older SuSE distribution (8.0, I think) that doesn\'t have gcc >3.0 installed. So when I run boinc I get the following:


heavner/boinc> ./boinc_4.02_i686-pc-linux-gnu
./boinc_4.02_i686-pc-linux-gnu: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory


And so in the spirit of trouble-shooting,

heavner/boinc> ldd -v boinc_4.02_i686-pc-linux-gnu | grep not
libstdc++.so.5 => not found
libgcc_s.so.1 => not found
libgcc_s.so.1 (GCC_3.0) => not found
libstdc++.so.5 (GLIBCPP_3.2) => not found
libstdc++.so.5 (CXXABI_1.2) => not found


I think the best solution would be to have the boinc executable available as a statical (not linked) download as well as the linked version currently. It is long past time to upgrade the computer anyway, so hopefully I\'ll get to it this week and be back in boinc-land.

I\'m just adding this info here in case anyone else runs into it.

Matt
ID: 276 · Report as offensive     Reply Quote
old_user1
Avatar

Send message
Joined: 5 Aug 04
Posts: 907
Credit: 299,864
RAC: 0
Message 299 - Posted: 7 Aug 2004, 10:14:53 UTC

yeah, I've actually statically linked everything I could think of in the CPDN binaries (the monitor program, climate model program, and smallexecs processing program), but I didn't do that for the BOINC client! I suppose some enterprising person could figure out how to statically link everything but the kitchen sink into BOINC! :-)

ID: 299 · Report as offensive     Reply Quote
old_user221

Send message
Joined: 6 Aug 04
Posts: 3
Credit: 202,374
RAC: 0
Message 490 - Posted: 9 Aug 2004, 4:50:00 UTC - in response to Message 299.  

I have run into the same problem trying to run CPDN on a Debian stable (woody) distribution. With Debian, a possible solution is to apt-pin the newer GNU C++ shared libraries into the system, but this requires work by the sysadmin.

A different idea is to obtain/create BOINC binaries which have been linked against different versions of the GNU libraries (assuming BOINC does not use functionality only available in the latest libraries). This means you will have several linux binaries for CPDN (one each for the various versions of GNU C++ libraries). It's ugly, but it is difficult to see how you are going to get around this problem if BOINC is built against the latest GNU libraries
ID: 490 · Report as offensive     Reply Quote
Profile old_user812

Send message
Joined: 12 Aug 04
Posts: 52
Credit: 121,983
RAC: 0
Message 881 - Posted: 13 Aug 2004, 2:32:45 UTC

Hi

I ran into this on freebsd 5.2.1 running linux emulation. It uses a version of redhat 7 for emulation, and the file only appears in version 8 (I installed linux_base_8 out of the ports, this installs the required library. Linux emulation is automatically loaded.)

So I'd guess the answer on linux platforms would be to get a more recent linux!

---
reiteration.net networks
ID: 881 · Report as offensive     Reply Quote
old_user206

Send message
Joined: 6 Aug 04
Posts: 2
Credit: 29,057
RAC: 0
Message 1020 - Posted: 16 Aug 2004, 1:04:35 UTC - in response to Message 299.  

> yeah, I've actually statically linked everything I could think of in the CPDN
> binaries (the monitor program, climate model program, and smallexecs
> processing program), but I didn't do that for the BOINC client! I suppose
> some enterprising person could figure out how to statically link everything
> but the kitchen sink into BOINC! :-)

Hey Carl-

Glad y'all finally hit 4.x. :-)

The problem with linking everything but the kitchen sink into boinc is glibc... specifically, gethostbyname(). I've *tried* pushing Dr. Anderson towards some other DNS resolving libraries to get around the gethostbyname() issue, but haven't had much luck. It was on the tasklist for M2 (and I think once 4.x hits S@H, it'll be M2)... but I don't think it'll happen now. :-(

Right now I have one box running 4.x and the other running 3.x. The 4.x box (running CPDN Beta [hopefully] and Boinc Alpha right now) is also an old pre-GCC 3.2 box.. so I'm running into the same issue.

Check out the 'collect2' script (it might be named differently, I forget) in the boinc/client directory for what Berkeley uses to link boinc so it works for the most folks. It does rely on their oddball box, though. It's somewhat of a Frankenstien box as far as I can tell.

Maybe Rom could get something compiled for you if they haven't already released 4.02 somewhere?

Rob
ID: 1020 · Report as offensive     Reply Quote
old_user150

Send message
Joined: 5 Aug 04
Posts: 1
Credit: 7,208,611
RAC: 0
Message 4561 - Posted: 23 Sep 2004, 19:35:24 UTC

I have also SuSE 8.0 and the downloaded BOINC Client does not run.
However, I just compiled the BOINC client (version 4.08) myself on SuSE 8.0 without any problems.

Download client from:
http://boinc.berkeley.edu/source/archive/

tar xfz boinc-xx.tar.gz
cd boinc-xx
./configure --disable-server
make

That's all!
Now CPDN-BOINC runs also on this old system ;-)

Hope this helps

Urs

ID: 4561 · Report as offensive     Reply Quote

Questions and Answers : Unix/Linux : shared library problem

©2024 cpdn.org