Front page | perl.vmsperl |
Postings from June 2002
Craig Berry wrote: !It assumes the kit is in your top-level directory and if you have MMS !rather than MMK you'll need to change that, but I'm sure the !experienced DCL hackers who've been posting test results lately will !have no trouble modifying this as necessary. Here's the procedure: I could not resist the invitation: --- build_devperl.com;-1 Fri Jun 14 12:45:36 2002 +++ build_devperl.com Fri Jun 14 12:47:15 2002 @@ -15,8 +15,12 @@ $ show process/accounting $ configure_step: $ set default [.perl] +$ if f$type(mmk) .nes. "" +$ then build_cmd := mmk +$ else build_cmd := mms +$ endif $ @configure -"Dusedevel" " -"des" $ show process/accounting -$ mmk -$ mmk test +$ 'build_cmd' +$ 'build_cmd' test $ exit I would by the way recommend invoking vmstar with: $ vmstar/extract/verbose/date_policy=none 'tarfile' and note that a lot of folks simply have 'tar' as the foreign command rather than 'vmstar'. Note also that the "-Dusedevel" parameter to @configure is no longer necessary now that patchlevel.h has an even numbered PERL_VERSION: #define PERL_REVISION 5 /* age */ #define PERL_VERSION 8 /* epoch */ #define PERL_SUBVERSION 0 /* generation */ I would nonetheless recommend retaining the "-Dusedevel" for build_devperl once the devel version is started. By the way, perhaps the Smoke script could be adapted for testing out several config options on VMS? Peter Prymmer