Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!wuarchive!rice!rice!sun-spots-request
From: ddp+@andrew.cmu.edu (Drew Daniel Perkins)
Newsgroups: comp.sys.sun
Subject: dynamic vs. static linking
Keywords: Miscellaneous
Message-ID: <1990Oct7.231048.3568@rice.edu>
Date: 7 Oct 90 21:30:00 GMT
Sender: sun-spots-request@rice.edu
Organization: Sun-Spots
Lines: 14
Approved: Sun-Spots@rice.edu
Originator: spots@walhalla.rice.edu
X-Sun-Spots-Digest: Volume 9, Issue 338, message 3

Can anyone comment on what commercial packages under SunOS 4.x do about
dynamic vs. static linking?  If I link a program on a SparcStation running
4.0.3c and then run it on a Sun 4/490 runnning 4.0.3, I get an anoying
message: ld.so: warning: /usr/lib/libc.so.1.3 has older revision than
expected 4

I've found a few ways to get around this, none of them particularly enticing:
1. Link on the 4.0.3 system so that I get /usr/lib/libc.so.1.3.
2. Link on the SS1 and explicitly use /usr/lib/libc.so.1.3.
3. Use static linking.

What do other people do?

Drew