develooper Front page | perl.vmsperl | Postings from June 2002

another snapshot today (was RE: possible VMS v5.5 fix...)

Craig A. Berry
June 14, 2002 08:27
another snapshot today (was RE: possible VMS v5.5 fix...)
Message ID:
At 1:37 PM -0700 6/13/02, Bohan, Larry wrote:
> When RC2 hits the streets, I'll comb though thru these 2 tests
> better detail.  My interest in RC1 had primarily been a 1st pass,
> see how easy it was to rebuild various extensions (30-45 of 'em),
> and take notes on what work-arounds were needed.

All combing appreciated.  However, the thing about a release
candidate is that the final release could follow very quickly unless
problems are reported so it's possible we could miss our chance to
fix something.  There is a new snapshot today that includes the VMS
changes that have been posted here over the last few days:


If you are building on VAX, you may also find that the following
patch, not yet included in the snapshot above, helps dodge D_FLOAT
overflow in some of the tests:

--- pp.c;-0     Fri Jun  7 09:24:27 2002
+++ pp.c        Fri Jun 14 00:45:34 2002
@@ -956,6 +956,7 @@
                             result *= base;
                             /* Only bother to clear the bit if it is set.  */
                             power &= ~bit;
+                            if (power == 0) break; /* don't square base again if we're done */
[end of patch]

You can always find the latest snapshot (usually every other day or
so) by going to the end of the list here:


Each snapshot is available in .tbz format, which is a smaller
download but requires bzip2 to unpack, and in .tgz format, which uses

You can find out what changes have been applied recently by going to


and choosing "Show recent patching activity".

I have a command procedure I use to configure, build, and test a
development snapshot.  It saves me a lot of time baby-sitting the
process plus I get a log of everything that happened.  I'll use it to
build today's snapshot like so:

$ submit build_devperl/param=perl_17238.tgz

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:

====== =====
$ if p1 .eqs. "" then goto configure_step
$ set verify
$ ziptype = f$parse(p1,,,"type") - "."
$ goto unpack_'ziptype'
$ unpack_tgz:
$ gunzip 'p1'
$ goto unpack_tar
$ unpack_tbz:
$ bzip2 -d 'p1'
$ goto unpack_tar
$ unpack_tar:
$ show process/accounting
$ tarfile = f$parse(p1,,,"name") + ".tar"
$ vmstar -xf 'tarfile'
$ show process/accounting
$ configure_step:
$ set default [.perl]
$ @configure -"Dusedevel" " -"des"
$ show process/accounting
$ mmk
$ mmk test
$ exit
====== end =====

Craig A. Berry

"... getting out of a sonnet is much more
 difficult than getting in."
                 Brad Leithauser Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About