Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!mcsun!ukc!acorn!steve
From: steve@acorn.co.uk (Steve "Daffy" Hunt)
Newsgroups: comp.windows.x
Subject: Re: syscalls in XView
Keywords: XView
Message-ID: <837@acorn.co.uk>
Date: 20 Sep 89 14:29:12 GMT
References: <1354@ole.UUCP>
Reply-To: steve@acorn.UUCP (Steve "daffy" Hunt)
Organization: Acorn Computers Ltd, Cambridge, UK
Lines: 22

In article <1354@ole.UUCP> yanagida@ole.UUCP (Bruce A. Yanagida) writes:
>
>XView defines its own "fcntl", "read", and "select" functions and  makes
>use of the "syscall" facility  to get to the  real system calls.   Since
>Apollo SR10.1  does not  have "syscall",  I'm stuck!   Anyone  have  any
>suggestions on how to get around this problem?  If I had source code for
>the system, I  could insert the  real code  in place of  syscall, but  I
>don't.  Am I out of luck?

I had a similar problem when porting XView to Acorn's RISCiX (BSD)
system.  Your best bet in the short term is to disassemble your
libc and find the system call wrappers for the three functions
concerned.  Duplicate this code with new names such as real_fcntl, etc.
Call these in place of the three references to syscall().

Now, in the long term:

Would anyone at Sun care to comment on the way the notifier has
been written?  Is this part of XView going to be implemented in
a more portable fashion for later releases?

					Steve Hunt.