At 2:08 PM -0700 5/12/00, [EMAIL PROTECTED] wrote:
> > >The install went without errors, but ended with:
>> > %MMK-I-ACTNOUPD, action did not update target INSTALL
>>
>> I saw this too. I have a feeling there is no tangible thing (file
>> system object) MMS/K can check to see if the INSTALL target is
>> up-to-date. Thus it's probably just telling you that it is finished
>> updating the INSTALL target but has no way to record the fact.
>
>Sure there is. Does PERL_ROOT:[000000]$(BINARY_NAME).$(BINARY_TYPE) exist?
>If so then perl was probably installed.
Hmm. Here's the relevant snippet from descrip.mms:
# 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
$(MINIPERL) installperl
It doesn't look like there are any file system objects to the left of
the colon. If we add a dependency, I wonder if we wouldn't want a
dummy file that gets copied to the install directory at the end of
the install rather than the Perl binary, which is one of the first
things copied. That way a failed or interrupted installation would
not report being up to date. Then we'd need to document that a
reinstall should use MMK/FORCE or the user should delete the dummy
file.
--
____________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]
