> >I got gcc 2.4.5 off of sunsite.unc.edu recently. I installed the
> >binaries and other support files in their respective directories.
> >The compiler later complained about libc.so.4 being still linked
> >to libc.so.4.3.3. How do I relink it to libc.so.4.4.1 without
> >losing the system?
> >I lost the system once by brilliantly deleting libc.so.4 and trying
> >to create another file like to link to the newer libc. *Now* I think
> >I'm getting the hang of it (well, almost)! :-))
> the answer is blowing in the wind, oh sorry in the FAQ.
> read the (weekly?) postings 'READ THIS BEFORE POSTING'
> look in the README, FAQ first.
> ln -f is the answer -f means force
> ln -f libc.so.4 libc.so.4.4.1
> should do the job
> Henrik Lund
nope. that trashes his new library. maybe he isn't the only one needing to
read the FAQ ;-) the correct answer is:
ln -sf libc.so.4.4.1 libc.so.4
(force symbolic link... filenames in the same order as for cp & mv)
(ie. ln -sf existingfile newsymlink)
personally, i'd rather answer one FAQ posting than try to post corrections to
all the incorrect FAQ answers.