Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!apple!sun-barr!rutgers!mit-eddie!apollo!kumorek
From: kumorek@apollo.COM (James Kumorek)
Newsgroups: comp.sys.apollo
Subject: Re: Apollo ANSI standard C?  How close?  Should it matter?
Message-ID: <445bb0a6.19451@apollo.COM>
Date: 11 Jul 89 15:47:00 GMT
References: <8906271541.AA06634@scrolls.wharton.upenn.edu> <4203@hacgate.scg.hac.com> <6732@sdcsvax.UCSD.Edu>
Organization: Apollo Computer, Chelmsford, Mass.
Lines: 28

In article <2821 of comp.sys.apollo> markley@net1.ucsd.edu 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.

Note that the original message said that it was the next release of the compilers,
not a current release, that will enable the compilers to write thier binaries over
NFS links.

Jim Kumorek
Apollo Computer
kumorek@apollo