On Dec 22, 2012, at 8:50 AM, "John E. Malmberg" <malmb...@encompasserve.org>
wrote:
> On 12/22/2012 8:07 AM, Craig A. Berry wrote:
>
>>>
>>> MCR SYS$DISK:[]generate_uudmap.exe uudmap.h bitcount.h mg_data.h
>>> Action did not update target BITCOUNT.H
>>> Action did not update target MG_DATA.H
>>>
>>> I'm not sure if this is a problem or not.
>>
>> Don't think so. MMS and MMK feel the need to tell you that they didn't do
>> anything.
>
> It is a bug in MMS or MMK (possibly both) depending on where you saw it.
>
> The tool thinks it was told to create "BITCOUNT.H" and did not find it
> because "bitcount.h" was actually created.
I don't think that has anything to do with it. Here's a simple reproducer
where everything is in upper case:
$ type descrip.mms
ALL : BITCOUNT.H MG_DATA.H UUDMAP.H
@ CONTINUE
BITCOUNT.H MG_DATA.H : UUDMAP.H
@ CONTINUE
UUDMAP.H :
@ COPY/NOLOG NL: UUDMAP.H
@ COPY/NOLOG NL: BITCOUNT.H
@ COPY/NOLOG NL: MG_DATA.H
$ mmk
%MMK-I-ACTNOUPD, action did not update target MG_DATA.H
I think it has to do with the double target and the fact that it knows it did
not take any actions to update that target. It seems to be harmless.
________________________________________
Craig A. Berry
mailto:craigbe...@mac.com
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
