Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucsd!sdcsvax!celece!markley
From: markley@celece.ucsd.edu (Mike Markley)
Newsgroups: comp.sys.apollo
Subject: Re: Apollo ANSI standard C?  How close?  Should it matter?
Message-ID: <6732@sdcsvax.UCSD.Edu>
Date: 29 Jun 89 16:56:28 GMT
References: <8906271541.AA06634@scrolls.wharton.upenn.edu> <4203@hacgate.scg.hac.com>
Sender: nobody@sdcsvax.UCSD.Edu
Reply-To: markley@celece.UUCP (Mike Markley)
Organization: UCSD Office of Academic Computing
Lines: 24

In article <4203@hacgate.scg.hac.com> lori@hacgate.scg.hac.com (Lori Barfield) writes:
>I'm not sure how much of the viewgraphs Jim Kumorek of Apollo passed out
>at the Sys Admin Conference in San Diego apply to C, but I'll try to
>weed out appropriate notes.  Hope this helps.
>
lot of stuff deleted...
>
>4.  Current gotcha:  object files don't pass through NFS gateways
>
>	at 10.2, object files will pass through gateways
>
This is not entirely true.  The compilers will not write object
files through an NFS gateway.  The linker will.  Also if you
copy an object file onto an NFS volume it is executable by the
Apollo workstation.  You can put a work-around to this problem
by specifying an -o /tmp/<name> to the cc line and then copying
this file to your current directory and linking it.  This is
what I did and I don't have any problems.

Mike Markley
University of California, San Diego
markley@celece.ucsd.edu
AFTER July 1st
markley@net1.ucsd.edu