home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!caen!sdd.hp.com!think.com!barmar
- From: barmar@think.com (Barry Margolin)
- Newsgroups: comp.sys.sun.misc
- Subject: Re: mixed SunOS 4.1.1 and 4.1.2 environments
- Date: 10 Sep 1992 20:12:51 GMT
- Organization: Thinking Machines Corporation, Cambridge MA, USA
- Lines: 24
- Message-ID: <18oa83INNg2h@early-bird.think.com>
- References: <1992Sep10.152932.127656@eratu.rz.uni-konstanz.de>
- NNTP-Posting-Host: telecaster.think.com
- Keywords: SunOS 4.1.1, SunOS 4.1.2, compytibility, shared library
-
- In article <1992Sep10.152932.127656@eratu.rz.uni-konstanz.de> hoehle@lindau.inf-wiss.ivp.uni-konstanz.de (Joerg-Cyril Hoehle) writes:
- >In order to prevent these warning to appear, I thought about compiling on a fast
- >4.1.2 machine, removing the executable, login into a slower 4.1.1 machine, typing
- >make again so that only linking (with the older libraries) is done and not the
- >full compile stage. The warning then disappears.
- >
- >Question: is this safe? Or should compile and link happen on the older OS for
- >compatibility between includes and libraries?
-
- It's generally safe, although I wouldn't bet my life on it, and I always
- recommend doing the entire build on the older version of the OS. Most
- structures used in Unix library calls don't have any kind of version
- information, so you're not likely to present an old library routine with a
- version of the structure that it can't handle.
-
- However, some macros may expand into calls to library routines that didn't
- exist in the older release. In general, if the link succeeds, it's likely
- to be OK.
-
- --
- Barry Margolin
- System Manager, Thinking Machines Corp.
-
- barmar@think.com {uunet,harvard}!think!barmar
-