Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!allosaur.cis.ohio-state.edu!bob
From: bob@allosaur.cis.ohio-state.edu (Bob Sutterfield)
Newsgroups: comp.windows.x,gnu.gcc
Subject: Re: X.V11R2 xterm all foreground color when compiled with GCC 1.26
Message-ID: <21283@tut.cis.ohio-state.edu>
Date: 2 Sep 88 23:06:53 GMT
References: <20830@tut.cis.ohio-state.edu> <4739@medusa.cs.purdue.edu>
Sender: news@tut.cis.ohio-state.edu
Organization: The Ohio State University Dept of Computer & Information Science
Lines: 23

In article <4739@medusa.cs.purdue.edu> spaf@cs.purdue.edu (Gene Spafford) writes:
|In article <20830@tut.cis.ohio-state.edu> bob@allosaur.cis.ohio-state.edu (Bob Sutterfield) writes:
|>When I compile xterm with gcc, everything is in the foreground color -
|>that is, I get a solid black window.  Compiled with the Sun cc, all is
|>well.  I see this effect with none of the other clients.
|>
|>What did I miss?
|
|You must have missed my postings on this in comp.windows.x:
| [...and the important information...]

Thanks to Spaf and the others who pointed out that I simply had to
compile server/os/4.2bsd/oscolor.c with Sun's cc, because of the
difference between gcc's and pcc's struct-valued function return
conventions.  Someday soon I may make a GNU-compiled libdbm.a so this
step won't be necessary.

Except for oscolor.c, our Suns are running a completely gcc-compiled
window system and client set now, with the Purdue speedups, and all is
well.  The performance improvement is remarkable!
-=-
Zippy sez,								--Bob
I smell a RANCID CORN DOG!