Here are the results:

@test_implicit_rule.com
%MMK-I-OPENDESC, reading description file HOME$SYSGRP:[JWPARKER.PERL]IMPLICIT_RU
LE.MMS;1
%MMK-I-CHECKUPD, checking need to update target TESTME.BAZ
%MMK-I-TRGLKUF, lookup for target TESTME.BAZ failed - update required
-RMS-E-FNF, file not found
%MMK-I-CHECKUPD, checking need to update target SIDETRACK.BAR
%MMK-I-TRGLKUF, lookup for target SIDETRACK.BAR failed - update required
-RMS-E-FNF, file not found
%MMK-I-PERFUPD, performing actions to update SIDETRACK.BAR
copy _NLA0: SIDETRACK.BAR
%MMK-I-TRGNUPD, target TESTME.BAZ is out of date - update required
%MMK-I-PERFUPD, performing actions to update TESTME.BAZ
copy TESTME.bar TESTME.baz
%COPY-E-OPENIN, error opening HOME$SYSGRP:[JWPARKER.PERL]TESTME.BAR; as input
-RMS-E-FNF, file not found
%MMK-F-ERRUPD, error status %X1067109A occurred when updating target TESTME.BAZ

Thanks,

John

At 03:08 PM 2/18/2005, you wrote:
>At 2:23 PM -0600 2/18/05, John W. Parker wrote:
>
>>- MMK V3.9-10
>
>
>>CC/DECC /Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj
>>/NOANSI_ALIAS/floa
>>t=ieee/ieee=denorm_results/Define=("VERSION=""1.99_01""","XS_VERSION=""1.99_01""
>>")/Include=([--],[.Encode])/NoList  ENCODE.c
>>%CC-F-OPENIN, error opening PERLKIT:[SOURCE.EXT.ENCODE]ENCODE.C; as input
>>-RMS-E-FNF, file not found
>>%MMK-F-ERRUPD, error status %X10B9002C occurred when updating target 
>>ENCODE.OBJ
>>%MMK-F-ERRUPD, error status %X1C14803C occurred when updating target DYNEXT
>>Terminated at BUILD due to %NONAME-F-NOMSG, Message number 1C14803C
>>
>>Any ideas on what could be wrong?  I have include an attachment of the output
>>of build_perl.com in hopes someone could see what I could not.
>
>Run the attached command procedure and let me know if you get an error.  There 
>was a problem in MMK 3.9-9 that was supposedly fixed in 3.9-10, but I have not 
>tried it myself yet.
>-- 
>________________________________________
>Craig A. Berry
>mailto:[EMAIL PROTECTED]
>
>"... getting out of a sonnet is much more
> difficult than getting in."
>                 Brad Leithauser

Reply via email to