Bug 1801 - ut2004-lnxpatch3236-1 cannot open libstdc++.so.5!!!!!!!!!!
Status: RESOLVED FIXED
Alias: None
Product: Unreal Tournament 2004
Classification: Unclassified
Component: dedicated server
Version: 3236 (Second official retail patch)
Hardware: PC Linux
: P1 blocker
Assignee: Ryan C. Gordon
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2004-06-20 21:35 EDT by nixnerd
Modified: 2006-03-02 16:06:20 EST
0 users

See Also:



Description nixnerd 2004-06-20 21:35:08 EDT
./ucc-bin: error while loading shared libraries: libstdc++.so.5: cannot open
shared object file: No such file or directory
Comment 1 nixnerd 2004-06-20 21:35:41 EDT
# ./ucc-bin
./ucc-bin: error while loading shared libraries: libstdc++.so.5: cannot open
shared object file: No such file or directory
Comment 2 nixnerd 2004-06-20 21:45:47 EDT
Plain 'ole lnxpatch3236 worked fine - aside from the long loading issues, but
sadly lnxpatch3236-1 gives error cannot open libstdc++.so.5 and refuses to run.
I had to revert back to lnxpatch3236! >:-(
Comment 3 Ryan C. Gordon 2004-06-21 02:22:23 EDT
I knew this would happen to _someone_.

The latest patch is built with gcc 3, which has an external dependency that gcc
2 doesn't (some gcc-specific support libraries). Any modern Linux distro should
have these libraries on it, but apparently some FreeBSD systems using Linux
binary compatibility or older Linux systems may not.

You need to either:

1) Install gcc3 on your system.
2) Update to a newer Linux distribution.
3) The easiest: download this:

    http://icculus.org/updates/cod/gcc3-libs.tar.bz2

And put them where the dynamic loader will find them. (/lib will work, but be
careful not to confuse future system updates). Don't forget to run ldconfig as
root after installing those libs.

--ryan.

Comment 4 nixnerd 2004-06-21 11:00:02 EDT
Thanks Ryan, keep up the good work!
Comment 5 Dennis 2004-11-11 14:53:40 EST
This is my first post here, so please forgive me if im doing annything wrong.
First post ever for bugzilla, so please feel free to correct me if posting at 
the wrong place/or doing obsolute posting.

Yesterday (10 november 2004) I have installed Fudora Core 3. I am trying to get 
a Coduo server running on it. 

When i run the binary i get:


-------------------------------------------->8

[root@server01 cod]# ./coduo_lnxded
./coduo_lnxded: error while loading shared libraries: libstdc++.so.5: cannot 
open shared object file: No such file or directory
[root@server01 cod]#

-------------------------------------------->8

I do have a libstdc++.so.6 file on my file system.

Is this a bug for the server binairy or is the fudora core 3 not downwards 
compatible?

Since the advice sounds: qoute from Ryan C. Gordon : "Any modern Linux distro 
should have these libraries on it, but apparently some FreeBSD systems using 
Linux binary compatibility or older Linux systems may not."

I figure Fudora code 3 is quite new...
Comment 6 Ryan C. Gordon 2004-11-11 15:06:07 EST
Fedora went from libstdc++.so.4 to 6.

Just download the package and put it somewhere, it shouldn't hurt anything.

--ryan.
Comment 7 Dennis 2004-11-11 15:22:58 EST
Thanks for the quick responce. I did get it to work with your suggestion.
Comment 8 757driverwannabee 2006-03-01 23:00:59 EST
While following these instructions, I managed to break a lot of things on my system that depend on libgcc_s.so. When you say 'put them where the loader will find them', I assume you mean /lib, correct?
Comment 9 Ryan C. Gordon 2006-03-02 07:24:02 EST
I meant somewhere that it will see them without overwriting existing system files.  :/

Like, say, the game's directory added to the LD_LIBRARY_PATH environment variable before running the game, or adding a new line to /etc/ld.so.conf

--ryan.
Comment 10 757driverwannabee 2006-03-02 16:06:20 EST
(In reply to comment #9)
> I meant somewhere that it will see them without overwriting existing system
> files.  :/
> 
> Like, say, the game's directory added to the LD_LIBRARY_PATH environment
> variable before running the game, or adding a new line to /etc/ld.so.conf
> 
> --ryan.
> 

Alright, understand now. Fixed hosage. Thanks.