From: Steven Smith <sos22@cam.ac.uk>
To: Haines Brown <brownh@hartford-hwp.com>
Cc: sos22@cam.ac.uk, linux-newbie@vger.kernel.org
Subject: Re: Phantom executables
Date: Tue, 30 Apr 2002 08:05:51 +0100 [thread overview]
Message-ID: <20020430070551.GA405@cam.ac.uk> (raw)
In-Reply-To: <200204300043.g3U0hDI07271@langhans.hartford-hwp.com>
[-- Attachment #1: Type: text/plain, Size: 2032 bytes --]
> It looks like I'll have get the old libstdc++.so.27 and I should be in
> business. I see that in rpmfind there's a libc-5.4.46-2 RPM for i386
> that provides libstdc++.so.27. I've downloaded but not yet installed
> it.
>
> It looks like I should simply install this old libc-5, and it will
> provide the libstdc++.27 that I need. However, I hope this
> installation of old libraries won't upset my system.
>
> I mention all this in the hope will confirm I'm on the right track and
> that I should not suffer ill effects from installing the RPM.
Everything you've said sounds reasonable, and just installing the RPM
should work.
Having said that, you might want to use the following, slightly
convoluted, method to install, as this should make any errors easier
to recover from.
1) Copy /lib/* into /lib.bak
2) Add a line ``/lib.bak'' at the top of /etc/ld.so.conf.
3) Run ldconfig. This is usually /sbin/ldconfig, but occasionally
/lib/ldconfig
4) Install the RPM.
5) From a shell, go ``export LD_LIBRARY_PATH=/lib''. Any programs started
from that shell will now use the new libc. If it suffers ugly errors,
copy /lib.bak back into /lib and rerun ldconfig. You might want to
give the --remove-destination switch to cp. Obviously, it will be
easier to run cp from a shell which isn't broken.
6) If there are no errors, remove the /lib.bak line from ld.so.conf and rerun
ldconfig. All programs started from now on should use the new libc.
I would recommend rebooting at this point.
If, after you've rebooted, nothing works any more, try booting again
but specifying LD_LIBRARY_PATH=/lib.bak on the command line.
Once everything's working, you can remove lib.bak.
It might be a good idea to have SASH installed before you try this,
as it doesn't need libc and might be useful for recovering if something
goes wrong. Boot disks and rescue disks are also useful.
Steven Smith,
sos22@cam.ac.uk.
Disclaimer: I'm not going to blow away my libc just to test this for you.
Sorry.
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-04-30 7:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-25 18:59 DVI to RTF G Anna
2002-04-26 8:15 ` Michael Scottaline
2002-04-26 20:50 ` Haines Brown
2002-04-26 21:08 ` Phantom executables Haines Brown
2002-04-26 21:50 ` Steven Smith
2002-04-30 0:43 ` Haines Brown
2002-04-30 7:05 ` Steven Smith [this message]
2002-04-26 22:02 ` Elias Athanasopoulos
2002-04-26 9:11 ` DVI to RTF Steven Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020430070551.GA405@cam.ac.uk \
--to=sos22@cam.ac.uk \
--cc=brownh@hartford-hwp.com \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox