I've been building Perl on AXP 7.1 machines this week, and finding a
bunch of quirks (mostly filesystem-related, but not all).
In the process, it's pretty common for files in the "main" Perl to get
updated, requiring that subsequent module builds create an updated
DESCRIP.MMS.
While an updated DESCRIP.MMS *is* generated (and we tell the user to
re-run MMS/K), we then continue merrily along using the old one.
A subsequent MMS/K run (new DESCRIP.MMS) will then find all the
EXEs, etc. updated and won't bother regenerating them.
Kinda defeats the point of the update, doesn't it?
Soo...here's a tiny little patch to lib/ExtUtils/MM_VMS.PM
to *abort* the MMS/K run after a new DESCRIP.MMS is generated.
The spawn/etc. nonsense is to get MMS/K to accept the error code
(just "exit 44" or setting $STATUS don't seem to work).
--- lib/ExtUtils/MM_VMS.pm-pre_abort Thu May 4 16:05:41 2000
+++ lib/ExtUtils/MM_VMS.pm Thu May 4 16:05:15 2000
@@ -1940,6 +1940,7 @@
$(PERL) "-I$(PERL_ARCHLIB)" "-I$(PERL_LIB)" Makefile.PL ],join('
',map(qq["$_"],@ARGV)),q[
$(NOECHO) $(SAY) "$(MAKEFILE) has been rebuilt."
$(NOECHO) $(SAY) "Please run $(MMS) to build the extension."
+ $(NOECHO) spawn/nolog/nonotify exit 44
];
join('',@m);
--
Drexel University \V --Chuck Lane
----------------->--------*------------<[EMAIL PROTECTED]
(215) 895-1545 / \ Particle Physics [EMAIL PROTECTED]
FAX: (215) 895-5934 /~~~~~~~~~~~ [EMAIL PROTECTED]
