Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!ATR-8.HAC.COM!nsche
From: nsche@ATR-8.HAC.COM (Norm Scherer)
Newsgroups: comp.windows.x
Subject: Re:  GCC 1.34 and X11R3 on Sun 3/60
Message-ID: <8906142302.AA06258@atr-8.hac.com>
Date: 14 Jun 89 23:02:33 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 23

I have compiled and run X11R3 using GCC 1.34 on a Sun 3/50 with
no particular problems.  You have probably falled prey to the
problem noted in the README file included with the Purdue.2.0
speedups.

    "Also, using GCC to compile os/4.2bsd/oscolor.c can result in problems
    unless you take corrective measures.  The problem lies with the fact
    that GCC returns structures differently as function values than does
    cc-derived code.  The symptom of this problem is that a GCC-compiled
    server will have totally black (or white) screens with no observable
    text.  To fix the problem, either compile oscolor.c with the regular
    "cc" compiler, or compile the dbm library with gcc and link against
    that.  You can also apply the enclosed dbm-gcc.h.patch file to your
    /usr/include/dbm.h file and compile oscolor.c with gcc as normal."


	Norm Scherer
 	Software Engineering Division
 	Hughes Aircraft Co., Ground Systems Group,
 	Fullerton Ca.
 	(nsche%atr-2s@hac2arpa.hac.com or nsche@atr-2s.hac.com)
 
Opinions are my own, not those of HAC or anyone else I have ever met