Path: utzoo!attcan!uunet!cs.utexas.edu!rutgers!mit-eddie!bu-cs!att!cbnewsh!wjc From: wjc@ho5cad.ATT.COM (Bill Carpenter) Newsgroups: unix-pc.general Subject: Re: Need advice/help on upgrading to 3.51 Message-ID: Date: 15 Apr 89 12:16:56 GMT References: <518@flatline.UUCP> <1369@sialis.mn.org> Sender: nntp@cbnewsh.ATT.COM Followup-To: unix-pc.general Distribution: unix-pc Organization: AT&T Bell Laboratories Lines: 26 In-reply-to: rjg@sialis.mn.org's message of 15 Apr 89 05:15:50 GMT In article <1369@sialis.mn.org> rjg@sialis.mn.org (Robert J. Granvin) writes: > >Compatibility Caveats: I'm running a DOS-73, EIA/RAM (w/1.5Mb), > > VDI_Libs, and a few other neato things. Is the object code (and > > associated libraries) portable from 3.0 -> 3.51? > > To the best of my knowledge. Does anyone claim differently? You shouldn't have any trouble with object code compatibility (including using shared libraries), but between 3.0 and 3.5 they changed from the "old" archive library format to the "new" format. What that meant was that if you had libsomething.a from 3.0 or before, you had to unpack it into individual files (using the old "ar") and then re-archive it into the new format (using the 3.5 ar). For 3.5, they shipped utilities (I think called "3.0ar" and "3.0nm") for just this purpose, but I think they didn't do that for 3.51. (So if you're going from 3.0->3.51, save your own copies of "ar" and "nm".) Of course all the libraries they ship you are already converted, except there was some slip up for "libcvdi.a" (the graphics library), so you have to convert that yourself if you want to use it. (It only takes a couple minutes.) [Note ... I am not connected with UNIXpc development or maintenance.] -- -- Bill Carpenter att!ho5cad!wjc or attmail!bill