Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!rex!ames!haven!mimsy!mojo!stripes
From: stripes@eng.umd.edu (Joshua Osborne)
Newsgroups: comp.windows.x
Subject: Re: R3 -> R4 - pitfalls for applications built under R3 on Suns ??
Message-ID: <1990Feb19.085336.22484@eng.umd.edu>
Date: 19 Feb 90 08:53:36 GMT
References: <EHO.90Feb16181111@word.Princeton.EDU>
Sender: news@eng.umd.edu (The News System)
Distribution: comp
Organization: Maryversity of Uniland, College Park
Lines: 31

To: eho@clarity.Princeton.EDU
Subject: Re: R3 -> R4 - pitfalls for applications built under R3 on Suns ??
Newsgroups: comp.windows.x
In-Reply-To: <EHO.90Feb16181111@word.Princeton.EDU>
Organization: Maryversity of Uniland, College Park
Cc: 
Bcc: 

In article <EHO.90Feb16181111@word.Princeton.EDU> you write:
>Can anyone give me any advise on this (like things to avoid/workarounds) ?
Of the programs I have tested all the R3 stuff works on a R4 server, some
of it requires that you do a "xset bc" ("Backwords Compatabilty"/"Bug Compat.").
I have not tested too many comerical programs and I have not tested too many
things that I have a R4 version (like xdvi, I use the xditview supplyed w/ R4).

I have also just recompiled alot of R3 stuff under R4 (to take advantage of
shared libs & MIT-COOKIE-1), most of it compiles w/o change, or with just a
"#define XAW_BC" and a few changes to the #include lines...

>I've Sun-3's and Sun-4 (all running SunOS 4.0.1)on my desk and I've gcc-1.35,
>and Emacs 18.55.
Use gcc on the sun 3's, but cc on the 4's, be careful to read the stuff in the
dox about shared libs.

>(Maybe I should wait a little more till more bugs are discovered ?).
If you want, but the whole thing seems less buggie then R3.
-- 
           stripes@wam.umd.edu          "Security for Unix is like
      Josh_Osborne@Real_World,The          Mutitasking for MS-DOS"
      "The dyslexic porgramer"                  - Kevin Lockwood
    Who needs friends when you can sit alone in your room and drink?