During the configuration process, the Config items version, revision, patchlevel, and subversion were being collected but never written out to config.sh. The following patch fixes that. The missing 'version' item caused problems for installperl. --- 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 + [End of patch.] The tweak below fixes the following problems in a VMS-specific hunk of installperl: 1) Now uses 'archname' Config item instead of deprecated 'arch'. 2) Location of core file list changed to reflect current layout of source tree. 3) A backwards map statement was storing a single return status rather than the intended list of filenames. --- installperl.;-0 Wed Mar 8 06:22:41 2000 +++ installperl Mon Apr 24 12:55:20 2000 @@ -254,9 +254,9 @@ mkpath("$installarchlib/CORE", 1, 0777); my @corefiles; if ($Is_VMS) { # We did core file selection during build - my $coredir = "lib/$Config{'arch'}/$ver"; + my $coredir = "lib/$Config{archname}/$ver/CORE"; $coredir =~ tr/./_/; - @corefiles = map { s|^$coredir/||i; } <$coredir/*.*>; + map { s|^$coredir/||i; } @corefiles = <$coredir/*.*>; } else { # [als] hard-coded 'libperl' name... not good! [End of patch.] _______________________________________________ Craig A. Berry mailto:craig.berry@metamorgs.com