Path: utzoo!mnetor!uunet!husc6!uwvax!rutgers!columbia!cunixc!alan
From: alan@cunixc.columbia.edu (Alan Crosswell)
Newsgroups: comp.windows.x
Subject: Re: X.V11R2 on the RT
Message-ID: <480@cunixc.columbia.edu>
Date: 9 Mar 88 19:32:05 GMT
References: <8803031836.AA05252@rover.UMD.EDU>
Reply-To: alan@cunixc.columbia.edu (Alan Crosswell)
Organization: Columbia University
Lines: 33

I've run into a couple of other problems compiling on the RT.  This is
on a system running the Pre-February release of 4.3.  The pre-February
relase is called ACIS 4.3 while the February release (which you have to
pay for again) is called Academic Operating System 4.3.  I wouldn't be
trying to compile X11 on the February release since it comes with it!

The hc man page says that although HC comes with an ANSI pre-processor,
the default is to use cpp.  You have to give the +Hnocpp switch (or something
like that) to get the ANSI preprocessor.

Then, once you give up on getting HC to compile the toolkit (it complains
about not being able to resolve &NULL which is used in the XtOffset macro)
and you try to use pcc (by editing Rt.macros) you will find that X11/Xmd.h
has #if defined(ibm032) && !defined(_pcc_)
    pragma blah blah blah
    #endif
Well, cpp does not define _pcc_ anywhere.  ibm032 does get defined.  So,
you go back to Rt.macros again and add -D_pcc_ to STD_DEFINES (I guess).

Each of the three times I've tried to compile X10 and now that I'm compiling
X11, I've always tried to use HC since it is supposed to generate tighter
code.  I've always gone back to ol' reliable slow horrible forgiving pcc
after fighting HC for a while.  Maybe the February release of AOS 4.3 (sounds
like something that runs on a Cyber to me:-) has finally fixed HC enough to
really build X11.

If an when I get it built on my old, slow (still waiting on that CPU upgrade)
RT running ACIS 4.3 I will post a followup.

Alan Crosswell
ACIS 4.3 Site Coordinator
User Services
Columbia University