From xemacs-m  Thu Jan  2 04:18:43 1997
Received: from sol1.cybernet-ag.net (sol1.cybernet-ag.net [194.221.86.98])
          by xemacs.cs.uiuc.edu (8.8.4/8.8.4) with ESMTP
	  id EAA02520 for <xemacs-beta@xemacs.org>; Thu, 2 Jan 1997 04:18:40 -0600 (CST)
Received: (from aseibert@localhost) by sol1.cybernet-ag.net  id LAA28179; Thu, 2 Jan 1997 11:18:13 +0100 (MET)
Date: Thu, 2 Jan 1997 11:18:13 +0100 (MET)
Message-Id: <199701021018.LAA28179@sol1.cybernet-ag.net>
From: Axel Seibert <aseibert@cybernet-ag.net>
To: xemacs-beta@xemacs.org
Subject: xemacs-19.15b5 under NEXTSTEP

I think I found a patch for the syssignal.h problem under NEXTSTEP;
hopefully I'll find the time tonight to post it.

Apart form that I tried to clean up the mess in src/m/next.h and
src/s/nextstep.h. There are a few things that are in both, and there
are things that go wrong during configure.

One thing is: configure switches rel-alloc on. That breaks the
compilation process. I tracked it down to configure thinking mmap was
available under NEXTSTEP, which it isn't. I haven' t found the culprit
yet.

If anybody got any advice, I'd be gratefull. 

The other thing is, that if you run configure without any arguments,
it finds the configuration to be "mab-next-nextstep" and then says
that xemacs hasn't been ported to mab-next-nextstep. To get it to
compile one has to manually advise configure to use
m68k-next-nextstep. I'm working on this as well.

And then there is the patch to beta6: Do I need rcs now?

Hope you hear from me tonight again :-)

Axel

