At 5:00 PM -0700 4/20/00, [EMAIL PROTECTED] wrote:
>Craig A. Berry wrote:
> > 1). The Config variable 'version' is documented in Config.pm but it
> > does not exist in my build.

>Dan and I patched around this a couple of times IIRC.

Well, looks like you guys did the hard part and forgot the easy part.
All this stuff is collected but never written out, and I wouldn't
swear that I've found all the missing ones.  Does this look right?:

--- vms/subconfigure.com;-0     Sun Mar 19 01:18:17 2000
+++ vms/subconfigure.com        Thu Apr 20 19:58:56 2000
@@ -4009,6 +4009,10 @@
 $ WC "libc='" + perl_libc + "'"
 $ WC "xs_apiversion='" + version + "'"
 $ WC "pm_apiversion='" + version + "'"
+$ WC "version='" + version + "'"
+$ WC "revision='" + revision + "'"
+$ WC "patchlevel='" + patchlevel + "'"
+$ WC "subversion='" + subversion + "'"
 $ WC "PERL_VERSION='" + patchlevel + "'"
 $ WC "PERL_SUBVERSION='" + subversion + "'"
 $ WC "pager='" + perl_pager +

That yields the following in config.sh; I'm building with the result now.

xs_apiversion='5_6_0'
pm_apiversion='5_6_0'
version='5_6_0'
revision='5'
patchlevel='6'
subversion='0'
PERL_VERSION='6'
PERL_SUBVERSION='0'

> > 2).  The Config variable 'arch' is neither documented nor exists,
>
>Bummer - does putting a
>
>arch='VMS-AXP'
>
>line into config.sh before the initial mms to build perl help?

It turns out 'arch' existed in 5.005 but must have been deprecated;
it's probably best to patch installperl to use 'archname'.

> > 3).  After hacking around the previous two problems, I'm stuck on a
> > stupid array problem
>
>$ type tt.pl
>@a1 = ('XXXa','XXXb', 'XXXc');
># @array = map { s|^XXX||i } @a1;
>@array = grep { s|^XXX||i } @a1;
>print "@array\n";
>$ perl tt.pl
>a b c

Thanks, and to Brad for the explanation.  Whoever wrote the
equivalent part of installperl was probably thinking grep and wrote
map.  It does make me wonder whether this part of the install ever
worked. 

I hope to have a patch out soon with all this stuff resolved.
-- 
____________________________________________
Craig A. Berry                   
mailto:[EMAIL PROTECTED]

Reply via email to