ldd /usr/bin/info will show you which libc it is using already.  That is
the one you want to point libz.so.1 to.  rm <linkname> will remove the
link.  It won't touch the underlying file.

Lawson
          >< Microsoft free environment

This mail client runs on Wine.  Your mileage may vary.

On Sat, 8 May 1999, Kurt Kehler wrote:

> On Fri, 7 May 1999 20:27:11 -0400, Michael Hobgood wrote:
> 
> >    I had this same problem when I installed Slackware 3.5  To solve
it you
> >need to create a symbolic link as follows:
> >
> >ln -s libc.so.5.4.44   libz.so.1
> >
> >If your libc.so file has a different number than 5.4.44 use the number
in
> >your file.
> 
> I tried this.  Since I had a libc.so.6 I used that instead of the
> above:
> darkstar:/lib# ln -s libc.so.6 libz.so.1
> 
> Now, when I type info I get: Segmentation fault
> 
> After doing the above symbolic link, my /lib looks like this:
> 
> darkstar:/lib# ls -al libc.so*
> lrwxrwxrwx   1 root     root           13 Oct 27  1998 libc.so.4 ->
> libc.so.4.7.6*
> -rwxr-xr-x   1 root     root       634880 Jun  4  1996 libc.so.4.7.6*
> lrwxrwxrwx   1 root     root           14 Oct 27  1998 libc.so.5 ->
> libc.so.5.4.46*
> -rwxr-xr-x   1 root     root       614840 Sep 14  1998 libc.so.5.4.46*
> lrwxrwxrwx   1 root     root           13 Oct 27  1998 libc.so.6 ->
> libc-2.0.7.so*
> 
> darkstar:/lib# ls -al libz*
> lrwxrwxrwx   1 root     root            9 May  8 02:11 libz.so.1 ->
> libc.so.6*
> ----------------------
> 
> Maybe I should have linked 'libc.so.5.4.46' instead of 'libc.so.6' to
> 'libz.so.1'?  How do I unlink what I just did?  Man unlink hasn't
> worked yet but I will reread it.  I'm afraid I will delete the actual
> file, rather than simply delete the link I just made.  :)
> 
> Thanks,
> Kurt Kehler
> 
> 
> 
> 
> 




___________________________________________________________________
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com/getjuno.html
or call Juno at (800) 654-JUNO [654-5866]

Reply via email to