Dan asked:
>Can you try the simple one with output redirection? I don't suppose we're
>lucky enough to have this fail like a good program with debugging built in...
Here ya go...
$ MCR Sys$Disk:[]miniperl.exe -e "print 'hello'" > foo.bar
$ type foo.bar
hello
$
Question: can I build with debugging at this point by just typing
mms/macro=("__DEBUG__=1")
or do I in fact need to reconfigure? I will try to reconfigure,
but I'd like to know if it's even necessary. Thanks.
Peter Prymmer
P.S. If you simply type that mms command it relinks a DGBMINIPERL.EXE but
the descrip.mms then trys to run `mcr sys$disk:[]miniperl [.vms]writemain.pl`
and that fails again (note that miniperl.exe was not relinked).
P.P.S. Here was the tail end of the build configed to be a debug build:
Link /Trace/Debug/Map/Full/Cross/NoDebug/Trace/NoMap/NoFull/NoCross/Exe=SYS$DISK
:[]MINIPERL.EXE miniperlmain.obj, DBGlibperl.olb/Library/Include=globals
,[]crtl.opt/Options
MCR Sys$Disk:[]miniperl.exe "-I[.lib]" [.VMS]Writemain.pl "DynaLoader Socket"
Fatal VMS error (status=114762) at DKB100:[VMSPERL]VMS.C;1, line 4653.
%RMS-E-DNF, directory not found
-NONAME-W-NOMSG, Message number 00000000
%MMS-F-ABORT, For target PERLMAIN.C, CLI returned abort status: %X0001C04A.
-RMS-E-DNF, directory not found
OK so here is a run:
$ miniperl :== $Sys$Disk:[]miniperl.exe
$ DEBUG/KEEP
OpenVMS Alpha DEBUG Version V7.1-000
DBG> RUN/COMMAND="miniperl"/ARGUMENTS="""-I[.lib]"" [.VMS]Writemain.pl ""DynaLoader
Socket"""
Fatal VMS error (status=114762) at DKB100:[VMSPERL]VMS.C;1, line 4653.
%RMS-E-DNF, directory not found
-NONAME-W-NOMSG, Message number 00000000
DBG> GO
%DEBUG-W-NOPROGRAM, function GO requires a running program.
DBG> quit
Suggestions?
