perl.vmsperl

perl.vmsperl http://www.nntp.perl.org/group/perl.vmsperl/ ... Copyright 1998-2013 perl.org Tue, 18 Jun 2013 07:09:21 +0000 ask@perl.org test PCSI kits for Perl 5.18.0 by Craig A. Berry Test installers for Perl 5.18.0 for OpenVMS 8.3 and later (Alpha or Itanium) are available at: https://sourceforge.net/projects/vmsperlkit/files/ N.B. SourceForge disallows dollar signs in file names, so after downloading you must rename the files from .PCSI_COMPRESSED to .PCSI$COMPRESSED for the product command to see the file. If all goes well, the kits will be updated with "V" instead of "T" prefixing the version number and released as final kits in perhaps a week or two. Give a shout if you spot any problems. The command procedure used to produce the kits is available at: https://sourceforge.net/p/vmsperlkit/code/ci/default/tree/perlkit/ You're welcome to use this to produce your own kits with different configuration options, but if you do, *please* change the package name to something other than "PERL" (e.g., put your initials in there or something). That should keep folks from stomping on each others' alternate installations. ________________________________________ Craig A. Berry mailto:craigberry@mac.com "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser http://www.nntp.perl.org/group/perl.vmsperl/2013/05/msg15611.html Fri, 31 May 2013 17:07:36 +0000 Re: perl 5.18.0 RC1 by Craig A. Berry On May 12, 2013, at 10:56 PM, Carl Friedberg <friedberg@exs.esb.com> wrote: >>> comp/parser.t I was able to reproduce a comp/parser.t failure by running in an environment where DCL$PATH pointed to a directory I had write access to by virtue of having a UIC group in the 1 to 10 range (i.e., effectively a system account even though it's not *the* SYSTEM account). Try deassigning DCL$PATH or running from a different account. ________________________________________ Craig A. Berry mailto:craigberry@mac.com "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser http://www.nntp.perl.org/group/perl.vmsperl/2013/05/msg15610.html Wed, 15 May 2013 00:13:31 +0000 RE: perl 5.18.0 RC1 by Carl Friedberg Thanks, Craig. I know this happened last time I ran some tests, so I've started tests on several more servers (Alphas) I'll keep you posted. Carl Friedberg (212) 798-0718 www.esb.com The Elias Book of Baseball Records 2013 Edition > -----Original Message----- > From: Craig A. Berry [mailto:craigberry@mac.com] > Sent: Sunday, May 12, 2013 10:07 PM > To: Carl Friedberg > Cc: vmsperl@perl.org (vmsperl@perl.org) > Subject: Re: perl 5.18.0 RC1 > > > On May 12, 2013, at 12:33 PM, Carl Friedberg <friedberg@exs.esb.com> > wrote: > > > Craig, > > > > my first cut at 18.0 > > Thanks for testing, Carl. And the rest of you losing sleep because you don't > know how Perl 5.18.0 will work in your environment with your preferred > configuration running your favorite extensions have nothing between you > and a great night's sleep except for downloading, building, and installing the > first (and possibly final) release candidate, available from: > > https://metacpan.org/release/rjbs/perl-5.18.0-RC1/ > > or > > http://search.cpan.org/~rjbs/perl-5.18.0-RC1/ > > > Anything you would like me to pursue? > > It's not up to me to say what's important to you. Generally core tests would > be more important than module tests, and module tests that are distributed > with the core (starting with dist/) would be more important than module > tests from CPAN (starting with cpan/). From your list, the ones starting with > comp/ and op/ would probably benefit from a closer look. > > > Itanium RX2600 (same as you, I believe) > > $ cc/version > > HP C V7.3-018 on OpenVMS IA64 V8.4 > > > > $ show system/noproc > > OpenVMS V8.4 on node TITAND 12-MAY-2013 13:30:24.27 Uptime 1 > 21:47:08 > > > > Failed 34 tests out of 2164, 98.43% okay. > > ../cpan/Archive-Extract/t/01_Archive-Extract.t > > ../cpan/CPANPLUS/t/03_CPANPLUS-Internals-Source.t > > ../cpan/CPANPLUS/t/04_CPANPLUS-Module.t > > ../cpan/CPANPLUS/t/20_CPANPLUS-Dist-MM.t > > ../cpan/Config-Perl-V/t/10_base.t > > ../cpan/ExtUtils-MakeMaker/t/INSTALL_BASE.t > > ../cpan/ExtUtils-MakeMaker/t/PL_FILES.t > > ../cpan/ExtUtils-MakeMaker/t/basic.t > > ../cpan/ExtUtils-MakeMaker/t/miniperl.t > > ../cpan/ExtUtils-MakeMaker/t/pm_to_blib.t > > ../cpan/ExtUtils-MakeMaker/t/xs.t > > ../cpan/Module-Build/t/PL_files.t > > ../cpan/Module-Build/t/compat.t > > ../cpan/Module-Build/t/install.t > > ../cpan/Module-Build/t/install_extra_target.t > > ../cpan/Module-Build/t/manifypods.t > > ../cpan/Module-Build/t/runthrough.t > > ../cpan/Module-Build/t/tilde.t > > ../cpan/autodie/t/recv.t > > ../dist/Carp/t/Carp.t > > ../dist/ExtUtils-Install/t/Install.t > > ../dist/ExtUtils-Install/t/InstallWithMM.t > > ../dist/ExtUtils-Install/t/Installapi2.t > > ../dist/ExtUtils-Install/t/can_write_dir.t > > ../dist/Net-Ping/t/510_ping_udp.t > > ../ext/Pod-Html/t/cache.t > > ../ext/VMS-Stdio/t/vms_stdio.t > > ../lib/perl5db.t > > comp/parser.t > > op/coreamp.t > > op/kill0.t > > op/stat.t > > porting/pod_rules.t > > porting/podcheck.t > > With > > $ cc/version > HP C V7.3-020 on OpenVMS IA64 V8.4 > > with update 8.0, on a disk with the following attributes: > > Volume Status: ODS-5, subject to mount verification, protected subsystems > enabled, write-through XFC caching enabled, write-through XQP caching > enabled, hard links enabled, special files enabled. > > from a non-privileged account, I get: > > cpan/CPANPLUS/t/03_CPANPLUS-Internals-Source .................. FAILED at > test 28 > cpan/ExtUtils-Constant/t/Constant ............................. FAILED at test 27 > cpan/Module-Build/t/compat .................................... FAILED at test 8 > cpan/Module-Build/t/debug ..................................... FAILED at test 1 > cpan/Module-Build/t/install_extra_target ...................... FAILED at test 4 > cpan/Module-Build/t/install ................................... FAILED--expected 35 > tests, saw 1 > cpan/Module-Build/t/manifypods ................................ FAILED--expected 21 > tests, saw 2 > cpan/Module-Build/t/PL_files .................................. FAILED--expected 8 > tests, saw 0 > cpan/Module-Build/t/properties/share_dir ...................... FAILED--expected > 23 tests, saw 16 > cpan/Module-Build/t/runthrough ................................ FAILED at test 13 > cpan/Module-Build/t/tilde ..................................... FAILED at test 16 > ext/Pod-Html/t/cache .......................................... FAILED at test 8 > ext/Pod-Html/t/crossref ....................................... FAILED at test 1 > ext/Pod-Html/t/htmldir1 ....................................... FAILED at test 1 > ext/Pod-Html/t/htmldir3 ....................................... FAILED at test 1 > lib/perl5db ................................................... FAILED at test 22 > Failed 16 tests out of 2171, 99.26% okay. > > which is quite a bit better than yours, but a few more than I expected, mainly > because Pod::Html has not been failing recently. I have no explanation for > why it's so different from yours. There must be some differences in > privileges, quotas, volume characteristics, external utilities installed (such as > tar or vmstar), etc. > ________________________________________ > Craig A. Berry > mailto:craigberry@mac.com > > "... getting out of a sonnet is much more > difficult than getting in." > Brad Leithauser http://www.nntp.perl.org/group/perl.vmsperl/2013/05/msg15609.html Mon, 13 May 2013 03:57:15 +0000 Re: perl 5.18.0 RC1 by Craig A. Berry On May 12, 2013, at 12:33 PM, Carl Friedberg <friedberg@exs.esb.com> wrote: > Craig, > > my first cut at 18.0 Thanks for testing, Carl. And the rest of you losing sleep because you don't know how Perl 5.18.0 will work in your environment with your preferred configuration running your favorite extensions have nothing between you and a great night's sleep except for downloading, building, and installing the first (and possibly final) release candidate, available from: https://metacpan.org/release/rjbs/perl-5.18.0-RC1/ or http://search.cpan.org/~rjbs/perl-5.18.0-RC1/ > Anything you would like me to pursue? It's not up to me to say what's important to you. Generally core tests would be more important than module tests, and module tests that are distributed with the core (starting with dist/) would be more important than module tests from CPAN (starting with cpan/). From your list, the ones starting with comp/ and op/ would probably benefit from a closer look. > Itanium RX2600 (same as you, I believe) > $ cc/version > HP C V7.3-018 on OpenVMS IA64 V8.4 > > $ show system/noproc > OpenVMS V8.4 on node TITAND 12-MAY-2013 13:30:24.27 Uptime 1 21:47:08 > > Failed 34 tests out of 2164, 98.43% okay. > ../cpan/Archive-Extract/t/01_Archive-Extract.t > ../cpan/CPANPLUS/t/03_CPANPLUS-Internals-Source.t > ../cpan/CPANPLUS/t/04_CPANPLUS-Module.t > ../cpan/CPANPLUS/t/20_CPANPLUS-Dist-MM.t > ../cpan/Config-Perl-V/t/10_base.t > ../cpan/ExtUtils-MakeMaker/t/INSTALL_BASE.t > ../cpan/ExtUtils-MakeMaker/t/PL_FILES.t > ../cpan/ExtUtils-MakeMaker/t/basic.t > ../cpan/ExtUtils-MakeMaker/t/miniperl.t > ../cpan/ExtUtils-MakeMaker/t/pm_to_blib.t > ../cpan/ExtUtils-MakeMaker/t/xs.t > ../cpan/Module-Build/t/PL_files.t > ../cpan/Module-Build/t/compat.t > ../cpan/Module-Build/t/install.t > ../cpan/Module-Build/t/install_extra_target.t > ../cpan/Module-Build/t/manifypods.t > ../cpan/Module-Build/t/runthrough.t > ../cpan/Module-Build/t/tilde.t > ../cpan/autodie/t/recv.t > ../dist/Carp/t/Carp.t > ../dist/ExtUtils-Install/t/Install.t > ../dist/ExtUtils-Install/t/InstallWithMM.t > ../dist/ExtUtils-Install/t/Installapi2.t > ../dist/ExtUtils-Install/t/can_write_dir.t > ../dist/Net-Ping/t/510_ping_udp.t > ../ext/Pod-Html/t/cache.t > ../ext/VMS-Stdio/t/vms_stdio.t > ../lib/perl5db.t > comp/parser.t > op/coreamp.t > op/kill0.t > op/stat.t > porting/pod_rules.t > porting/podcheck.t With $ cc/version HP C V7.3-020 on OpenVMS IA64 V8.4 with update 8.0, on a disk with the following attributes: Volume Status: ODS-5, subject to mount verification, protected subsystems enabled, write-through XFC caching enabled, write-through XQP caching enabled, hard links enabled, special files enabled. from a non-privileged account, I get: cpan/CPANPLUS/t/03_CPANPLUS-Internals-Source .................. FAILED at test 28 cpan/ExtUtils-Constant/t/Constant ............................. FAILED at test 27 cpan/Module-Build/t/compat .................................... FAILED at test 8 cpan/Module-Build/t/debug ..................................... FAILED at test 1 cpan/Module-Build/t/install_extra_target ...................... FAILED at test 4 cpan/Module-Build/t/install ................................... FAILED--expected 35 tests, saw 1 cpan/Module-Build/t/manifypods ................................ FAILED--expected 21 tests, saw 2 cpan/Module-Build/t/PL_files .................................. FAILED--expected 8 tests, saw 0 cpan/Module-Build/t/properties/share_dir ...................... FAILED--expected 23 tests, saw 16 cpan/Module-Build/t/runthrough ................................ FAILED at test 13 cpan/Module-Build/t/tilde ..................................... FAILED at test 16 ext/Pod-Html/t/cache .......................................... FAILED at test 8 ext/Pod-Html/t/crossref ....................................... FAILED at test 1 ext/Pod-Html/t/htmldir1 ....................................... FAILED at test 1 ext/Pod-Html/t/htmldir3 ....................................... FAILED at test 1 lib/perl5db ................................................... FAILED at test 22 Failed 16 tests out of 2171, 99.26% okay. which is quite a bit better than yours, but a few more than I expected, mainly because Pod::Html has not been failing recently. I have no explanation for why it's so different from yours. There must be some differences in privileges, quotas, volume characteristics, external utilities installed (such as tar or vmstar), etc. ________________________________________ Craig A. Berry mailto:craigberry@mac.com "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser http://www.nntp.perl.org/group/perl.vmsperl/2013/05/msg15608.html Mon, 13 May 2013 02:07:11 +0000 perl 5.18.0 RC1 by Carl Friedberg Craig, my first cut at 18.0 Anything you would like me to pursue? Itanium RX2600 (same as you, I believe) $ cc/version HP C V7.3-018 on OpenVMS IA64 V8.4 $ show system/noproc OpenVMS V8.4 on node TITAND 12-MAY-2013 13:30:24.27 Uptime 1 21:47:08 Failed 34 tests out of 2164, 98.43% okay. ../cpan/Archive-Extract/t/01_Archive-Extract.t ../cpan/CPANPLUS/t/03_CPANPLUS-Internals-Source.t ../cpan/CPANPLUS/t/04_CPANPLUS-Module.t ../cpan/CPANPLUS/t/20_CPANPLUS-Dist-MM.t ../cpan/Config-Perl-V/t/10_base.t ../cpan/ExtUtils-MakeMaker/t/INSTALL_BASE.t ../cpan/ExtUtils-MakeMaker/t/PL_FILES.t ../cpan/ExtUtils-MakeMaker/t/basic.t ../cpan/ExtUtils-MakeMaker/t/miniperl.t ../cpan/ExtUtils-MakeMaker/t/pm_to_blib.t ../cpan/ExtUtils-MakeMaker/t/xs.t ../cpan/Module-Build/t/PL_files.t ../cpan/Module-Build/t/compat.t ../cpan/Module-Build/t/install.t ../cpan/Module-Build/t/install_extra_target.t ../cpan/Module-Build/t/manifypods.t ../cpan/Module-Build/t/runthrough.t ../cpan/Module-Build/t/tilde.t ../cpan/autodie/t/recv.t ../dist/Carp/t/Carp.t ../dist/ExtUtils-Install/t/Install.t ../dist/ExtUtils-Install/t/InstallWithMM.t ../dist/ExtUtils-Install/t/Installapi2.t ../dist/ExtUtils-Install/t/can_write_dir.t ../dist/Net-Ping/t/510_ping_udp.t ../ext/Pod-Html/t/cache.t ../ext/VMS-Stdio/t/vms_stdio.t ../lib/perl5db.t comp/parser.t op/coreamp.t op/kill0.t op/stat.t porting/pod_rules.t porting/podcheck.t ### Since not all tests were successful, you may want to run some of ### them individually and examine any diagnostic messages they produce. ### See the INSTALL document's section on "make test". ### You have a good chance to get more information by running ### ./perl harness ### in the 't' directory since most (>=80%) of the tests succeede Carl Friedberg www.esb.com The Elias Book of Baseball Records 2013 Edition http://www.nntp.perl.org/group/perl.vmsperl/2013/05/msg15607.html Sun, 12 May 2013 17:34:04 +0000 VMS (was RE: status of WinCE Perl port in 2012) by Carl Friedberg I do not wish to start a flame war, but I respectfully disagree with your assessment of VMS porting support. I believe there are at least five of us in the Perl VMS community who could step in if Craig Berry needed to step down from his Perl VMS duties. I hope that never happens, but don't write VMS off. Please. Current hardware is still manufactured, and the latest Intel Itanium processor will be supported by VMS. Five years from now, I expect that situation to be the same. VMS has been around since 1977. It is actively supported and developed at HP. Carl Friedberg www.esb.com The Elias Book of Baseball Records 2013 Edition -----Original Message----- From: bulk88 [mailto:bulk88@hotmail.com] Sent: Wednesday, January 16, 2013 3:38 PM To: Konovalov, Vadim (Vadim)** CTR ** Cc: perl5-porters@perl.org; Steve Hay; Nicholas Clark; Jan Dubois Subject: Re: status of WinCE Perl port in 2012 Konovalov, Vadim (Vadim)** CTR ** wrote: > tl;dr > > 'wince' port is still stangates, I have no objections for it to be removed, > but maybe it still usefull to wait a bit more and to see on where will go > other OS projects, namely QT and firefox, WRT this platform, > and then follow their path. > > Opinions welcome. > > More text follow. > > First, let me express my gratitude to the community for the support. > > Next, my vision of the port. > > Currently, 'wince' port is based on 'celib' library, which is gone from the WEB > and which is randomly located on old folders of some rare people (me > included) > > The idea that I was having was to get rid of dependancy of 'celib', (at least > URLs to CELIB aren't pointing to downloadable files anyway) > > 2 ways: 1) embed needed pieces of CELIB and 2) look how other projects > with 'wince' port do. Embedding CELIB into Perl's git (license???) or uploading to CPAN is the solution. How much modulizing/Alien:: CELIB needs IDK. I don't think anyone will be fixing any bugs in CELIB other than a Perl WM/CE user. Is this the same celib http://celib.cvs.sourceforge.net/celib/ ? > > One of most interesting libraries that support 'wince' is QT. > An idea was to 1) look how QT does the thing and 2) maybe try building Perl > with QT library (license issues are left aside, just experiments purposes) > > It appears that overall ability to build QT for wince decreases over time. > > As many already know, http://qt-project.org/ announced their 5.0 version, > and anouncement > http://blog.qt.digia.com/blog/2012/12/19/qt-5-0/?utm_source=rss&utm_medium=rss&utm_campaign=qt-5-0 > contains QT roadmap http://www.youtube.com/watch?v=3QgG9oYhH-c > which mentions port to 1) android and further to 2) windows mobile... > > but even http://qt-project.org/downloads contains "Qt libraries 4.8.4 for Windows CE (269 MB)" > but not 5.0 for WINCE. > There is mention that Qt 5 will support "Windows 8 (WinRT)" among current > Mobile platforms. > WinRT/WP 8 is not related to WinCE kernel OSes. The distance is somewhere between OS9 and OSX or even further than those 2. > Going through helpful QT recomendations at > > http://qt-project.org/doc/qt-4.8/requirements-wince.html > http://qt-project.org/doc/qt-4.8/windowsce-customization.html > http://qt-project.org/doc/qt-4.8/install-wince.html > > suggests getting proper cross-compiler, and this is helpful. > > There are also other helpful links such as > http://qt-project.org/forums/viewthread/1138 > http://qt-project.org/forums/viewthread/633 > http://qt-project.org/forums/viewthread/13621 > which are inspiring. > Looks complicated. Not sure if CELib or QT is harder to use from a C/build process point. > > On the other side - reading the article at > http://news.cnet.com/8301-1001_3-57431236-92/microsoft-bans-firefox-on-arm-based-windows-mozilla-says/ > and wikipedia article on > http://en.wikipedia.org/wiki/Windows_Phone_8 > makes me think that there is no C/C++ for development altogether, and even that - getting mobile > development kit requires Windows 8 OS (not even Vista) which makes me stop at this point. > Perl won't run without jailbreaking on iOS, and will never be in the App Store. Unless AS does something, Perl will never run on WP 8 un-jailbroken. Jailbroken WP8 is regular C++ Win32 we know and love http://i.imgur.com/lWKjp.png . http://msdn.microsoft.com/en-US/library/windows/apps/hh694083 the rules seem to have an non-embedded interpreted language ban (the high level script is not replaceable), more liberal than iOS, but still no Perl. I don't think there is any market for AS to do a signed WP8 Perl anyway. (Jan, maybe you can answer what AS's plans are with AP and WP8?) > Also - reading this article - http://en.wikipedia.org/wiki/Windows_Phone - makes me think that even binaries will not be run on newer windows phone?? > <quote> > Terry Myerson, corporate VP of Windows Phone engineering, said, "With the move to capacitive touch screens, away from the stylus, and the moves to some of the hardware choices we made for the Windows Phone 7 experience, we had to break application compatibility with Windows Mobile 6.5." > </quote> > My interest is in stylus based mid 2000s WM OSes. WP 7 (CE based) IMO is beta for WP 8's GUI and unrelated to other CE series. > So, two questions are > 1) is port needed? does it worth efforts? Good question. Philosophy wise, I say some effort should be tried. In 5 years I predict Perl 5 will run on only 2 OSes, generic POSIX (limited to Linux, OSX, and BSD), and maybe Win32. If Perl is only run on POSIX, then POSIX will creep into the codebase. Having non-POSIX platforms helps with POSIX not creeping in. On the otherhand, if there are no smoke tests, and no users to report bugs, it is useless to keep the platform around "in case" someone comes with a bug (or maybe the real reason to keep around dead platforms is for bragging rights), right? Looking at Perl's special platforms (first part is my opinion of the amount of support these OSes require in LOC in Perl, 2nd part is my guess at how POSIX they are), Plan 9 (low, semi-unix), Qnx (low, unix), Symbian (high, non-unix), Cygwin (low, semi-unix, 1-2 porters, last known smoke http://www.nntp.perl.org/group/perl.daily-build.reports/2012/10/msg128941.html ), OS2 (high, non-unix), Netware (high, non-unix), VMS (high, non-unix?, 1 porter), and djgpp (high, non-unix, already marked for removal) are heading towards removal in the next 5 years. Win32 will be the only non-POSIX platform left. Now the dilemma with cable boxing/walled gardens is, if everything is a cable box, what is the developer's system? a cable box? :-D MS made free almost all their development tools over the last half decade, probably to keep up with FOSS platforms. But the tide could always turn back towards a $10K license fee. > 3) sit a while and look at what happens at QT/windows mobile port?? I think nothing will happen. WM/CE are dead. Most people throw away mobile devices after 18-24 months. CE has no console window. Who will provide it? http://techbase.kde.org/Projects/KDE_on_Windows/Windows_CE#Console CELIB sounds better than that. >> >> All in all, now I confirm usefulness of a port and do promise to >> provide stable build of it, including binaries, including perl+tcltk. > > Regards, > Vadim. I have a CE build enviroment setup. Now the question is about repairing the makefile/build process. If it is less than a week of work (for me, and maybe Vadim) to keep it working with blead, it should remain. http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15606.html Wed, 16 Jan 2013 21:35:20 +0000 Re: Bizarre copy of unknown by Craig A. Berry On Jan 9, 2013, at 11:01 AM, Thomas Pfau <tfpfau@gmail.com> wrote: > I went back to the threaded perl and removed the CCFLAGS from makefile.pl. It builds and runs now. I'm not sure why that was in there. It must have been added by an older version of h2xs. > > Thanks for the help. Sorry for distracting you from other things. Glad I could help. And VMS::CMS looks like a nifty module :-). ________________________________________ Craig A. Berry mailto:craigberry@mac.com "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15605.html Thu, 10 Jan 2013 12:29:43 +0000 Re: Bizarre copy of unknown by Thomas Pfau I went back to the threaded perl and removed the CCFLAGS from makefile.pl. It builds and runs now. I'm not sure why that was in there. It must have been added by an older version of h2xs. Thanks for the help. Sorry for distracting you from other things. On Jan 9, 2013 11:42 AM, "Thomas Pfau" <tfpfau@gmail.com> wrote: > I think this has something to do with threads. I rebuilt perl at work > without threads and the module works again. > On Jan 9, 2013 8:20 AM, "Craig A. Berry" <craigberry@mac.com> wrote: > >> >> On Jan 8, 2013, at 10:07 PM, Thomas Pfau <tfpfau@gmail.com> wrote: >> >> > > Bizarre copy of UNKNOWN in list assignment at >> /DISK$USERS/PFAU/PROG/PERL/vms-cms/blib/lib/VMS/CMS.pm line 490. >> >> A quick web search shows that this usually means the compiler flags used >> to compile the extension are different from the compiler flags used to >> compile Perl. Your Makefile.PL has the line: >> >> CCFLAGS => >> "/include=[]/standard=relaxed_ansi/prefix=all/obj=.obj/noshare_globals" >> >> which will be similar but not 100% the same as what's used to build Perl, >> depending on configuration. You'll probably want to take $Config{ccflags} >> and append "/noshare_globals" to it, though since that's the default for >> the compiler, it doesn't seem necessary to specify it. >> >> You can see what your Perl was built with by doing: >> >> $ perl -"V:ccflags" >> ccflags='/Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj >> /NOANSI_ALIAS/float=ieee/ieee=denorm/NAMES=(SHORTENED)/Define=_USE_STD_STAT=1'; >> >> ________________________________________ >> Craig A. Berry >> mailto:craigberry@mac.com >> >> "... getting out of a sonnet is much more >> difficult than getting in." >> Brad Leithauser >> >> http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15604.html Wed, 09 Jan 2013 17:02:06 +0000 Re: Bizarre copy of unknown by Thomas Pfau I think this has something to do with threads. I rebuilt perl at work without threads and the module works again. On Jan 9, 2013 8:20 AM, "Craig A. Berry" <craigberry@mac.com> wrote: > > On Jan 8, 2013, at 10:07 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > > > > Bizarre copy of UNKNOWN in list assignment at > /DISK$USERS/PFAU/PROG/PERL/vms-cms/blib/lib/VMS/CMS.pm line 490. > > A quick web search shows that this usually means the compiler flags used > to compile the extension are different from the compiler flags used to > compile Perl. Your Makefile.PL has the line: > > CCFLAGS => > "/include=[]/standard=relaxed_ansi/prefix=all/obj=.obj/noshare_globals" > > which will be similar but not 100% the same as what's used to build Perl, > depending on configuration. You'll probably want to take $Config{ccflags} > and append "/noshare_globals" to it, though since that's the default for > the compiler, it doesn't seem necessary to specify it. > > You can see what your Perl was built with by doing: > > $ perl -"V:ccflags" > ccflags='/Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj > /NOANSI_ALIAS/float=ieee/ieee=denorm/NAMES=(SHORTENED)/Define=_USE_STD_STAT=1'; > > ________________________________________ > Craig A. Berry > mailto:craigberry@mac.com > > "... getting out of a sonnet is much more > difficult than getting in." > Brad Leithauser > > http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15603.html Wed, 09 Jan 2013 16:42:45 +0000 Re: Bizarre copy of unknown by Craig A. Berry On Jan 8, 2013, at 10:07 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > > Bizarre copy of UNKNOWN in list assignment at /DISK$USERS/PFAU/PROG/PERL/vms-cms/blib/lib/VMS/CMS.pm line 490. A quick web search shows that this usually means the compiler flags used to compile the extension are different from the compiler flags used to compile Perl. Your Makefile.PL has the line: CCFLAGS => "/include=[]/standard=relaxed_ansi/prefix=all/obj=.obj/noshare_globals" which will be similar but not 100% the same as what's used to build Perl, depending on configuration. You'll probably want to take $Config{ccflags} and append "/noshare_globals" to it, though since that's the default for the compiler, it doesn't seem necessary to specify it. You can see what your Perl was built with by doing: $ perl -"V:ccflags" ccflags='/Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj /NOANSI_ALIAS/float=ieee/ieee=denorm/NAMES=(SHORTENED)/Define=_USE_STD_STAT=1'; ________________________________________ Craig A. Berry mailto:craigberry@mac.com "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15602.html Wed, 09 Jan 2013 13:20:51 +0000 Re: Bizarre copy of unknown by Thomas Pfau On Tue, Jan 8, 2013 at 11:02 PM, Craig A. Berry <craigberry@mac.com> wrote: > On Jan 8, 2013, at 9:14 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > > > It looks like the definition of PL_sv_undef has something to do with > threads. Could this be broken because I enabled threads in my build? > > It doesn't have anything to do with threads directly, except all PL_xxx > global variables are not really global variables under threads, but are > instead members of the interpreter struct. > > > On Tue, Jan 8, 2013 at 9:24 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > > This is even causing problems with the generated constant function. If > I try to get the value of a constant I get this: > > > > $x = &VMS::CMS::CMS_K_ACCEPT > > The ampersand is forcing it to be interpreted as a subroutine call, but > that's not really a subroutine is it? > Yes. References to constants are resolved using AUTOLOAD which treats it like a subroutine. The subroutine returns the value of the constant. > Bizarre copy of UNKNOWN in list assignment at > /DISK$USERS/PFAU/PROG/PERL/vms-cms/blib/lib/VMS/CMS.pm line 490. > > The error message means it doesn't know the type of the scalar that's > having its flags checked (search for "Bizarre" in sv.c). I see that most > of your routines have return values of type SV *, so I would think that > instead of > > RETVAL = &PL_sv_undef; > > you would want: > > RETVAL = (SV *) &PL_sv_undef; > > but I don't know if that would help with the immediate problem. > I don't think that would help. RETVAL should be declared by the XS generation code as SV* so I don't think the cast would accomplish anything. I'll take a look at the generated C code. I haven't had time to download your module and try it. Is the one on CPAN > the latest? > Yes, the one on CPAN exhibits the problem. -- Thomas Pfau tfpfau@gmail.com http://www.linkedin.com/in/thomaspfau http://nbpfaus.net/~pfau/ http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15601.html Wed, 09 Jan 2013 04:07:58 +0000 Re: Bizarre copy of unknown by Craig A. Berry On Jan 8, 2013, at 9:14 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > It looks like the definition of PL_sv_undef has something to do with threads. Could this be broken because I enabled threads in my build? It doesn't have anything to do with threads directly, except all PL_xxx global variables are not really global variables under threads, but are instead members of the interpreter struct. > On Tue, Jan 8, 2013 at 9:24 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > This is even causing problems with the generated constant function. If I try to get the value of a constant I get this: > > $x = &VMS::CMS::CMS_K_ACCEPT The ampersand is forcing it to be interpreted as a subroutine call, but that's not really a subroutine is it? > Bizarre copy of UNKNOWN in list assignment at /DISK$USERS/PFAU/PROG/PERL/vms-cms/blib/lib/VMS/CMS.pm line 490. The error message means it doesn't know the type of the scalar that's having its flags checked (search for "Bizarre" in sv.c). I see that most of your routines have return values of type SV *, so I would think that instead of RETVAL = &PL_sv_undef; you would want: RETVAL = (SV *) &PL_sv_undef; but I don't know if that would help with the immediate problem. I haven't had time to download your module and try it. Is the one on CPAN the latest? ________________________________________ Craig A. Berry mailto:craigberry@mac.com "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15600.html Wed, 09 Jan 2013 04:03:17 +0000 Re: Bizarre copy of unknown by Thomas Pfau It looks like the definition of PL_sv_undef has something to do with threads. Could this be broken because I enabled threads in my build? On Tue, Jan 8, 2013 at 9:24 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > This is even causing problems with the generated constant function. If I > try to get the value of a constant I get this: > > $x = &VMS::CMS::CMS_K_ACCEPT > Bizarre copy of UNKNOWN in list assignment at > /DISK$USERS/PFAU/PROG/PERL/vms-cms/blib/lib/VMS/CMS.pm line 490. > > That implies that the code created by ExtUtils::MakeMaker::WriteConstants > is broken. > > > On Tue, Jan 8, 2013 at 10:59 AM, Thomas Pfau <tfpfau@gmail.com> wrote: > >> I am having issues with my 5.16.2 build. Modules that worked fine on 5.8 >> and 5.10 are now aborting with this error when returning an undefined value >> by referencing &PL_sv_undef. I have been "fixing" these by changing them to >> sv_newmortal() but I question why this code is suddenly broken. Does anyone >> know what changed? >> > > > > -- > Thomas Pfau > tfpfau@gmail.com > http://www.linkedin.com/in/thomaspfau > http://nbpfaus.net/~pfau/ -- Thomas Pfau tfpfau@gmail.com http://www.linkedin.com/in/thomaspfau http://nbpfaus.net/~pfau/ http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15599.html Wed, 09 Jan 2013 03:14:15 +0000 Re: Bizarre copy of unknown by Thomas Pfau This is even causing problems with the generated constant function. If I try to get the value of a constant I get this: $x = &VMS::CMS::CMS_K_ACCEPT Bizarre copy of UNKNOWN in list assignment at /DISK$USERS/PFAU/PROG/PERL/vms-cms/blib/lib/VMS/CMS.pm line 490. That implies that the code created by ExtUtils::MakeMaker::WriteConstants is broken. On Tue, Jan 8, 2013 at 10:59 AM, Thomas Pfau <tfpfau@gmail.com> wrote: > I am having issues with my 5.16.2 build. Modules that worked fine on 5.8 > and 5.10 are now aborting with this error when returning an undefined value > by referencing &PL_sv_undef. I have been "fixing" these by changing them to > sv_newmortal() but I question why this code is suddenly broken. Does anyone > know what changed? > -- Thomas Pfau tfpfau@gmail.com http://www.linkedin.com/in/thomaspfau http://nbpfaus.net/~pfau/ http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15598.html Wed, 09 Jan 2013 02:24:45 +0000 Bizarre copy of unknown by Thomas Pfau I am having issues with my 5.16.2 build. Modules that worked fine on 5.8 and 5.10 are now aborting with this error when returning an undefined value by referencing &PL_sv_undef. I have been "fixing" these by changing them to sv_newmortal() but I question why this code is suddenly broken. Does anyone know what changed? http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15597.html Tue, 08 Jan 2013 15:59:33 +0000 Re: VMS::Time module by Craig A. Berry On Jan 2, 2013, at 7:28 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > See http://nbpfaus.net/~pfau/perl.log for a log of a session where I start with all of the files named properly, go through the build process, and make a zipdist. The case in the filenames has been altered by the time things get to the zip file. Is DECC$EFS_CASE_PRESERVE defined at the point where you say "mmk zipdist"? ________________________________________ Craig A. Berry mailto:craigberry@mac.com "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15596.html Thu, 03 Jan 2013 01:36:11 +0000 Re: VMS::Time module by Thomas Pfau See http://nbpfaus.net/~pfau/perl.log for a log of a session where I start with all of the files named properly, go through the build process, and make a zipdist. The case in the filenames has been altered by the time things get to the zip file. On Tue, Jan 1, 2013 at 6:52 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > I just downloaded it recently. I believe it's the latest. I think the > changes may occur as perl builds the directory tree. > > Copyright (c) 1990-2008 Info-ZIP - Type 'zip "-L"' for software license. > This is Zip 3.0 (July 5th 2008), by Info-ZIP. > > > > On Tue, Jan 1, 2013 at 6:35 PM, Craig A. Berry <craigberry@mac.com> wrote: > >> >> On Jan 1, 2013, at 2:26 PM, Thomas Pfau <tfpfau@gmail.com> wrote: >> >> > I have this working on Alpha with (5.16.2) and without (5.10.0) 64 bit >> integer support, and on VAX (5.8.4). >> > >> > Before uploading this to CPAN I'm curious if anyone has a solution for >> 'mmk zipdist' mangling the case of filenames. The PAUSE server wants to >> extract certain files from the distribution but can't find them because of >> case differences. >> >> What version of zip do you have? As far as I know, zipdist just uses >> your zip program, and recent versions of Info-Zip preserve case just fine. >> ________________________________________ >> Craig A. Berry >> mailto:craigberry@mac.com >> >> "... getting out of a sonnet is much more >> difficult than getting in." >> Brad Leithauser >> >> > > > -- > Thomas Pfau > tfpfau@gmail.com > http://www.linkedin.com/in/thomaspfau > http://nbpfaus.net/~pfau/ > -- Thomas Pfau tfpfau@gmail.com http://www.linkedin.com/in/thomaspfau http://nbpfaus.net/~pfau/ http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15595.html Thu, 03 Jan 2013 01:28:31 +0000 Re: VMS::Time module by Thomas Pfau I just downloaded it recently. I believe it's the latest. I think the changes may occur as perl builds the directory tree. Copyright (c) 1990-2008 Info-ZIP - Type 'zip "-L"' for software license. This is Zip 3.0 (July 5th 2008), by Info-ZIP. On Tue, Jan 1, 2013 at 6:35 PM, Craig A. Berry <craigberry@mac.com> wrote: > > On Jan 1, 2013, at 2:26 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > > > I have this working on Alpha with (5.16.2) and without (5.10.0) 64 bit > integer support, and on VAX (5.8.4). > > > > Before uploading this to CPAN I'm curious if anyone has a solution for > 'mmk zipdist' mangling the case of filenames. The PAUSE server wants to > extract certain files from the distribution but can't find them because of > case differences. > > What version of zip do you have? As far as I know, zipdist just uses your > zip program, and recent versions of Info-Zip preserve case just fine. > ________________________________________ > Craig A. Berry > mailto:craigberry@mac.com > > "... getting out of a sonnet is much more > difficult than getting in." > Brad Leithauser > > -- Thomas Pfau tfpfau@gmail.com http://www.linkedin.com/in/thomaspfau http://nbpfaus.net/~pfau/ http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15594.html Tue, 01 Jan 2013 23:52:12 +0000 Re: VMS::Time module by Craig A. Berry On Jan 1, 2013, at 2:26 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > I have this working on Alpha with (5.16.2) and without (5.10.0) 64 bit integer support, and on VAX (5.8.4). > > Before uploading this to CPAN I'm curious if anyone has a solution for 'mmk zipdist' mangling the case of filenames. The PAUSE server wants to extract certain files from the distribution but can't find them because of case differences. What version of zip do you have? As far as I know, zipdist just uses your zip program, and recent versions of Info-Zip preserve case just fine. ________________________________________ Craig A. Berry mailto:craigberry@mac.com "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15593.html Tue, 01 Jan 2013 23:35:51 +0000 Re: 5.16.2 build by John E. Malmberg On 1/1/2013 4:51 PM, Craig A. Berry wrote: > >> Apparently DECC$READDIR_DROPDOTNOTYPE enabled causes problems. We >> have that set at work for something else. I had to define it locally to >> "disabled" and the build completed. > > This doesn't surprise me at all. There is latent support that I > suspect hasn't been tested much. Also note that whether you can build > with it or not doesn't say much either way about whether you can run > with it. Anyone interested can poke at what's there by doing: Several of the DECC$ logicals will probably interfere with build of Perl. I did my builds (a few years ago) with the DECC$ logical names settings off. I only turned them on for testing. Regards, -John malmberg@encompasserve.org Personal Opinion Only http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15592.html Tue, 01 Jan 2013 23:08:18 +0000 Re: 5.16.2 build by Thomas Pfau On Tue, Jan 1, 2013 at 5:51 PM, Craig A. Berry <craigberry@mac.com> wrote: > > On Dec 31, 2012, at 12:32 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > > Also, I haven't had any luck building on an ODS-5 volume on either Alpha > or Integrity. Tests are running now. > > Building on ODS-5 definitely works for a default build, but I think you > were building with case sensitive symbols. > I was originally trying to build with case sensitive symbols but realized it was going to be a nightmare and gave up. All of my later attempts had this option turned off. -- Thomas Pfau tfpfau@gmail.com http://www.linkedin.com/in/thomaspfau http://nbpfaus.net/~pfau/ http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15591.html Tue, 01 Jan 2013 23:08:06 +0000 Re: 5.16.2 build by Craig A. Berry On Dec 31, 2012, at 12:32 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > I finally got 5.16.2 to complete the build process on Integrity today. Thanks to your reports, 3 or 4 bugs that needed fixing have been fixed and the fixes checked into the repository so they'll be part of 5.18. As far as I can remember, all of the problems you encountered had to do with choosing non-default configuration options that haven't been fully maintained. > Apparently DECC$READDIR_DROPDOTNOTYPE enabled causes problems. We have that set at work for something else. I had to define it locally to "disabled" and the build completed. This doesn't surprise me at all. There is latent support that I suspect hasn't been tested much. Also note that whether you can build with it or not doesn't say much either way about whether you can run with it. Anyone interested can poke at what's there by doing: $ search [.vms]vms.c DROPDOTNOTYPE in the source tree. > Also, I haven't had any luck building on an ODS-5 volume on either Alpha or Integrity. Tests are running now. Building on ODS-5 definitely works for a default build, but I think you were building with case sensitive symbols. This is more difficult than it should be because the case of some symbol names is derived from the case of some object file names via the object library into which they're inserted. The names of the object files in turn are determined by the names of the source files, which are determined in some cases by the compiler and in some cases by MMS/MMK, which tend to upcase things willy nilly in the process of macro expansion. MakeMaker currently upcases symbol names in an attempt to match that behavior, which doesn't work (on an ODS-5 disk) for symbol names that don't go through macro expansion. I only got far enough before the holidays to see what a mess it is. The patch below reverses MakeMaker's current upcasing behavior, but then we don't match the symbols that have been upcased by macro expansion. I don't know of any way to make the correct case survive macro expansion and work on both ODS-2 and ODS-5 disks. I think it would be reasonable to require ODS-5 for case preserved symbol builds, but I don't know of a way to make even that work. --- cpan/ExtUtils-MakeMaker/lib/ExtUtils/MM_VMS.pm;-0 2012-12-17 04:22:23 -0600 +++ cpan/ExtUtils-MakeMaker/lib/ExtUtils/MM_VMS.pm 2012-12-23 15:18:05 -0600 @@ -970,18 +970,14 @@ $(BASEEXT).opt : Makefile.PL push @m, ' $(PERL) -e "print ""$(INST_STATIC)/Include='; if ($self->{OBJECT} =~ /\bBASEEXT\b/ or $self->{OBJECT} =~ /\b$self->{BASEEXT}\b/i) { - push @m, ($Config{d_vms_case_sensitive_symbols} - ? uc($self->{BASEEXT}) :'$(BASEEXT)'); + push @m, '$(BASEEXT)'; } else { # We don't have a "main" object file, so pull 'em all in - # Upcase module names if linker is being case-sensitive - my($upcase) = $Config{d_vms_case_sensitive_symbols}; my(@omods) = split ' ', $self->eliminate_macros($self->{OBJECT}); for (@omods) { s/\.[^.]*$//; # Trim off file type s[\$$\w+_EXT$][]; # even as a macro s/.*[:>\/\]]//; # Trim off dir spec - $_ = uc if $upcase; }; my(@lines); ________________________________________ Craig A. Berry mailto:craigberry@mac.com "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15590.html Tue, 01 Jan 2013 22:51:24 +0000 Re: VMS::Time module by Thomas Pfau I have this working on Alpha with (5.16.2) and without (5.10.0) 64 bit integer support, and on VAX (5.8.4). Before uploading this to CPAN I'm curious if anyone has a solution for 'mmk zipdist' mangling the case of filenames. The PAUSE server wants to extract certain files from the distribution but can't find them because of case differences. NAME VMS::Time - Manipulate OpenVMS binary time values SYNOPSIS use VMS::Time ':all'; $now = gettim(); $bin = bintim('01-jan-2010 12:00:00.00'); $asc = asctim($bin); ($year, $month, $day, $hr, $mn, $sc, $cc) = numtim($bin); $unix = vms_to_epoch($bin); $vms = epoch_to_vms(time()); DESCRIPTION These functions provide access to the OpenVMS time system services SYS$GETTIM, SYS$BINTIM, SYS$ASCTIM, and SYS$NUMTIM. Also provided are functions for converting between OpenVMS binary times and unix epoch time values. EXPORT None by default. Any function or constant may be imported by name. All functions can be imported using the tag ':routines'. All constants can be imported using the tag ':constants'. Routines and constants can be imported using the tag ':all'. OVERVIEW VMS::Time can accept and return VMS times in various formats depending upon the platform and how perl was built. The routines that return VMS time values accept a return mode argument that determines the format for the returned value. Constants are defined for the return modes as follows. PACK - Pack format (default) Returns the time as a string containing an 8 byte OpenVMS time value. LONGINT - Integer Returns the time value as an integer. This is only supported if perl was built with support for long integers. FLOAT - Floating point Returns the time value as a floating point number. Precision may be lost especially if perl was not built with support for long doubles. FLOAT is not supported on VAX systems. HEX - Hex string Returns the time value as a hex encoded string with a leading '0x'. BIGINT - Math::BigInt Returns the time value as a Math::BigInt object. Math::BigInt must have been previously loaded. The format for input VMS time values is deduced from the attributes of the perl variable passed to the function. If the variable contains an integer, LONGINT format is assumed. If the variable containes a floating point value, FLOAT format is assumed. If the variable is a string with a leading '0x', HEX format is assumed. If the variable is an 8 byte string, PACK format is assumed. If the variable is a Math::BigInt object, BIGINT format is assumed. FUNCTIONS bintim - convert ascii time string to binary $bin = bintim('01-jan-2010 12:00:00.00'[,$retmode]); Converts the time string to a VMS time value. $retmode indicates the format for the returned value as described in the overview section. asctim - convert binary time to ascii string $text = asctim([$bin]) Converts an OpenVMS time to its textual presentation. If a binary time is not provided, the current time is used. gettim - get current time as binary $bin = gettim([$retmode]); Returns the current time. $retmode specifies the format of the returned value as described in the overview section. numtim - get current time as array or convert binary time to array @a = numtim(); # current time @a = numtim($bin); # supplied time value Returns an array of numeric values representing the current time. The values are returned in the order year, month, day, hour, minute, second, hundredth of seconds. If no binary time value is provided the current time is used. epoch_to_vms - convert unix epoch time value to vms time $bin = epoch_to_vms($tm); Converts the provided unix time value to OpenVMS binary time format. vms_to_epoch - convert vms time to unix epoch time value $tm = vms_to_epoch($bin); Converts an 8 byte OpenVMS binary time to a unix time value. SEE ALSO See the OpenVMS System Services Reference Manual for descriptions of the referenced system services. AUTHOR Thomas Pfau, <tfpfau@gmail.com<gt> COPYRIGHT AND LICENSE VMS::Time is Copyright (C) 2013 by Thomas Pfau This module is free software. You can redistribute it and/or modify it under the terms of the Artistic License 2.0. This module is distributed in the hope that it will be useful but it is provided "as is"and without any express or implied warranties. http://www.nntp.perl.org/group/perl.vmsperl/2013/01/msg15589.html Tue, 01 Jan 2013 20:26:19 +0000 Re: VMS::Time module by Thomas Pfau I was thinking about this today and thought of another way to select the return format. What if the routines that returned a VMS time value had an extra argument indicating what format to return it in? Constants for the format argument could be provided by the module. The possible formats could include 8 byte string (packed format), integer (if 64 bit integer support is built into perl), or float. Does this sound like a more usable interface? For example: $tm1 = gettim(VMSTM_PACK); $tm2 = bintim('31-DEC-2012 18:00', VMSTM_FLOAT); It was suggested to return a list of values but then the caller needs to know which entry in the returned list is in the desired format. It also means returning multiple values when the caller probably only wants one. On Mon, Dec 24, 2012 at 5:19 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > I wrote a time module that interfaces to the VMS time system services - > $BINTIM, $ASCTIM, $GETTIM, and $NUMTIM. I also had a replacement routines > for $ASCTIM, $BINTIM and $GETTIM that could be used on non-VMS platforms. > > Currently it accepts and returns VMS time buffers as 8 byte strings but I > was thinking of allowing numeric values to be passed if perl was built with > 64 bit integer support. I could detect the input format by using > SvIOK/SvPOK. The problem I have is determining how the user wants the > information returned. > > Current interface ($now and $bin are 8 byte strings containing the time): > $now = gettim(); > $bin = bintim('01-jan-2010 12:00:00.00'); > $asc = asctim($bin); > ($year, $month, $day, $hr, $mn, $sc, $cc) = numtim($bin); > > I'm thinking of using an optional additional argument on gettim and bintim > that would be written with the 8 byte string and have the routines return > the time as an integer if perl is built with 64 bit integers. I could try > to interface to the bigint module and return a bigint value if 64 bit > integers aren't available. > > Would anyone find this useful? Any comments on the interface? > > -- > Thomas Pfau > tfpfau@gmail.com > http://www.linkedin.com/in/thomaspfau > http://nbpfaus.net/~pfau/ -- Thomas Pfau tfpfau@gmail.com http://www.linkedin.com/in/thomaspfau http://nbpfaus.net/~pfau/ http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15588.html Mon, 31 Dec 2012 23:57:38 +0000 5.16.2 build by Thomas Pfau I finally got 5.16.2 to complete the build process on Integrity today. Apparently DECC$READDIR_DROPDOTNOTYPE enabled causes problems. We have that set at work for something else. I had to define it locally to "disabled" and the build completed. Also, I haven't had any luck building on an ODS-5 volume on either Alpha or Integrity. Tests are running now. -- Thomas Pfau tfpfau@gmail.com http://www.linkedin.com/in/thomaspfau http://nbpfaus.net/~pfau/ http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15587.html Mon, 31 Dec 2012 18:32:33 +0000 Re: VMS::Time module by Craig A. Berry On Dec 27, 2012, at 8:52 PM, John E. Malmberg <malmberg@Encompasserve.org> wrote: > On 12/24/2012 4:19 PM, Thomas Pfau wrote: >> I wrote a time module that interfaces to the VMS time system services - >> $BINTIM, $ASCTIM, $GETTIM, and $NUMTIM. I also had a replacement routines >> for $ASCTIM, $BINTIM and $GETTIM that could be used on non-VMS platforms. >> >> Currently it accepts and returns VMS time buffers as 8 byte strings but I >> was thinking of allowing numeric values to be passed if perl was built with >> 64 bit integer support. I could detect the input format by using >> SvIOK/SvPOK. The problem I have is determining how the user wants the >> information returned. > > Can you use wantarray? > >> Current interface ($now and $bin are 8 byte strings containing the time): >> $now = gettim(); >> $bin = bintim('01-jan-2010 12:00:00.00'); >> $asc = asctim($bin); >> ($year, $month, $day, $hr, $mn, $sc, $cc) = numtim($bin); >> >> I'm thinking of using an optional additional argument on gettim and bintim >> that would be written with the 8 byte string and have the routines return >> the time as an integer if perl is built with 64 bit integers. I could try >> to interface to the bigint module and return a bigint value if 64 bit >> integers aren't available. > >> Would anyone find this useful? Any comments on the interface? It looks like a good translation into Perl of the native time routines. > > It might be useful. As I posted earlier, I am looking at what it would take to implement a perl script that could be run detached to keep a VMS directory synchronized with Dropbox. > > While I have not yet started my investigation, I suspect that I will need to convert time stamps from the DropBox server to that of the VMS server. These time stamps might be in Windows format or Linux format, so I would need a way to convert and compare the timestamps, hopefully with the least loss of precision. A very long time ago Dan Sugalski posted an example of converting VMS quadword dates into Unix seconds since the epoch: <http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/1998-11/msg00063.html> That gives you the seconds in a a double, which is good enough up until the year 3000 or so. ________________________________________ Craig A. Berry mailto:craigberry@mac.com "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15586.html Sat, 29 Dec 2012 14:22:48 +0000 Re: VMS::Time module by John E. Malmberg On 12/24/2012 4:19 PM, Thomas Pfau wrote: > I wrote a time module that interfaces to the VMS time system services - > $BINTIM, $ASCTIM, $GETTIM, and $NUMTIM. I also had a replacement routines > for $ASCTIM, $BINTIM and $GETTIM that could be used on non-VMS platforms. > > Currently it accepts and returns VMS time buffers as 8 byte strings but I > was thinking of allowing numeric values to be passed if perl was built with > 64 bit integer support. I could detect the input format by using > SvIOK/SvPOK. The problem I have is determining how the user wants the > information returned. Can you use wantarray? > Current interface ($now and $bin are 8 byte strings containing the time): > $now = gettim(); > $bin = bintim('01-jan-2010 12:00:00.00'); > $asc = asctim($bin); > ($year, $month, $day, $hr, $mn, $sc, $cc) = numtim($bin); > > I'm thinking of using an optional additional argument on gettim and bintim > that would be written with the 8 byte string and have the routines return > the time as an integer if perl is built with 64 bit integers. I could try > to interface to the bigint module and return a bigint value if 64 bit > integers aren't available. > Would anyone find this useful? Any comments on the interface? It might be useful. As I posted earlier, I am looking at what it would take to implement a perl script that could be run detached to keep a VMS directory synchronized with Dropbox. While I have not yet started my investigation, I suspect that I will need to convert time stamps from the DropBox server to that of the VMS server. These time stamps might be in Windows format or Linux format, so I would need a way to convert and compare the timestamps, hopefully with the least loss of precision. Regards, -John Personal Opinion Only http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15585.html Fri, 28 Dec 2012 02:54:28 +0000 VMS::Time module by Thomas Pfau I wrote a time module that interfaces to the VMS time system services - $BINTIM, $ASCTIM, $GETTIM, and $NUMTIM. I also had a replacement routines for $ASCTIM, $BINTIM and $GETTIM that could be used on non-VMS platforms. Currently it accepts and returns VMS time buffers as 8 byte strings but I was thinking of allowing numeric values to be passed if perl was built with 64 bit integer support. I could detect the input format by using SvIOK/SvPOK. The problem I have is determining how the user wants the information returned. Current interface ($now and $bin are 8 byte strings containing the time): $now = gettim(); $bin = bintim('01-jan-2010 12:00:00.00'); $asc = asctim($bin); ($year, $month, $day, $hr, $mn, $sc, $cc) = numtim($bin); I'm thinking of using an optional additional argument on gettim and bintim that would be written with the 8 byte string and have the routines return the time as an integer if perl is built with 64 bit integers. I could try to interface to the bigint module and return a bigint value if 64 bit integers aren't available. Would anyone find this useful? Any comments on the interface? -- Thomas Pfau tfpfau@gmail.com http://www.linkedin.com/in/thomaspfau http://nbpfaus.net/~pfau/ http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15584.html Mon, 24 Dec 2012 22:19:21 +0000 Re: perl 5.16.2 build problems by Thomas Pfau I started looking through some of the failures. t/comp/parser ................................................. FAILED--unexpected output at test 0 1..123 ... ok 23 - interpolation, here doc ok 24 - ';&' sub prototype confuses the lexer # ok 25 ok 26 - eval { foo => 'bar' } ok 27 - { foo => 'bar' } ... garbage line of output appears to come from this: # Bug #21575 # ensure that the second print statement works, by playing a bit # with the test output. my %data = ( foo => "\n" ); print "#"; print( $data{foo}); $test = $test + 1; print "ok $test\n"; Pipe problem? t/op/stat ..................................................... FAILED at test 31 not ok 31 - symlink() ok # Failed test 31 - symlink() ok at [.t.op]stat.t line 223 not ok 32 - -l # Failed test 32 - -l at [.t.op]stat.t line 224 ... ok 81 - lstat $ioref reverts to regular fstat # Can't symlink [.t.op]stat.t: permission denied at [.t.op]stat.t line 485. # Looks like you planned 113 tests but ran 81. %SYSTEM-F-ABORT, abort t/op/taint .................................................... FAILED--unexpected output at test 531 Appears to be due to building with secure logical name translations. First error is this: ok 7 # skip all directories are writeable Insecure $ENV{DCL$PATH} while running with -t switch at [.t.op]taint.t line 192. Insecure dependency in popen while running with -t switch at [.t.op]taint.t line 192. not ok 8 cpan/autodie/t/Fatal .......................................... FAILED--expected test 15, saw test 17 ok 14 - Close filehandle using - \*FOO Fatal VMS error (status=114730) at DKA100:[PERL-5_16_2]VMS.C;1, line 11973 %RMS-E-FND, ACP file or directory lookup failed Fatal VMS error (status=114730) at DKA100:[PERL-5_16_2]VMS.C;1, line 11973 %RMS-E-FND, ACP file or directory lookup failed ok 16 - Package :void Fatal::opendir in scalar context ok 17 - Can't override print cpan/File-Path/t/Path ......................................... FAILED at test 66 ok 65 - bug 487319 setup not ok 66 - debian bug 487319 setup symlink # Failed test 'debian bug 487319 setup symlink' # at cpan/file-path/t/path.t line 332. # bug487319-symlink ok 67 - mask of symlink target dir unchanged (debian bug 487319) http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15583.html Mon, 24 Dec 2012 19:31:18 +0000 Re: perl 5.16.2 build problems by Craig A. Berry On Dec 24, 2012, at 5:45 AM, Thomas Pfau <tfpfau@gmail.com> wrote: > Tests completed. Results are in http://nbpfaus.net/~pfau/perltest.zip And the summary is: t/comp/parser ................................................. FAILED--unexpected output at test 0 t/op/stat ..................................................... FAILED at test 31 t/op/taint .................................................... FAILED--unexpected output at test 531 t/porting/manifest ............................................ FAILED at test 58 cpan/Archive-Extract/t/01_Archive-Extract ..................... FAILED at test 28 cpan/autodie/t/Fatal .......................................... FAILED--expected test 15, saw test 17 cpan/CPANPLUS-Dist-Build/t/02_CPANPLUS-Dist-Build ............. FAILED at test 4 cpan/CPANPLUS/t/00_CPANPLUS-Internals-Utils ................... FAILED--no leader found cpan/CPANPLUS/t/01_CPANPLUS-Configure ......................... FAILED--no leader found cpan/CPANPLUS/t/02_CPANPLUS-Internals ......................... FAILED--no leader found cpan/CPANPLUS/t/03_CPANPLUS-Internals-Source .................. FAILED--no leader found cpan/CPANPLUS/t/04_CPANPLUS-Module ............................ FAILED--no leader found cpan/CPANPLUS/t/05_CPANPLUS-Internals-Fetch ................... FAILED--no leader found cpan/CPANPLUS/t/06_CPANPLUS-Internals-Constants ............... FAILED--no leader found cpan/CPANPLUS/t/07_CPANPLUS-Internals-Extract ................. FAILED--no leader found cpan/CPANPLUS/t/08_CPANPLUS-Backend ........................... FAILED--no leader found cpan/CPANPLUS/t/09_CPANPLUS-Internals-Search .................. FAILED--no leader found cpan/CPANPLUS/t/10_CPANPLUS-Error ............................. FAILED--no leader found cpan/CPANPLUS/t/15_CPANPLUS-Shell ............................. FAILED--no leader found cpan/CPANPLUS/t/19_CPANPLUS-Dist .............................. FAILED--no leader found cpan/CPANPLUS/t/20_CPANPLUS-Dist-MM ........................... FAILED--no leader found cpan/CPANPLUS/t/21_CPANPLUS-Dist-No-Build ..................... FAILED--no leader found cpan/CPANPLUS/t/25_CPANPLUS ................................... FAILED--no leader found cpan/CPANPLUS/t/30_CPANPLUS-Internals-Selfupdate .............. FAILED--no leader found cpan/CPANPLUS/t/40_CPANPLUS-Internals-Report .................. FAILED--no leader found cpan/File-Path/t/Path ......................................... FAILED at test 66 cpan/Module-Build/t/files ..................................... FAILED--expected 4 tests, saw 0 cpan/Module-Build/t/manifypods ................................ FAILED at test 11 cpan/Module-Build/t/PL_files .................................. FAILED--expected 8 tests, saw 0 cpan/Module-Build/t/properties/dist_suffix .................... FAILED at test 2 cpan/Module-Build/t/runthrough ................................ FAILED at test 11 cpan/Module-Build/t/tilde ..................................... FAILED at test 16 cpan/Module-Metadata/t/metadata ............................... FAILED at test 114 cpan/Test-Harness/t/unicode ................................... FAILED--no leader found cpan/Time-HiRes/t/alarm ....................................... FAILED at test 7 cpan/Time-HiRes/t/ualarm ...................................... FAILED at test 8 dist/Cwd/t/cwd ................................................ FAILED at test 23 dist/ExtUtils-Command/t/cp .................................... FAILED at test 1 lib/File/Copy ................................................. FAILED--expected 463 tests, saw 27 lib/File/Find/t/find .......................................... FAILED at test 10 lib/File/Find/t/taint ......................................... FAILED at test 10 lib/perl5db ................................................... FAILED at test 18 lib/vmsish .................................................... FAILED at test 22 Failed 43 tests out of 2155, 98.00% okay. Which is a lot more than I usually get. In fact here's what I get for my recent build of 5.16.2 on Alpha 8.3: t/op/stat ..................................................... FAILED at test 82 cpan/Archive-Extract/t/01_Archive-Extract ..................... FAILED at test 115 cpan/Module-Build/t/PL_files .................................. FAILED at test 3 cpan/Module-Build/t/properties/dist_suffix .................... FAILED at test 2 cpan/Module-Build/t/runthrough ................................ FAILED at test 11 cpan/Module-Build/t/tilde ..................................... FAILED at test 16 cpan/Module-Metadata/t/metadata ............................... FAILED at test 114 ext/Pod-Html/t/cache .......................................... FAILED at test 8 lib/perl5db ................................................... FAILED at test 18 Failed 9 tests out of 2111, 99.57% okay. To account for the differences, one would have to methodically go through the very large matrix of, in no particular order: 1.) Volume characteristics of the build volume, notably ODS-2 versus ODS-5, but assuming ODS-5, are access dates enabled, etc. 2.) VMS version and ECO level. 3.) CRTL ECO level. 4.) Extended parse enabled or not. 5.) Compiler version. 6.) Presence or absence of what versions of certain external utilities, notably tar. 7.) What DECC$* features, if any, are enabled. 8.) Complete configuration output from perl -"V". A large number of the failures I'm not getting involve stat() calls, and I think there have been fixes in this area, and the Time::HiRes failures definitely point to a bug in the CRTL that has been fixed. So getting a current CRTL ECO would probably be the one thing to focus on if any of these test failures is a concern. ________________________________________ Craig A. Berry mailto:craigberry@mac.com "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15582.html Mon, 24 Dec 2012 13:38:17 +0000 Re: perl 5.16.2 build problems by Thomas Pfau Tests completed. Results are in http://nbpfaus.net/~pfau/perltest.zip -- Thomas Pfau tfpfau@gmail.com http://www.linkedin.com/in/thomaspfau http://nbpfaus.net/~pfau/ http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15581.html Mon, 24 Dec 2012 11:45:30 +0000 Re: perl 5.16.2 build problems by Thomas Pfau I started over, told it not to use mixed case symbols, and after about 4.25 hours it appears to have completed successfully. Now to start the tests.... On Sun, Dec 23, 2012 at 2:01 PM, Craig A. Berry <craigberry@mac.com> wrote: > > On Dec 23, 2012, at 12:52 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > > > Some defaults aren't restored properly when re-executing configure.com. > > > > Enable thread upcalls? [n] y > > Installation prefix to use (for PERL_ROOT)? [ perl_root.] ] > dsa0:[perl-5_16_2_root.] > > What pager is used on your system? [type/pag] type/page=save=10 > > The intention is that it will read the config.sh generated by a previous > configuration if it exists and use it as your new set of defaults. This is > in imitation of what Configure does. If you don't want that behavior, you > need to make the realclean target before reconfiguring, which will removing > any existing config.sh files. > > ________________________________________ > Craig A. Berry > mailto:craigberry@mac.com > > "... getting out of a sonnet is much more > difficult than getting in." > Brad Leithauser > > -- Thomas Pfau tfpfau@gmail.com http://www.linkedin.com/in/thomaspfau http://nbpfaus.net/~pfau/ http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15580.html Mon, 24 Dec 2012 03:38:16 +0000 Re: perl 5.16.2 build problems by Craig A. Berry On Dec 23, 2012, at 12:52 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > Some defaults aren't restored properly when re-executing configure.com. > > Enable thread upcalls? [n] y > Installation prefix to use (for PERL_ROOT)? [ perl_root.] ] dsa0:[perl-5_16_2_root.] > What pager is used on your system? [type/pag] type/page=save=10 The intention is that it will read the config.sh generated by a previous configuration if it exists and use it as your new set of defaults. This is in imitation of what Configure does. If you don't want that behavior, you need to make the realclean target before reconfiguring, which will removing any existing config.sh files. ________________________________________ Craig A. Berry mailto:craigberry@mac.com "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15579.html Sun, 23 Dec 2012 19:01:46 +0000 Re: perl 5.16.2 build problems by Thomas Pfau Some defaults aren't restored properly when re-executing configure.com. Enable thread upcalls? [n] y Installation prefix to use (for PERL_ROOT)? [ perl_root.] ] dsa0:[perl-5_16_2_root.] What pager is used on your system? [type/pag] type/page=save=10 -- Thomas Pfau tfpfau@gmail.com http://www.linkedin.com/in/thomaspfau http://nbpfaus.net/~pfau/ http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15578.html Sun, 23 Dec 2012 18:53:09 +0000 Re: perl 5.16.2 build problems by Thomas Pfau Ok, I fixed that options file and now it fails on devel/ppport. I'm starting over with the case sensitive build turned off. On Sun, Dec 23, 2012 at 9:16 AM, Craig A. Berry <craigberry@mac.com> wrote: > > On Dec 23, 2012, at 7:58 AM, Thomas Pfau <tfpfau@gmail.com> wrote: > > > Ok, I just saw it. I selected the option to preserve case in symbol > names. The module gets named 'globals' but the options file calls for > 'GLOBALS'. > > Aha. Another non-default option I haven't tried in a long time. It looks > like the following line in the linker option file generator will need to > fiddle with case when that option is selected: > > $ search [.vms]gen_shrfls.pl globals > my $incstr = 'PERL,GLOBALS'; > > > ________________________________________ > Craig A. Berry > mailto:craigberry@mac.com > > "... getting out of a sonnet is much more > difficult than getting in." > Brad Leithauser > > -- Thomas Pfau tfpfau@gmail.com http://www.linkedin.com/in/thomaspfau http://nbpfaus.net/~pfau/ http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15577.html Sun, 23 Dec 2012 18:39:52 +0000 Re: perl 5.16.2 build problems by Craig A. Berry On Dec 23, 2012, at 7:58 AM, Thomas Pfau <tfpfau@gmail.com> wrote: > Ok, I just saw it. I selected the option to preserve case in symbol names. The module gets named 'globals' but the options file calls for 'GLOBALS'. Aha. Another non-default option I haven't tried in a long time. It looks like the following line in the linker option file generator will need to fiddle with case when that option is selected: $ search [.vms]gen_shrfls.pl globals my $incstr = 'PERL,GLOBALS'; ________________________________________ Craig A. Berry mailto:craigberry@mac.com "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15576.html Sun, 23 Dec 2012 14:16:13 +0000 Re: perl 5.16.2 build problems by Thomas Pfau Ok, I just saw it. I selected the option to preserve case in symbol names. The module gets named 'globals' but the options file calls for 'GLOBALS'. On Sun, Dec 23, 2012 at 8:56 AM, Thomas Pfau <tfpfau@gmail.com> wrote: > I downloaded the latest MMK and tried again. It still failed to find > module GLOBALS although it did find PERL. > > > On Sat, Dec 22, 2012 at 11:32 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > >> I zipped up the log files and config.h. You can grab it from >> http://nbpfaus.net/~pfau/perlbuild.zip. >> >> perlbuild-1.log was the first part of the build. That failed due to not >> finding dynaloader.c. I issued the MMK commands to get it generated and >> then resubmitted the build. That produced perlbuild-2.log. I started all >> of this after deleting the entire directory tree and unpacking the sources >> again. >> >> I have MMK V3.9-9. I'll try again with 4.1. >> >> >> On Sat, Dec 22, 2012 at 11:15 PM, Craig A. Berry <craigberry@mac.com>wrote: >> >>> >>> On Dec 22, 2012, at 5:14 PM, Thomas Pfau <tfpfau@gmail.com> wrote: >>> >>> > My build had problems with DynLoader which I was able to get past with >>> 'mmk dynloader.xs', 'mmk dynloader.c', 'mmk all'. >>> >>> I didn't have that problem. I don't know if it makes a difference, but >>> I was using MMK 4.1 for this. >>> >>> > After that I restarted the full build. It died with the following >>> while building in dist/Cwd: >>> > >>> > Link /NoTrace/NoMap /Shareable=[--.LIB.AUTO.CWD]PL_CWD.EXE >>> Cwd.opt/Option,[--]perlshr_attr.opt/Option >>> > %LINK-W-SHRWRNERS, compilation warnings >>> > in shareable image file >>> DISK$USERS:[pfau.FREEWARE.perl-5_16_2]PERLSHR.EXE;1 >>> > %MMK-F-ERRUPD, error status %X10648268 occurred when updating target >>> [--.LIB.AUTO.CWD]PL_CWD.EXE >>> > %MMK-F-ERRUPD, error status %X10648268 occurred when updating target >>> [--.LIB.AUTO.CWD]PL_CWD.EXE >>> > Unsuccessful make(dist/Cwd): code=1024 at make_ext.pl line 466. >>> > %NONAME-F-NOMSG, Message number 0C14803C >>> > %MMK-F-ERRUPD, error status %X0C14803C occurred when updating target >>> DYNEXT >>> >>> This is almost certainly a symptom of not getting completely cleaned up >>> after the compiler warnings you reported earlier. >>> >>> > >>> > I looked further up in the build log and found this: >>> > >>> > Link /NoTrace/NoMap/Share=PERLSHR.EXE DynaLoader.obj, >>> []perlshr_bld.opt/Option, perlshr_attr.opt/Option >>> > %LINK-W-NOSUCHMOD, module PERL not found >>> > in library DISK$USERS:[pfau.FREEWARE.perl-5_16_2]LIBPERL.OLB;1 >>> > %LINK-W-NOSUCHMOD, module GLOBALS not found >>> > in library DISK$USERS:[pfau.FREEWARE.perl-5_16_2]LIBPERL.OLB;1 >>> > Link /NoTrace/NoMap/THREADS=(MULTIPLE_KERNEL,UPCALLS)/Exe=PERL.EXE >>> perlmain.obj, perlshr.opt/Option, perlshr_attr.opt/Option ,[]crt$ >>> > %LINK-W-SHRWRNERS, compilation warnings >>> > in shareable image file >>> DISK$USERS:[pfau.FREEWARE.perl-5_16_2]PERLSHR.EXE;1 >>> > >>> > Any ideas? >>> >>> Something went wrong compiling globals.c and/or perl.c. If you have >>> compiler warnings or failures that we haven't addressed yet, that would be >>> the place to start. If there aren't any that we haven't dealt with, then >>> you haven't been getting the results of the previous compiles cleaned up >>> adequately. >>> >>> > BTW, is threading supported on VMS? >>> >>> It is, but you don't get it unless you configure with -"Dusethreads". >>> My link looked like: >>> >>> $ sea sys$login:build_5_16_2.log "exe=perl" >>> Link /NoTrace/NoMap/Exe=PERL.EXE perlmain.obj, perlshr.opt/Option, >>> perlshr_attr.opt/Option ,[]crtl.opt/Options >>> >>> >>> ________________________________________ >>> Craig A. Berry >>> mailto:craigberry@mac.com >>> >>> "... getting out of a sonnet is much more >>> difficult than getting in." >>> Brad Leithauser >>> >>> >> >> >> -- >> Thomas Pfau >> tfpfau@gmail.com >> http://www.linkedin.com/in/thomaspfau >> http://nbpfaus.net/~pfau/ >> > > > > -- > Thomas Pfau > tfpfau@gmail.com > http://www.linkedin.com/in/thomaspfau > http://nbpfaus.net/~pfau/ > -- Thomas Pfau tfpfau@gmail.com http://www.linkedin.com/in/thomaspfau http://nbpfaus.net/~pfau/ http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15575.html Sun, 23 Dec 2012 13:58:23 +0000 Re: perl 5.16.2 build problems by Thomas Pfau I downloaded the latest MMK and tried again. It still failed to find module GLOBALS although it did find PERL. On Sat, Dec 22, 2012 at 11:32 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > I zipped up the log files and config.h. You can grab it from > http://nbpfaus.net/~pfau/perlbuild.zip. > > perlbuild-1.log was the first part of the build. That failed due to not > finding dynaloader.c. I issued the MMK commands to get it generated and > then resubmitted the build. That produced perlbuild-2.log. I started all > of this after deleting the entire directory tree and unpacking the sources > again. > > I have MMK V3.9-9. I'll try again with 4.1. > > > On Sat, Dec 22, 2012 at 11:15 PM, Craig A. Berry <craigberry@mac.com>wrote: > >> >> On Dec 22, 2012, at 5:14 PM, Thomas Pfau <tfpfau@gmail.com> wrote: >> >> > My build had problems with DynLoader which I was able to get past with >> 'mmk dynloader.xs', 'mmk dynloader.c', 'mmk all'. >> >> I didn't have that problem. I don't know if it makes a difference, but I >> was using MMK 4.1 for this. >> >> > After that I restarted the full build. It died with the following >> while building in dist/Cwd: >> > >> > Link /NoTrace/NoMap /Shareable=[--.LIB.AUTO.CWD]PL_CWD.EXE >> Cwd.opt/Option,[--]perlshr_attr.opt/Option >> > %LINK-W-SHRWRNERS, compilation warnings >> > in shareable image file >> DISK$USERS:[pfau.FREEWARE.perl-5_16_2]PERLSHR.EXE;1 >> > %MMK-F-ERRUPD, error status %X10648268 occurred when updating target >> [--.LIB.AUTO.CWD]PL_CWD.EXE >> > %MMK-F-ERRUPD, error status %X10648268 occurred when updating target >> [--.LIB.AUTO.CWD]PL_CWD.EXE >> > Unsuccessful make(dist/Cwd): code=1024 at make_ext.pl line 466. >> > %NONAME-F-NOMSG, Message number 0C14803C >> > %MMK-F-ERRUPD, error status %X0C14803C occurred when updating target >> DYNEXT >> >> This is almost certainly a symptom of not getting completely cleaned up >> after the compiler warnings you reported earlier. >> >> > >> > I looked further up in the build log and found this: >> > >> > Link /NoTrace/NoMap/Share=PERLSHR.EXE DynaLoader.obj, >> []perlshr_bld.opt/Option, perlshr_attr.opt/Option >> > %LINK-W-NOSUCHMOD, module PERL not found >> > in library DISK$USERS:[pfau.FREEWARE.perl-5_16_2]LIBPERL.OLB;1 >> > %LINK-W-NOSUCHMOD, module GLOBALS not found >> > in library DISK$USERS:[pfau.FREEWARE.perl-5_16_2]LIBPERL.OLB;1 >> > Link /NoTrace/NoMap/THREADS=(MULTIPLE_KERNEL,UPCALLS)/Exe=PERL.EXE >> perlmain.obj, perlshr.opt/Option, perlshr_attr.opt/Option ,[]crt$ >> > %LINK-W-SHRWRNERS, compilation warnings >> > in shareable image file >> DISK$USERS:[pfau.FREEWARE.perl-5_16_2]PERLSHR.EXE;1 >> > >> > Any ideas? >> >> Something went wrong compiling globals.c and/or perl.c. If you have >> compiler warnings or failures that we haven't addressed yet, that would be >> the place to start. If there aren't any that we haven't dealt with, then >> you haven't been getting the results of the previous compiles cleaned up >> adequately. >> >> > BTW, is threading supported on VMS? >> >> It is, but you don't get it unless you configure with -"Dusethreads". My >> link looked like: >> >> $ sea sys$login:build_5_16_2.log "exe=perl" >> Link /NoTrace/NoMap/Exe=PERL.EXE perlmain.obj, perlshr.opt/Option, >> perlshr_attr.opt/Option ,[]crtl.opt/Options >> >> >> ________________________________________ >> Craig A. Berry >> mailto:craigberry@mac.com >> >> "... getting out of a sonnet is much more >> difficult than getting in." >> Brad Leithauser >> >> > > > -- > Thomas Pfau > tfpfau@gmail.com > http://www.linkedin.com/in/thomaspfau > http://nbpfaus.net/~pfau/ > -- Thomas Pfau tfpfau@gmail.com http://www.linkedin.com/in/thomaspfau http://nbpfaus.net/~pfau/ http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15574.html Sun, 23 Dec 2012 13:56:22 +0000 Re: perl 5.16.2 build problems by Thomas Pfau I zipped up the log files and config.h. You can grab it from http://nbpfaus.net/~pfau/perlbuild.zip. perlbuild-1.log was the first part of the build. That failed due to not finding dynaloader.c. I issued the MMK commands to get it generated and then resubmitted the build. That produced perlbuild-2.log. I started all of this after deleting the entire directory tree and unpacking the sources again. I have MMK V3.9-9. I'll try again with 4.1. On Sat, Dec 22, 2012 at 11:15 PM, Craig A. Berry <craigberry@mac.com> wrote: > > On Dec 22, 2012, at 5:14 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > > > My build had problems with DynLoader which I was able to get past with > 'mmk dynloader.xs', 'mmk dynloader.c', 'mmk all'. > > I didn't have that problem. I don't know if it makes a difference, but I > was using MMK 4.1 for this. > > > After that I restarted the full build. It died with the following > while building in dist/Cwd: > > > > Link /NoTrace/NoMap /Shareable=[--.LIB.AUTO.CWD]PL_CWD.EXE > Cwd.opt/Option,[--]perlshr_attr.opt/Option > > %LINK-W-SHRWRNERS, compilation warnings > > in shareable image file > DISK$USERS:[pfau.FREEWARE.perl-5_16_2]PERLSHR.EXE;1 > > %MMK-F-ERRUPD, error status %X10648268 occurred when updating target > [--.LIB.AUTO.CWD]PL_CWD.EXE > > %MMK-F-ERRUPD, error status %X10648268 occurred when updating target > [--.LIB.AUTO.CWD]PL_CWD.EXE > > Unsuccessful make(dist/Cwd): code=1024 at make_ext.pl line 466. > > %NONAME-F-NOMSG, Message number 0C14803C > > %MMK-F-ERRUPD, error status %X0C14803C occurred when updating target > DYNEXT > > This is almost certainly a symptom of not getting completely cleaned up > after the compiler warnings you reported earlier. > > > > > I looked further up in the build log and found this: > > > > Link /NoTrace/NoMap/Share=PERLSHR.EXE DynaLoader.obj, > []perlshr_bld.opt/Option, perlshr_attr.opt/Option > > %LINK-W-NOSUCHMOD, module PERL not found > > in library DISK$USERS:[pfau.FREEWARE.perl-5_16_2]LIBPERL.OLB;1 > > %LINK-W-NOSUCHMOD, module GLOBALS not found > > in library DISK$USERS:[pfau.FREEWARE.perl-5_16_2]LIBPERL.OLB;1 > > Link /NoTrace/NoMap/THREADS=(MULTIPLE_KERNEL,UPCALLS)/Exe=PERL.EXE > perlmain.obj, perlshr.opt/Option, perlshr_attr.opt/Option ,[]crt$ > > %LINK-W-SHRWRNERS, compilation warnings > > in shareable image file > DISK$USERS:[pfau.FREEWARE.perl-5_16_2]PERLSHR.EXE;1 > > > > Any ideas? > > Something went wrong compiling globals.c and/or perl.c. If you have > compiler warnings or failures that we haven't addressed yet, that would be > the place to start. If there aren't any that we haven't dealt with, then > you haven't been getting the results of the previous compiles cleaned up > adequately. > > > BTW, is threading supported on VMS? > > It is, but you don't get it unless you configure with -"Dusethreads". My > link looked like: > > $ sea sys$login:build_5_16_2.log "exe=perl" > Link /NoTrace/NoMap/Exe=PERL.EXE perlmain.obj, perlshr.opt/Option, > perlshr_attr.opt/Option ,[]crtl.opt/Options > > > ________________________________________ > Craig A. Berry > mailto:craigberry@mac.com > > "... getting out of a sonnet is much more > difficult than getting in." > Brad Leithauser > > -- Thomas Pfau tfpfau@gmail.com http://www.linkedin.com/in/thomaspfau http://nbpfaus.net/~pfau/ http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15573.html Sun, 23 Dec 2012 04:32:55 +0000 Re: perl 5.16.2 build problems by Craig A. Berry On Dec 22, 2012, at 5:14 PM, Thomas Pfau <tfpfau@gmail.com> wrote: > My build had problems with DynLoader which I was able to get past with 'mmk dynloader.xs', 'mmk dynloader.c', 'mmk all'. I didn't have that problem. I don't know if it makes a difference, but I was using MMK 4.1 for this. > After that I restarted the full build. It died with the following while building in dist/Cwd: > > Link /NoTrace/NoMap /Shareable=[--.LIB.AUTO.CWD]PL_CWD.EXE Cwd.opt/Option,[--]perlshr_attr.opt/Option > %LINK-W-SHRWRNERS, compilation warnings > in shareable image file DISK$USERS:[pfau.FREEWARE.perl-5_16_2]PERLSHR.EXE;1 > %MMK-F-ERRUPD, error status %X10648268 occurred when updating target [--.LIB.AUTO.CWD]PL_CWD.EXE > %MMK-F-ERRUPD, error status %X10648268 occurred when updating target [--.LIB.AUTO.CWD]PL_CWD.EXE > Unsuccessful make(dist/Cwd): code=1024 at make_ext.pl line 466. > %NONAME-F-NOMSG, Message number 0C14803C > %MMK-F-ERRUPD, error status %X0C14803C occurred when updating target DYNEXT This is almost certainly a symptom of not getting completely cleaned up after the compiler warnings you reported earlier. > > I looked further up in the build log and found this: > > Link /NoTrace/NoMap/Share=PERLSHR.EXE DynaLoader.obj, []perlshr_bld.opt/Option, perlshr_attr.opt/Option > %LINK-W-NOSUCHMOD, module PERL not found > in library DISK$USERS:[pfau.FREEWARE.perl-5_16_2]LIBPERL.OLB;1 > %LINK-W-NOSUCHMOD, module GLOBALS not found > in library DISK$USERS:[pfau.FREEWARE.perl-5_16_2]LIBPERL.OLB;1 > Link /NoTrace/NoMap/THREADS=(MULTIPLE_KERNEL,UPCALLS)/Exe=PERL.EXE perlmain.obj, perlshr.opt/Option, perlshr_attr.opt/Option ,[]crt$ > %LINK-W-SHRWRNERS, compilation warnings > in shareable image file DISK$USERS:[pfau.FREEWARE.perl-5_16_2]PERLSHR.EXE;1 > > Any ideas? Something went wrong compiling globals.c and/or perl.c. If you have compiler warnings or failures that we haven't addressed yet, that would be the place to start. If there aren't any that we haven't dealt with, then you haven't been getting the results of the previous compiles cleaned up adequately. > BTW, is threading supported on VMS? It is, but you don't get it unless you configure with -"Dusethreads". My link looked like: $ sea sys$login:build_5_16_2.log "exe=perl" Link /NoTrace/NoMap/Exe=PERL.EXE perlmain.obj, perlshr.opt/Option, perlshr_attr.opt/Option ,[]crtl.opt/Options ________________________________________ Craig A. Berry mailto:craigberry@mac.com "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser http://www.nntp.perl.org/group/perl.vmsperl/2012/12/msg15572.html Sun, 23 Dec 2012 04:15:40 +0000