Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!rutgers!psuvax1!schwartz@shire.cs.psu.edu From: schwartz@shire.cs.psu.edu (Scott Schwartz) Newsgroups: comp.windows.x Subject: Gcc 1.34? Keywords: X11R3 Message-ID: <4333@psuvax1.cs.psu.edu> Date: 3 Mar 89 22:11:20 GMT References: <13578@duke.cs.duke.edu> <13678@duke.cs.duke.edu> <13724@duke.cs.duke.edu> Sender: news@psuvax1.cs.psu.edu Reply-To: schwartz@shire.cs.psu.edu (Scott Schwartz) Organization: Pennsylvania State University, Computer Science Lines: 12 In-reply-to: ndd@romeo.cs.duke.edu (Ned D. Danieley) In article <13724@duke.cs.duke.edu>, ndd@romeo (Ned D. Danieley) writes: >Okay, I got several answers. It turns out that gcc 1.33 works just >fine, with the exception of oscolor.c and rgb. I suspect that these would >work, too, if I had applied the dbm fix suggested in the Purdue >speedup notes. I hate to ask, but, has anyone tried gcc 1.34? I am thinking about building R3+purdue2.1 with it, but would like to know if anyone has had bad results with this combination before I start on it. (The platform is Sun3/Sun4.) -- Scott Schwartz