trying to install mime-tools-5_427 on perl 5.10.0 (VMS 8.3)
Hi,
I've hit a bit of a wall. I unpack the tar, and
follow the usual perl mantra:
perl -d makefile.pl
Loading DB routines from perl5db.pl version 1.3
Editor support available.
Enter h or `h h' for help, or `perldoc perldebug' for more help.
Can't call method load_all_extensions on an undefined value at
inc/Module/Install.pm line 167.
at inc/Module/Install.pm line 167
Module::Install::preload('Module::Install=HASH(0x59aa60)') called at
inc/Module/Install.pm line 147
Module::Install::import('inc::Module::Install') called at makefile.pl
line 3
main::BEGIN() called at inc/Module/Install.pm line 3
eval {...} called at inc/Module/Install.pm line 3
BEGIN failed--compilation aborted at makefile.pl line 3.
at makefile.pl line 3
Debugged program terminated. Use q to quit or R to restart,
use o inhibit_exit to avoid stopping after program termination,
h q, h R or h o to get additional info.
D
I believe I have all of the required pieces in place,
or already in the core. Any hints appreciated.
Carl Friedberg
friedb...@esb.com
www.esb.com
The Elias Book of Baseball Records
2009 Edition
Re: Perl 5.10.1 release notes help needed
Craig A. Berry wrote: It's looking like we'll get a release candidate for Perl 5.10.1 in the next week or two. Indications are it will be the best ever Perl on VMS release, but it would be helpful if the so-called perldelta, the changes since the previous release, could be updated for accuracy and completeness. What's in there so far is below. I will see what I can come up with, but people who know things (especially John M.), should give a holler with relevant details. An update to the pod is in order for the PERL_VMS_POSIX_EXIT logical name. That should help you with what to put in the delta file. I forgot to indicate in the file that the DECC$FILENAME_UNIX_REPORT feature also activates the PERL_VMS_POSIX_EXIT mode. The support for UNIX filenames when using the DECC$FILENAME_UNIX_REPORT and DECC$EFS_CHARSET has been greatly improved. Only a few of the dual life modules do not have support. -John wb8...@qsl.net Personal Opinion Only --- /rsync_root/perl/pod/perlvms.podMon Apr 20 04:03:09 2009 +++ pod/perlvms.pod Wed Jul 15 21:13:08 2009 @@ -1167,16 +1167,16 @@ SS$_NORMAL, and setting C$? to a non-zero value results in the generic failure status SS$_ABORT. See also Lperlport/exit. -With the future POSIX_EXIT mode set, setting C$? will cause the -new value to also be encoded into C$^E so that the either the -original parent or child exit status values of 0 to 255 -can be automatically recovered by C programs expecting _POSIX_EXIT -behavior. If both a parent and a child exit value are non-zero, then it -will be assumed that this is actually a VMS native status value to -be passed through. The special value of 0x is almost a NOOP as -it will cause the current native VMS status in the C library to -become the current native Perl VMS status, and is handled this way -as consequence of it known to not be a valid native VMS status value. +With the CPERL_VMS_POSIX_EXIT logical name defined as ENABLE, +setting C$? will cause the new value to also be encoded into C$^E +so that the either the original parent or child exit status values o + 0 to 255 can be automatically recovered by C programs expecting +_POSIX_EXIT behavior. If both a parent and a child exit value are +non-zero, then it will be assumed that this is actually a VMS native +status value to be passed through. The special value of 0x is +almost a NOOP as it will cause the current native VMS status in the +C library to become the current native Perl VMS status, and is handled +this way as a it is known to not be a valid native VMS status value. It is recommend that only values in range of normal UNIX parent or child status numbers, 0 to 255 are used. @@ -1186,10 +1186,15 @@ non-zero values to SS$_ABORT when setting C$? in an END block (but zero will still be converted to SS$_NORMAL). -Do not use the pragma Cuse vmsish 'status' with the future -POSIX_EXIT mode, as they are at times requesting conflicting -actions and the consequence of ignoring this advice will be -undefined to allow future improvements in the POSIX exit handling. +Do not use the pragma Cuse vmsish 'status' with CPERL_VMS_POSIX_EXIT +enabled, as they are at times requesting conflicting actions and the +consequence of ignoring this advice will be undefined to allow future +improvements in the POSIX exit handling. + +In general, with the PERL_VMS_POSIX_EXIT enabled, more detailed information +will be availble in the exit status for DCL scripts or other native VMS tools, +and will give the expected information for Posix programs. It has not been +made the default for backward compatibility. =item $|
Re: Perl 5.10.1 release notes help needed
On Jul 15, 2009, at 9:45 PM, John E. Malmberg wrote: An update to the pod is in order for the PERL_VMS_POSIX_EXIT logical name. That should help you with what to put in the delta file. Thanks, John, this is in blead at http://perl5.git.perl.org/perl.git/commitdiff/d9ac7b6 . What about the GNV$UNIX_SHELL logical? Should we leave it undocumented or should we document it and say it's subject to change if a supported mechanism for detecting the GNV bash shell becomes available? Craig A. Berry mailto:craigbe...@mac.com ... getting out of a sonnet is much more difficult than getting in. Brad Leithauser
Re: trying to install mime-tools-5_427 on perl 5.10.0 (VMS 8.3)
On Jul 15, 2009, at 5:26 PM, Carl Friedberg wrote:
Hi,
I've hit a bit of a wall. I unpack the tar, and
follow the usual perl mantra:
perl -d makefile.pl
Loading DB routines from perl5db.pl version 1.3
Editor support available.
Enter h or `h h' for help, or `perldoc perldebug' for more help.
Can't call method load_all_extensions on an undefined value at inc/
Module/Install.pm line 167.
at inc/Module/Install.pm line 167
Module::Install::preload('Module::Install=HASH(0x59aa60)')
called at inc/Module/Install.pm line 147
Module::Install, IMO, is inherently fragile, as is any program that
thinks it knows how to install itself. But no one cares what I think.
Check for an inc logical name. Not sure what else to suggest --
maybe SET WATCH FILE to see what it's actually looking for.
Module::Install::import('inc::Module::Install') called at
makefile.pl line 3
main::BEGIN() called at inc/Module/Install.pm line 3
eval {...} called at inc/Module/Install.pm line 3
BEGIN failed--compilation aborted at makefile.pl line 3.
at makefile.pl line 3
Debugged program terminated. Use q to quit or R to restart,
use o inhibit_exit to avoid stopping after program termination,
h q, h R or h o to get additional info.
D
I believe I have all of the required pieces in place,
or already in the core. Any hints appreciated.
Carl Friedberg
friedb...@esb.com
www.esb.com
The Elias Book of Baseball Records
2009 Edition
Craig A. Berry
mailto:craigbe...@mac.com
... getting out of a sonnet is much more
difficult than getting in.
Brad Leithauser
Re: Perl 5.10.1 release notes help needed
Craig A. Berry wrote: On Jul 15, 2009, at 9:45 PM, John E. Malmberg wrote: An update to the pod is in order for the PERL_VMS_POSIX_EXIT logical name. That should help you with what to put in the delta file. Thanks, John, this is in blead at http://perl5.git.perl.org/perl.git/commitdiff/d9ac7b6. What about the GNV$UNIX_SHELL logical? Should we leave it undocumented or should we document it and say it's subject to change if a supported mechanism for detecting the GNV bash shell becomes available? I do not know when the GNV bash/make utilities will start setting that logical name. Until we can get some testing done with it, either we should leave it undocumented or document it as experimental. -John wb8...@qsl.net Personal Opinion Only
