Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!olivea!apple!agate!ucbvax!dog.ee.lbl.gov!nosc!humu!pilikia!art
From: art@pilikia.pegasus.com (Art Neilson)
Newsgroups: comp.mail.mush
Subject: Re: Need Help with Mush 7.2.2 and SCO UNIX submit.
Message-ID: <1991Apr25.171927.3778@pilikia.pegasus.com>
Date: 25 Apr 91 17:19:27 GMT
References: <1991Apr24.053145.1083@rfengr.com>
Organization: Pilikia, Honolulu
Lines: 21

In article <1991Apr24.053145.1083@rfengr.com> rfarris@rfengr.com (Rick Farris) writes:
>I have a couple of observations to make about compiling Mush v7.2
>(as just posted to c.s.m) under SCO UNIX 3.2V2.0 and then a question.
>
>First, mush compiled very easily, with a couple of minor mods: I
>had to hunt up a definition of "EACCESS".  I finally found it in
>/usr/include/sys.s (yes, sys.s), which is not really an includable 
>file.  I ended up just grabbing the
>
>	#define EACCESS          0x2528
>
>line from sys.s and stuffing it in at the top of lock.c.  The

are you sure this isn't just a misspelling, EACCESS looks remarkably
close to EACCES, defined in errno.h.  After eyeballing the code in
lock.c which uses EWOULDBLOCK (EWOULDBLOCK is defined as EACCESS
ifdef M_UNIX, EAGAIN for other SysV's) it really looks as if this 
is the case.
-- 
Arthur W. Neilson III		| INET: art@pilikia.pegasus.com
Bank of Hawaii Tech Support	| UUCP: uunet!ucsd!nosc!pilikia!art