RE: ODS-5 Filenames
Cheers Craig. I'll go back to Sanface and see if they're willing to change the code at source. Rob. -Original Message- *** Any opinions expressed in email are those of the individual and not necessarily those of the company. This email and any files transmitted with it are confidential and solely for the use of the intended recipient or entity to who they are addressed. It may contain material protected by attorney-client privilege. If you are not the intended recipient, or a person responsible for delivering to the intended recipient, be advised that you have received this email in error and that any use is strictly prohibited. Random House Group +44 (0) 20 7840 8400. http://www.randomhouse.co.uk http://www.booksattransworld.co.uk http://www.kidsatrandomhouse.co.uk *** From: Craig Berry [mailto:[EMAIL PROTECTED] Sent: 09 February 2005 20:32 To: Atkinson, Robert Cc: vmsperl@perl.org Subject: Re: ODS-5 Filenames On Wednesday, February 09, 2005, at 08:47AM, Atkinson, Robert [EMAIL PROTECTED] wrote: I'm using TXT2PDF from Sanface Software. We've converted some of our disks to ODS-5, but now find that the files generated from uppercase filenames are created in lower case. Perl follows the legacy CRTL behavior of downcasing filenames. We plan to honor DECC$EFS_CASE_PRESERVE at some point, but there is a fair amount of work to be done yet to get that working. In the meantime, it looks like sysopen will create in upper case: $ perl -e use Fcntl; sysopen(FH, 'FOO.BAR', O_WRONLY | O_TRUNC | O_CREAT) or die $!; $ dir foo.bar Directory D1:[CRAIG] FOO.BAR;1 Total of 1 file.
Re: Quotas and disk space requirements for build/test Perl?
Michael G Schwern wrote: On Wed, Feb 09, 2005 at 10:30:04PM -0500, John E. Malmberg wrote: Except won't that number change based on compiler and architecture not to mention keeping it up to date with each version of Perl? Is disk really that expensive? I had to dedicate an RF72 on my VAX 4000-500 in order to do a debug build. I can not afford to add more disks to my hobby system, as all three DSSI bays are full, and I do not have a DSSI to SCSI converter. Disk space can be a premium on older or hobby systems. I have run out of disk space on two systems that I have attempted to do debug builds. But disk space is the minor issue compared to the quotas. Or am I just missing something being a Unix user? I am having issues with the testing phase hanging, and I am assuming that it is process quota related. -John [EMAIL PROTECTED] Personal Opinion Only
Smoke [5.8.6] 23944 FAIL(M) openvms V7.2 (VAX/2 cpu)
Automated smoke report for 5.8.6 patch 23944 FAFNER: VAX 7000-720 (VAX/2 cpu) onopenvms - V7.2 using CC/DECC version 60490005 smoketime 3 hours 38 minutes (average 1 hour 49 minutes) Summary: FAIL(M) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = make test-prep 23944 Configuration (common) none --- - ? ? M - -Duser_c_flags=/FLOAT=G_FLOAT | | | +- PERLIO = perlio -Dusevmsdebug | | +--- PERLIO = stdio -Dusevmsdebug | +- PERLIO = perlio +--- PERLIO = stdio MANIFEST did not declare 'EXTRA.PODS' MANIFEST did not declare 'PERL_SETUP.COM' MANIFEST did not declare 'T/FOO' MANIFEST did not declare 'T/TMP0001' MANIFEST did not declare 'T/TMP0002' MANIFEST did not declare 'T/TMP0003' MANIFEST did not declare 'T/TMP0004' MANIFEST did not declare 'T/TMP0005' MANIFEST did not declare 'T/TMP0006' MANIFEST did not declare 'T/TMP0007' MANIFEST did not declare 'T/TMP0008' MANIFEST did not declare 'T/TMP0009' MANIFEST did not declare 'T/TMP0010' MANIFEST did not declare 'T/TMP0011' MANIFEST did not declare 'T/TMP0012' MANIFEST did not declare 'T/TMP0013' MANIFEST did not declare 'T/TMP0014' -- Report by Test::Smoke v1.19_61 build 799 running on perl 5.8.0 (Reporter v0.019 / Smoker v0.021)
Re: Quotas and disk space requirements for build/test Perl?
At 10:30 PM -0500 2/9/05, John E. Malmberg wrote: Is there some documentation on how much disk space is needed to build and test Perl normally or in debug? Not really. As Michael suggests, it would be a rather large matrix, and would require a pretty significant effort to maintain. But here's what I have for a non-cleaned-up debug build directory of a recent bleadperl on Alpha: $ dir/size/grand [...] Grand total of 500 directories, 5565 files, 671845 blocks. Obviously that would be less on VAX, and probably more on Itanium, given the differences in object code size. The debug build appears to be very large, this mainly seems to be from the listing files. A debug build with out the listing files might be easier to manage. Once upon a time, /LIST/SHOW=ALL was not quite so generous with the information it gave you. But now it gives you, for example, a complete 15-page listing of all possible compiler messages and it gives it to you again in each listing file. You might just replace the DBGSPECFLAGS macro in your descrip.mms with something more to your liking. You might also replace the /MAP with /NOMAP on the LINK commands if you don't think you'll need the map files. Also can some guidance be given on what account quotas are needed for the different platforms? Once these are known, it should not be hard to add them to the configure.com script to do a sanity check. Quotas to build or quotas to install and run? Either or both would be nice to have, but very painstaking to develop and obsolete almost immediately. It's certainly worth discussing what sort of limits people run into, though, and trying to develop some general advice. The test suite is a heavy user and abuser of subprocesses and pipes, so make sure your PRCLM and BYTLM are generous. The default PRCLM of 2 on VAX is almost certainly inadequate. -- Craig A. Berry mailto:[EMAIL PROTECTED] ... getting out of a sonnet is much more difficult than getting in. Brad Leithauser
Smoke [5.9.2] 23956 FAIL(M) openvms V7.2 (VAX/2 cpu)
Automated smoke report for 5.9.2 patch 23956 FAFNER: VAX 7000-720 (VAX/2 cpu) onopenvms - V7.2 using CC/DECC version 60490005 smoketime 3 hours 1 minute (average 1 hour 30 minutes) Summary: FAIL(M) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = make test-prep 23956 Configuration (common) none --- - M - M - -Duser_c_flags=/FLOAT=G_FLOAT | | | +- PERLIO = perlio -Dusevmsdebug | | +--- PERLIO = stdio -Dusevmsdebug | +- PERLIO = perlio +--- PERLIO = stdio MANIFEST did not declare 'LIB/CONFIG.POD' MANIFEST did not declare 'PERL_SETUP.COM' -- Report by Test::Smoke v1.19_61 build 799 running on perl 5.8.0 (Reporter v0.019 / Smoker v0.021)
lstat() and hardlinks start with OpenVMS 7.3-1
On Sun, 6 Feb 2005, Craig A. Berry wrote: We'll have to explicitly test for lstat in configure.com, including some sort of test that it not only is present in the CRTL but actually works, i.e., has the underlying OS support. According to the new features documentation for 7.3-1, link() and the related routines except for symlink() were implemented and supported. The link() routine only works on ODS-5 volumes that have been enabled for hardlinks. Currently if you build perl with d_link and friends, defined, two perl modules will attempt use it to create hard links instead of copies on the build disk in at least two places. So that would imply that the build disk needs to be ODS-5 and have hard links enabled. The only issue with that is that the f$getdvi() call to let you that information does not seem to have shown up until OpenVMS 8.2. I have not checked if SYS$GETDVI() will return that information or if for older versions the output of show device/full would be needed. Once you get past that, those two perl modules still fail to create the hard link because they have VMS specific code to append .com to the file they are creating where it is created, but that file extension is not there when the new name is linked, or a copy made. It appears that the syscopy module calls an rmscopy module that somehow figures out to try some extensions. Those modules are: Directory BUILD_ROOT:[00.utils] c2ph.PL;1 76 10-FEB-2005 13:24:12.81 (RWED,RWED,RE,) Directory BUILD_ROOT:[00.x2p] s2p.PL;1 107 10-FEB-2005 15:22:08.05 (RWED,RWED,RE,) So in order to get the build to complete, these modules need to be changed to either always copy on OpenVMS, or use the extension on the link operation. I have not checked the perl source to see if there are other places hard links are used where I did not have to make any changes. symlinks() will be a different issue, and they will likely require POSIX style filespecifications given to them. -John [EMAIL PROTECTED] Personal Opinion Only
Re: Quotas and disk space requirements for build/test Perl?
On Thu, 10 Feb 2005, Michael G Schwern wrote: On Thu, Feb 10, 2005 at 07:27:43AM -0500, John E. Malmberg wrote: I had to dedicate an RF72 on my VAX 4000-500 in order to do a debug build. I can not afford to add more disks to my hobby system, as all three DSSI bays are full, and I do not have a DSSI to SCSI converter. Disk space can be a premium on older or hobby systems. I have run out of disk space on two systems that I have attempted to do debug builds. Obviously I am missing something. Can't you pick up a used 10 gig IDE disk for $20 these days? The adapters to connect it to a VAX that does not have built in SCSI will cost at least $300 to $1000 for the Q-BUS to SCSI (used and apparently still in high demand) + the IDE to SCSI converter which was a few hundred $ the last time I checked with no one yet admitting to have gotten that unspported configuration to work. Some of the IDE to SCSI converters are known not to work with OpenVMS because they have not implmented the SCSI features that OpenVMS uses. A Russian posted the schematics for their Q-BUS to IDE adapter on the Internet a few years back. The drivers are only for 4.x of VAX/VMS. Only some of the later generation of Alpha systems can take IDE drives, and then they are limited to 137 GB. Just how big are these debug builds? The one that I just got completed is showing to be 1.37 GB in size. Out of a 4 GB disk. I notice that there is some mention in the documenation of Perl that indicates that it is currently about 80 MB of source. Or are we talking some really old hardware here? Old OpenVMS systems seem to stick around for ever. :-) -John [EMAIL PROTECTED] Personal Opinion Only
Smoke [5.9.2] 23960 FAIL(M) openvms V7.2 (VAX/2 cpu)
Automated smoke report for 5.9.2 patch 23960 FAFNER: VAX 7000-720 (VAX/2 cpu) onopenvms - V7.2 using CC/DECC version 60490005 smoketime 3 hours 5 minutes (average 1 hour 32 minutes) Summary: FAIL(M) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = make test-prep 23960 Configuration (common) none --- - M - M - -Duser_c_flags=/FLOAT=G_FLOAT | | | +- PERLIO = perlio -Dusevmsdebug | | +--- PERLIO = stdio -Dusevmsdebug | +- PERLIO = perlio +--- PERLIO = stdio MANIFEST did not declare 'LIB/CONFIG.POD' MANIFEST did not declare 'PERL_SETUP.COM' -- Report by Test::Smoke v1.19_61 build 799 running on perl 5.8.0 (Reporter v0.019 / Smoker v0.021)
