🚀 go-pugleaf

In article <296@adiron.UUCP> tro@adiron.UUCP (Tom Olin) writes:
>I am attempting to use the DECUS C compiler on RT-11 V4.  The
>compile-time environment that I have consists of CC.SAV, AS.SAV, and
>CLIB.OBJ.  Other than a few source files (GREP.C, ECHO.C, etc.), that's
>it.  No documentation of any sort.
>
>When I run CC, I can get it's usage line, but when I attempt to compile
>anything, I get the message "?MON-F-No dev[ice] nnnnnn", where the nnnnnn
>varies, depending on exactly how I enter the command line.  
>	(1) Exactly what is CC complaining about?  What must I do to
>	get it to work?
>
Most likely, the lack of a device logically named 'C'.  ASSIGN SY: C:
will take care of that.  Of course, probably it is looking for
C:STDIO.H as an #include file when it dies.
>	(3) If I can get CC working, I assume I run its output through
>	AS.  Am I correct? 
RU C:CC file.c/A	! will chain from CC to AS automatically and delete
			! the intermediate file.S
Is there anything else I should know about
>	the compiler, such as special LINK options?
>
LINK file,C:(SUPORT,CLIB)/bottom:2000	! will take care of most cases.
		! C programs use lots of stack space in general

>If anybody has some documentation which will answer these questions, I
>would like to make arrangements to receive it.
>
Documentation is available from the DECUS library, and amounts to several
hundred pages.  Either hard copy or RUNOFF source form.  If you have trouble
getting it, ask me for more help.  I suppose a self-addressed stamped
magtape could be dealt with, but the library is the best place to go.


-- 
	carl lowenstein		marine physical lab	u.c. san diego
	{ihnp4|decvax|akgua|dcdwest|ucbvax}	!sdcsvax!mplvax!cdl