Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!vicorp!Uuunet Newsgroups: comp.windows.x Subject: Re: R3 -> R4 - pitfalls for applications built under R3 on Suns ?? Message-ID: <1990Feb24.112113.17368@vicorp.uu.net> Date: 24 Feb 90 11:21:13 GMT Sender: Uuunet@vicorp.uu.net (UUNET) Organization: Maryversity of Uniland, College Park Lines: 23 In-Reply-To: To: eho@clarity.Princeton.EDU In article 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?