At 12:02 PM 4/18/2001 -0700, Peter Prymmer wrote:
>On Wed, 18 Apr 2001, Martin Vorlaender wrote:
>
>>
>> Errr, wait a moment:
>>
>> $ write sys$output f$message(%X10B90003)
>> %CC-I-NORMAL, normal successful completion
Doh! Of course an informational doesn't halt the compiler. I suspect the
success status we are seeing indicates "compiled with informational
messages" or similar.
>> $ IF compile_status .EQ. %X10B90003 THEN compile_status = good_compile !!!
>> $ GOSUB just_mcr_it
>> $ longdblsize = tmp
>> $ d_longdbl = "define"
>> $ echo "Your long doubles are ''longdblsize' bytes long."
>> $ ENDIF
Much better. Is there any successful compile status that we *don't* want to
be considered a good compile? Or in other words why check for a specific
status rather than success?
Perhaps we need to modify it to something like the following:
># install ought not need a source, but it doesn't work if one's not
># there. Go figure...
>install : $(MINIPERL_EXE)
> @ @perl_setup.com
> If F$TrnLnm("Sys") .nes. "" Then Deass SYS
> create/directory perl_root:[lib]
This breaks if perl_root:[000000] does not exist yet. I seem to remember we
require its creation prior to installation in the docs, but I don't think
it's actually necessary in the current incarnation of installperl, at least
for the non-CLD case.
> copy $(DBG)perl$(E) perl_root:[000000]
> copy $(DBG)perlshr$(E) perl_root:[000000]
> $(MINIPERL) installperl
>
>And make suitable changes to installperl so as not to double install
>perl.exe and perlshr.exe (I suspect it'd be nice to avoid PURGE).
It generally checks dates as well as existence before moving files.
