From xemacs-m  Thu Apr 24 21:47:26 1997
Received: from pentagana.sonic.jp (jhod@tc-6-097.tokyo.gol.com [203.216.8.97])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id VAA18188
	for <xemacs-beta@xemacs.org>; Thu, 24 Apr 1997 21:47:23 -0500 (CDT)
Received: (from jhod@localhost) by pentagana.sonic.jp (8.7.1+2.6Wbeta4/3.4W3) id LAA00341; Fri, 25 Apr 1997 11:36:44 +0900
To: xemacs-beta@xemacs.org
Subject: Re: 20.2b2 on irix 6.2/n32 ok
References: <19970424220117.17341@iria.mines.u-nancy.fr> <m23esgm9kb.fsf@altair.xemacs.org>
From: jhod@po.iijnet.or.jp (P. E. Jareth Hein)
In-Reply-To: Steven L Baur's message of 24 Apr 1997 13:48:20 -0700
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Date: 25 Apr 1997 11:36:43 +0900
Message-ID: <u4afmn3k1w.fsf@pentagana.sonic.jp>
Lines: 27
X-Mailer: Gnus v5.4.45/XEmacs 20.2(beta1)

Steven L Baur <steve@miranova.com> writes:

> Olivier Galibert <Olivier.Galibert@mines.u-nancy.fr> writes:
> 
> > Provided the changes to src/s/irix6-0.h and src/m/iris4d.h
> > I shown in my previous mail, compile has gone ok and the
> > beast is working fine.
> 
> I haven't applied these to baseline yet because I don't understand how 
> they're supposed to fit in.  Is this n32 environment the way all Irix 6
> systems are supposed to compile XEmacs?

The n32 compiler/library set is the direction SGI wants to go with
their development environment. Supporting it as an option is definatly
a win, as sooner or later the 'o32' environment will vanish the was
coff support vanished in 6.x. However, is this the desired default I can't
answer yet. I've got mine compiled with o32 right now...

> > Having removed motif fixed the instant core with the copy function. Now
> > I need to find whether the bug is in SGI's motif or in xemacs itself.

BTW: Oliver, have you picked up patch 1697? It fixes several Motif
problems.

--Jareth Hein
jhod@po.iijnet.or.jp

