Xref: utzoo comp.unix.i386:6617 gnu.emacs:3210
Path: utzoo!utgpu!watserv1!watmath!uunet!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!dquah
From: dquah@athena.mit.edu (Danny Quah)
Newsgroups: comp.unix.i386,gnu.emacs
Subject: gnu emacs, epoch on iAPX 386
Summary: Fatal error running emacs on Interactive 2.2
Keywords: emacs, Interactive UNIX, core dump
Message-ID: <1990Jul8.225350.20974@athena.mit.edu>
Date: 8 Jul 90 22:53:50 GMT
Sender: dquah@athena.mit.edu
Organization: Economics, Massachusetts Institute of Technology
Lines: 26

[Thanks! to the nice people who've put 386 binaries on tek4310.kent.edu]

	I've gotten a number of things from tek4310.kent.edu and all
(microemacs, bash, and gcc for example) are working great on my
Toshiba T5100 (4M ram, 100M hard disk, 387 installed, Interactive UNIX
2.2 brand spanking new).  Piece by piece I've also put in /usr/local
the emacs and epoch executables.  "file" correctly shows "iAPX 386
executable" on /usr/local/bin/emacs and epoch.  Upon invocation,
however, emacs crashes and burns with

Fatal error (12).Bad system call.

	I take it that this emacs has worked for other people.  What
have I missed?  Anyone know which system call this is?  Have I just
not installed a fateful piece of the OS? [In case it matters I have
SDS, Kernel Configuration, Core Base, File Management, Spell Utilities
installed.]

	If this isn't of general interest, please email rather than
posting.  I'm happy to summarize if I get requests.

--
--Danny (dquah@athena.mit.edu, dquah@dolphin.mit.edu)
Dept. of Economics MIT, E52-274b, Cambridge MA 02139
Voice: (617) 253-0914 Fax: (617) 253-1330
#