home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!uwm.edu!ogicse!news.u.washington.edu!serval!luke.eecs.wsu.edu!hlu
- From: hlu@luke.eecs.wsu.edu (H.J. Lu)
- Newsgroups: comp.os.linux
- Subject: Re: libc.a errors with gcc 2.3.3
- Keywords: gcc, 486
- Message-ID: <1993Jan1.224805.21285@serval.net.wsu.edu>
- Date: 1 Jan 93 22:48:05 GMT
- Article-I.D.: serval.1993Jan1.224805.21285
- References: <1993Jan1.013916.26835@mintaka.lcs.mit.edu> <1993Jan1.073740.17721@serval.net.wsu.edu> <1i175uINNndp@alnitak.usc.edu>
- Sender: news@serval.net.wsu.edu (USENET News System)
- Organization: Washington State University!
- Lines: 25
-
- In article <1i175uINNndp@alnitak.usc.edu> dkyoon@alnitak.usc.edu (Dae-Kyun Yoon) writes:
- >>>Also:
- >>> Is it safe to delete /usr/lib/shlib/jump and nojump?
- >>> I believe these are the gcc 2.2.2d directories for
- >>> the jump libraries and have been replaced with
- >>> lib*.ca and lib*.sa in /usr/lib. Is this correct?
- >>>
- >
- >>Yes.
- >
- >I doubt that just removing /usr/lib/shlib/jump is really safe, especially
- >if you have thoses libraries other than the standard gcc's. I think
- >you'd better copy old libraries to /usr/lib/*.sa first before removing
- >jump/ directory.
-
- Oops.
-
- >
- >BTW, H.J., could you tell us what jump-4.2.TZ is for, then ?
- >
-
- That is the source code for building shared libraries.
-
-
- H.J.
-