Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!husc6!cmcl2!rutgers!ucla-cs!zen!ucbvax!hplabs!pyramid!chris
From: chris@pyrps5 (Chris Guthrie)
Newsgroups: comp.windows.x,comp.sys.pyramid
Subject: Re: Porting X windows to Pyramid
Message-ID: <4819@pyramid.pyramid.com>
Date: Wed, 12-Aug-87 19:46:43 EDT
Article-I.D.: pyramid.4819
Posted: Wed Aug 12 19:46:43 1987
Date-Received: Sat, 15-Aug-87 04:53:18 EDT
Sender: daemon@pyramid.pyramid.com
Reply-To: chris@pyrps5.UUCP (Chris Guthrie)
Organization: Pyramid Technology Corp., Mountain View, CA
Lines: 35
Keywords: X windows Pyramid
Summary: Pyramid release/mailing list
Xref: mnetor comp.windows.x:1244 comp.sys.pyramid:46

I'm working on X for Pyramid so I thought I'd give some information
and a quick note about my solution to the XDraw bug.  

I've spent the last week bringing up most of the X10R4 stuff under
Pyramid's OSx 4.0 system.  I hope to have an unsupported release ready
in about a week which will contain most of the main X sources and
some contributed software.  This will be for the Pyramid client end.
It won't include code for any of the servers (although I'm using a
Sun 3/50).  For more information about the release you should
give me a call.  My phone number is below.

I'd also like to set up a mailing list here for sites running X on
their Pyramids.  I hope this can allow some discussions about problems
and directions for X10 and X11 on the Pyramids.  Please drop me a line
if you want to be added.  See below for my net address.

Finally some information about porting X to the Pyramid.  The standard
C compiler pads structures which contain shorts and chars so that it
remains on a four-byte boundary.  This causes problems with the X
protocol since vertices are three shorts and four get sent.

The solution I arrived at was to compile all the X source using the
'-q' flag which prevents the extra padding.  This seems to have worked
for everything but xterm.  In xterm's main.c there is an ioctl to grab
the current tty chars (TIOCGETC).  Unfortunately, the tchar structure
is padded in libc and the kernel, but not in xterm when the -q flag is
used.  I seem to have gotten around this by compiling main.o without
the -q flag and everything else with it.  So far I haven't found
any other problems.  This seems to be the simplest way to compile it
without changing code.

	 Chris

Chris Guthrie  {allegra,cmcl2,decwrl,hplabs,ut-sally,utzoo}!pyramid!chris
Pyramid Technology Corp, Mountain View, CA  +1 415 965 7200