Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!van-bc!jtc From: jtc@van-bc.UUCP (J.T. Conklin) Newsgroups: comp.unix.xenix Subject: Re: SCO stopping enhancements for Xenix? Keywords: SCO Xenix Message-ID: <213@van-bc.UUCP> Date: 1 Mar 90 02:49:31 GMT References: <1313@polari.UUCP> Reply-To: jtc@van-bc.UUCP (J.T. Conklin) Organization: Wimsey Associates Lines: 35 In article <1313@polari.UUCP> corwin@polari.UUCP (Don Glover) writes: >No, BUT what has just happened indicates that this might be the case. In >november I was told by a tech support rep that there would be an upgrade >to the development system "in the first quarter of 90", this upgrade was >supposed to have brought the xenix compiler up to the equivalent of the >MicroSnot 5.1 compiler. Today I was told there will be no upgrade for the >xenix development system, if I want to upgrade I have to go to Unix (and >as a result pay through the nose for the upgrade). I hope this is not true -- First no NFS and then no DS upgrade for XENIX. This ties my hands as a developer, and I can't afford to orphan XENIX just like that. I would like to store the source code repository on a central NFS fileserver and compile the code on the host for which it is targeted. Cross compilation is an option, but would be a real pain for device driver work. This will really slow down the edit-compile- link-test cycle. Perhaps I should go on sabbatical, licence, port and distribute a NFS for XENIX; then and spend some time cleaning up the GNU C compiler. --jtc -- J.T. Conklin ...!{uunet,ubc-cs}!van-bc!jtc, jtc@wimsey.bc.ca