From xemacs-m  Thu Jan  9 01:40:37 1997
Received: from pentagana.sonic.jp (root@tokyo-05-175.gol.com [202.243.51.175])
          by xemacs.cs.uiuc.edu (8.8.4/8.8.4) with ESMTP
	  id BAA15581 for <xemacs-beta@xemacs.org>; Thu, 9 Jan 1997 01:40:35 -0600 (CST)
Received: from sonic.co.jp (mother.sonic.jp [194.93.1.1]) by pentagana.sonic.jp (8.7.1+2.6Wbeta4/3.4W3) with ESMTP id QAA12040; Thu, 9 Jan 1997 16:40:48 +0900
Received: from pentagana ([194.93.1.69]) by mother.sonic.jp with SMTP
	(1.40.112.4/16.2) id AA038945516; Thu, 9 Jan 1997 16:38:36 +0900
Sender: jhod@po.iijnet.or.jp
Message-Id: <32D4A0FE.4841C814@po.iijnet.or.jp>
Date: Thu, 09 Jan 1997 16:40:46 +0900
From: Jareth Hein <jhod@po.iijnet.or.jp>
Organization: Sonic Software Planning, Tokyo
X-Mailer: Mozilla 3.01 (X11; I; Linux 2.1.16 i586)
Mime-Version: 1.0
To: Martin Buchholz <mrb@Eng.Sun.COM>
Cc: Karel Zuiderveld <Karel.Zuiderveld@cv.ruu.nl>, xemacs-beta@xemacs.org
Subject: Re: 20.0-b34: XIM problems on Irix 6.3
References: <199701082010.VAA14563@wodan.cv.ruu.nl> <199701082106.NAA21514@xemacs.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Martin Buchholz wrote:
> 
> Sounds like your cpp doesn't grok #elif.  Given that it's hard to
> believe there's no native SGI solution to this, SGI folks should
> investigate further - does CPP=cc -E give the  desired result?
> 
> Here's the code in Makefile.in.in:
> 
> #ifndef HAVE_XIM
> #define INPUT_METHOD_X_OBJS
> #elif defined(XIM_MOTIF)
> #define INPUT_METHOD_X_OBJS input-method-motif.o
> #else
> #define INPUT_METHOD_X_OBJS input-method-xlib.o
> #endif
> 
> Probably all the elif's should be rewritten to use, eg.
> 
> #ifndef HAVE_XIM
>   #define INPUT_METHOD_X_OBJS
> #else
>   #if defined(XIM_MOTIF)
>     #define INPUT_METHOD_X_OBJS input-method-motif.o
>   #else
>     #define INPUT_METHOD_X_OBJS input-method-xlib.o
>   #endif
> #endif
> 
> but that upsets the XEmacs maintainers' fragile sense of esthetics...
> 
> Brand new SGI's simply can't be this broken.
>

Unfortunatly, I have reported this 'misfeature' to SGI, and they
responded that their CPP is KNR compliant only, and is likely to stay
that way. I believe I reported this to the list here before I left on
vacation, but maybe it didn't get through. Yet another reason not to use
CPP on Makefiles, eh?


--Jareth Hein

