On Sat, 26 Oct 2013, Brian Schenkenberger, VAXman- wrote:
Cory Smelosky <b4 at gewt.net> writes:
Evening,
After a little more fiddling I have determined for sure that something
isn't in a table it should be in.
MOIRA::CSMELOSKY$ run dka0:[vms$common.sysexe]decc$compiler
%CLI-F-SYNTAX, error parsing 'VCG$VERSION'
-CLI-E-ENTNF, specified entity not found in command tables
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name routine name line
rel PC abs
PC
7FF64BB9
7FF64BB9
7FF649BF
7FF649BF
7FF644E0
7FF644E0
001CB692
001CB692
0019B0ED
0019B0ED
00199CEA
00199CEA
00194F5A
00194F5A
COMPILE cc_driver 52136
00000247
0018F69F
(I just did that for a test...doing a full reinstall won't help. How
would I manually toss it in to DCLTABLES?)
The installation should add "CC" (the C Compiler) command to DCLTABLES.EXE.
Make sure that you have only one DCLTABLES.EXE in SYS$COMMON:[SYSLIB].
Reinstalling the compiler THIS time worked. No idea why it didn't the other 2
times...
You can not simply RUN the C compiler executable because it will look for
command information via CLI$routines/SYS$CLI callbacks. You *might* get
away with $ MCR DKA0:[VMS$COMMON.SYSEXE]DECC$COMPILER not giving you the
stack dump traceback but gawd only knows what qualifier defaults you will
be given.
When you have the C Compiler installed, try:
$ CREATE HELLO.C
#include <stdio.h>
main() { printf("Hello World\n");}
^Z <== Ctrl/Z to exit
$ CC HELLO
$ LINK HELLO
$ RUN HELLO
FYI, You also require a PAK for the DEC C compiler.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects