This is the mail archive of the
glibc-linux@ricardo.ecn.wfu.edu
mailing list for the glibc project.
RE: Error 127 in install of glibc 2.2.3
- To: <glibc-linux at ricardo dot ecn dot wfu dot edu>
- Subject: RE: Error 127 in install of glibc 2.2.3
- From: "Kate Ahrens" <kate dot ahrens at unisonfree dot net>
- Date: Mon, 30 Jul 2001 18:51:44 +0100
- Reply-To: glibc-linux at ricardo dot ecn dot wfu dot edu
Hi Allin,
> > > One question occurs to me: What did you do with the glibc 2.2.3
> > > installation that you put under /usr/local? I suppose it ought
> > > to be deleted entirely in case it interferes with the new
> > > installation under /usr.
> >
> > I haven't done anything with it. What's the safest way to remove it?
>
> Hmm. Not sure about that. You can find a listing of the files
> installed by glibc 2.2.3 at
> ftp://ricardo.ecn.wfu.edu/pub/glibc-2.2.3/listing.txt
I looked at that. Thanks. But my /usr/local directories (esp lib) have other
files mixed in so Ican't just rm * - is there a way to delete files by date,
so that I can wipe everything that was installed at the same time?
> I'd say the most important candidates for deletion are the files in
> lib and sbin (under /usr/local). I'm not sure about the wisdom of the
> recommendation to install glibc under /usr/local at first -- seems to
> me there's too much potential for confusion and conflicts. Some of
> the glibc components have paths "hard-wired" into them at compile
> time. In fact it might help your system recovery if you were to make
> sure /usr/local is not in your path at boot time, and /usr/local/lib
> is not referenced in /etc/ld.so.conf (as a temporary measure).
Can you explain how to check these things?
I'd second your thoughts about the /usr/local thing. At the time, I thought
it was a sensible precaution but I don't understand how the libraries can
have installed OK into /usr/local and then failed to install into /usr
unless the first installation made the problems for the second one. It's
certainly led to confusion here. I've now gone three days without being able
to log in I still can't get my system started and I'm getting very behind
with work. Not what I'd anticipated at all.
Nick