home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!think.com!barmar
- From: barmar@think.com (Barry Margolin)
- Newsgroups: comp.sys.sun.admin
- Subject: Re: How to update shared libraries?
- Date: 17 Dec 1992 19:03:59 GMT
- Organization: Thinking Machines Corporation, Cambridge MA, USA
- Lines: 33
- Message-ID: <1gqiuvINNj6m@early-bird.think.com>
- References: <1992Dec17.115050.9821@news.uni-stuttgart.de>
- NNTP-Posting-Host: telecaster.think.com
-
- In article <1992Dec17.115050.9821@news.uni-stuttgart.de> jens@kssun3.rus.uni-stuttgart.de (Jens Schweikhardt 07151690270) writes:
- >On our Sparc Station with SUNOS 4.1.1 we have shared libraries
- ...
- >Now I ftp'd a binary from some other Sparc Station which on invocation
- >produced a linker warning:
- >ld.so: warning: /usr/lib/libc.so.1.6.1 has older revision than expected 7
-
- Revision 7 is the version of libc that comes with SunOS 4.1.2. This
- warning indicates that the binary was linked on a 4.1.2 system.
-
- >So my libraries are not up to date.
-
- Your libraries are fine -- you have the most up-to-date version for 4.1.1.
- The problem is that the program you copied was compiled on a newer OS
- revision. Running programs compiled on a newer OS is not guaranteed to
- work, since the newer compiler and includes may have references to features
- that didn't exist in the old revision. You can ignore the warning and hope
- things work (they usually do, as there aren't many such differences between
- 4.1.1 and 4.1.2), you can upgrade the 4.1.1 system to a newer release, or
- you can recompile the program on the 4.1.1 system.
-
- I can get from the same Sparc Station
- >the libraries with version 1.8 and 1.8.1. My question is if I can
- >just ftp these and put them in my /usr/lib and do a ldconfig.
-
- No, that's pretty dangerous. The newer shared libraries may expect new or
- modified system call interfaces.
-
- --
- Barry Margolin
- System Manager, Thinking Machines Corp.
-
- barmar@think.com {uunet,harvard}!think!barmar
-