develooper Front page | perl.perl5.porters | Postings from January 2001

Re: subversion undef on VMS (was Re: [ID 20001218.033] Not OK: perlv5.6.1 +v5.6.1-TRIAL1 on VMS_AXP V7.2-1)

Thread Previous | Thread Next
From:
Peter Prymmer
Date:
January 17, 2001 10:45
Subject:
Re: subversion undef on VMS (was Re: [ID 20001218.033] Not OK: perlv5.6.1 +v5.6.1-TRIAL1 on VMS_AXP V7.2-1)
Message ID:
Pine.OSF.4.10.10101171038000.289071-100000@aspara.forte.com


On Wed, 17 Jan 2001, Jarkko Hietaniemi wrote:

> On Tue, Jan 16, 2001 at 11:38:46PM -0600, Craig A. Berry wrote:
> > At 10:55 PM -0600 12/18/00, Craig A. Berry wrote:
> > >At 4:55 PM -0500 12/18/00, Dan Sugalski wrote:
> > >>At 03:52 PM 12/18/00 -0600, Jarkko Hietaniemi wrote:
> > >>>  > Summary of my perl5 (revision 5.0 version 6 subversion undef) 
> > >>>configuration:
> > >>>
> > >>>subversion undef?
> > >>
> > >>Looks like configure.com needs another whacking about...
> > >
> > >The problem appears to be the following commented-out line in configure.com:
> > >
> > >$! WC "PERL_SUBVERSION='" + subversion + "'" ! VMS specific to 
> > >descrip_mms.template
> > >
> > >Anyone know why this is commented out or what descrip_mms.template
> > >has to do with it?
> > 
> > It's been almost a month, I haven't heard a reply to this question,
> > and our subversion is still missing.  I say we put it back in and place
> > the burden of explanation on whoever commented it out in the first
> > place.
> 
> It seems to have been the "Change 6613 by jhi@alpha on 2000/08/14
> 13:45:33", "VMS configure.com update continues."  I *think* I got
> it from Peter Prymmer, unfortunately I didn't seem to document it
> back then...

It might have come from me although I don't recall it very well.

It might have been fallout from a change in patchlevel.h in the 5.6.0
release of some sort (confusion over the intent of subversion vs
api_subversion?). FWIW here are the versions that a unix box has:

% grep -i version config.sh
api_subversion='0'
api_version='5'
api_versionstring='5.005'
ccversion='V5.6-082'
gccversion=''
ignore_versioned_solibs=''
inc_version_list='5.005/alpha-dec_osf 5.005'
inc_version_list_init='"5.005/alpha-dec_osf","5.005",0'
pm_apiversion='5.005'
subversion='0'
version='5.7.0'
versiononly='undef'
xs_apiversion='5.005'
PERL_VERSION=7
PERL_SUBVERSION=0
PERL_API_VERSION=5
PERL_API_SUBVERSION=0

The other possiblilty is that it was to head off an unitialized variable
warning in DCL.  For example:

% type subver.com
$ WC := write sys$output
$! without initialization
$ WC "subversion='" + subversion + "'"
$! with initialization to empty string
$ subversion = ""
$ WC "subversion='" + subversion + "'"
$! with initialization to nonempty string
$ subversion = "0"
$ WC "subversion='" + subversion + "'"
% @subver
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
 \SUBVERSION\
subversion=''
subversion='0'

And it could very well be that a bug in configure.com prevents the
$ subversion="0" assignment from kicking in.

Perhaps another thing worth testing is what munchconfig.exe and
descrip.mms would do with:

PERL_SUBVERSION=0

rather than with the 'single quotation marks':

PERL_SUBVERSION='0'

I'll try to look into it.

Peter Prymmer



Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About