home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sun.misc
- Path: sparky!uunet!mcsun!sun4nl!fwi.uva.nl!casper
- From: casper@fwi.uva.nl (Casper H.S. Dik)
- Subject: Re: Can I get rid of "ld.so: warning: /usr/lib/libc.so.1.foo.bar ..."
- Message-ID: <1992Jul24.075143.27487@fwi.uva.nl>
- Sender: news@fwi.uva.nl
- Nntp-Posting-Host: adam.fwi.uva.nl
- Organization: FWI, University of Amsterdam
- References: <1992Jul24.010617.11446@kronos.arc.nasa.gov>
- Date: Fri, 24 Jul 1992 07:51:43 GMT
- Lines: 31
-
- kthompso@kronos.arc.nasa.gov (Kevin Thompson) writes:
-
-
- >Like many large installations I expect, we have several different SunOS'es
- >running on various machines. If one builds a program (say perl) on 4.1.2,
- >then anytime you run perl on a program running 4.1.1, or some random patch,
- >or whatever, you get:
-
- >ld.so: warning: /usr/lib/libc.so.1.6 has older revision than expected 7
-
- >Is there any sort of general way of getting rid of these? Can one just make
- >links on every machine from /usr/lib/libc.so.1.7 to /usr/libc/.so.1.6 (or
- >whatever)? Is there harm in this? libc doesn't change much, this warning
- >message drives me bananas ....
-
- You can install the 4.1.2 libc on the 4.1.1 machines. 4.1.2
- contains a libc jumbo patch that is also available for 4.1.1.
- The patch id is #100266/#100267 (domestic/intl). I don't know what
- revision it is.
-
- You can also simply hardlink libc.s[oa].1.6 to libc.s[oa].1.7. But remember
- that these warnings are there for a reason.
-
- We have built all software running on 4.1.1 and 4.1.2 machines on 4.1.1
- machines because in general newer releases can run software compiled
- on older releases, but the reverse isn't necessarily true.
-
- Casper
- --
- | Casper H.S. Dik
- | casper@fwi.uva.nl
-