Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ncar!ames!lll-lcc!lll-winken!lll-crg.llnl.gov!casey
From: casey@lll-crg.llnl.gov (Casey Leedom)
Newsgroups: comp.windows.x
Subject: xclock -analog broken under Purdue + PurduePlus speed ups
Message-ID: <388@lll-winken.UUCP>
Date: 29 Dec 88 20:19:39 GMT
Sender: usenet@lll-winken.UUCP
Reply-To: casey@lll-crg.llnl.gov (Casey Leedom)
Organization: Lawrence Livermore National Laboratory
Lines: 29


  Well I've perused the news group and there's no other mention of this,
so ...

  I finally bit the bullet and installed the Purdue and PurduePlus speed
ups.  The reviews of the performance enhancements were just too
attractive.  Not even the warning that the PurduePlus speed ups would
break my ability to compile X11.3 with anything but gcc deterred me
(apparently the #else halves of the PurduePlus #ifdef __GNUCC__ code is
not correct) ...

  And, I have to say that the reviews were right.  It's wonderfully
fast.  I recommend them to anyone willing to be committed to compiling X
with gcc and not being able to compile with your native compiler.  Just
be sure that you don't blithely install a new version of gcc without
checking to make sure that it compiles X without bugs ...

  But, on to the main point, everything except xclock -analog seems to be
working.  Not understanding the essential nature of the changes to the
server, I'm totally in the dark and unable to find the problem myself.
In analog mode, all line segment seem to be rooted to the left hand edge
of the window giving a ``Death Star'' like appearance.  Very pretty and
surrealistic, but not really useful.

  Salient details: Purdue, PurduePlus, and MIT patches 1, 2, and 3
installed; compiling with GNU cc 1.32.  Sun 3/280, 2/50, 3/60.  Sun OS
3.5.

Casey