At 02:54 PM 5/9/00 +0100, Martin J. Evans wrote:
>mms
>%MMS-F-GWKNOPRN, There are no known sources for the current target
>[.BLIB.ARCH.AUTO.DBI]DRIVER.XST
>
>The directory [.BLIB] and subdirectories were never created by the descrip.mms
>file and no file copies occurred.
>
>I discovered that an mms config creates the directories but the file copies are
>still missing. Then, today when I got around to investigating this properly I
>discovered mms all, appears to do it correct - it surprised me that I had to
>mention all as the target.
I believe what is causing this problem (and it's always been this way for
DBI) is that Unix make utilities search for the 'all' target and build that
first if no target is explicitly specified, whereas MMK and MMS build
whatever target they encounter first in descrip.mms if no target is
explicitly specified. In the case of DBI, this means that it attempts to
build the Perl.xsi target before the requisite file copies, as Martin has
noticed.
The VMS version of MakeMaker as far as I can tell creates dependencies in
the same order as they would be created under Unix, which seems like the
right thing to do until you encounter a case like this. The obvious
workaround is to explicitly specify the all target, but I wonder if we
shouldn't play with MM_VMS.pm so that it puts additional dependencies at the
end rather than the beginning. Anyone have an opinion on this?
_______________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]
