In comp.os.linux.setup jw <jesswalton37@hotmail.com>:
> On Tue, 2005-08-09 at 16:33 +0200, Peter T. Breuer wrote:
>> jw <jesswalton37@hotmail.com> wrote:
>> > On Tue, 2005-08-09 at 08:41 -0400, Nico Kadel-Garcia wrote:
>> > > "Peter T. Breuer" <ptb@oboe.it.uc3m.es> wrote in message
>> > > news:1ihms2-san.ln1@news.it.uc3m.es...
>> > > > jw <jesswalton37@hotmail.com> wrote:
>> > > >> (error while loading shared libraries: libstdc++.so.5: cannot open
>> > > >> shared object file: No such file or directory)
>> > > >>
>> > > >> Can someone please help me here?
>> > > >
>> > > > Put it back or install it. What's your problem with that? In what way
>> > > > is the message difficult to understand - it says it isn't there, so put
>> > > > it there!
[..]
> It seems to me that your not trying to percieve anything. However it is
> quite clear that you enjoy responding to these posts because it does
> something for your ego.
> Your by no means required to respond to any post. If you find the post
> is beneath your intellectual level it would probably be best for you as
> well as others if you just kept your responses to yourself.
You mentioned, in your reply to Jean-David, you'd run FC 4i you
should have pointed out this important information earlier.
Just try (from some xterm, use 'su -' to become root or use sudo
if configure):
yum install compat-libstdc++
Or use 'up2date' to install the package.
Peter already outlined in his first reply you'd simply need to
install the package, you could have used 'yum search libstdc' to
search for the needed file or used up2date. You want to get
comfortable with the tools of your package manager (rpm), so you
could have resolved the problem from just reading the error
message, no rocket science involved. To get you started, try:
man rpm
man yum
man up2date
BTW
Glad to hear "Discovery" came back successfully without further
problems.
--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo
zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 302: microelectronic Riemannian curved-space
fault in write-only file system