Path: utzoo!attcan!uunet!lll-winken!ames!pasteur!ucbvax!tut.cis.ohio-state.edu!bloom-beacon!ATHENA.MIT.EDU!jik
From: jik@ATHENA.MIT.EDU (Jonathan I. Kamens)
Newsgroups: comp.windows.x
Subject: X11 R3 on RTs (again)
Message-ID: <8905040515.AA12979@PIT-MANAGER.MIT.EDU>
Date: 4 May 89 05:15:34 GMT
References: <4544@psuvax1.cs.psu.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 36


   Date: 3 May 89 13:02:51 GMT
   From: shire.cs.psu.edu!ehrlich@psuvax1.cs.psu.edu
   Organization: Department of Computer Science, Penn State University
   Sender: xpert-request@expo.lcs.mit.edu

   After obtaining the `new' X11 R3 server code from expo I tried to make
   World only to discover that the MetaWare High-C compiler version 1.4r
   gets extremely upset with the XtOffset macro defined in
   X11/Instrinsic.h and complains with errors like the following every
   time the macro is used:

   E "Composite.c",L36/C16:
   |    Must be a compile- or load-time computable expression.
   Object module not generated.

Yeah, we had this problem in a major way here at Athena.  The other
problem is that developers of Xt applications that use XtOffset lose
in a major way since our default compiler is hc and we had to give
specific instructions to tell people to use pcc.

There are two possible solutions to the problem:

1. Get the new hc (hc 2.1o, I think, is the most recent version), in
   which this problem is fixed.

2. Augment your Imakefile rules for RT's so that each directory gets
   compiled first with "make -k CC=hc" and then again with "make -k
   CC=pcc."  This way, any files that didn't build properly the first
   time because of the XtOffset will build properly the second time
   through.

Jonathan Kamens			              USnail:
MIT Project Athena				410 Memorial Drive, No. 223F
jik@Athena.MIT.EDU				Cambridge, MA 02139-4318
Office: 617-253-4261			      Home: 617-225-8218