autosplit.t needs an update for when VMS is operating in case preserved
mode.
blib.t can not use the VMS hack around the CATDIR when VMS CRTL is in
UNIX mode.
vmsish.t has a problem that is common to a lot of the tests.
When VMS CRTL is in UNIX mode, the program name is returned as a UNIX
h2xs.t change is that when the CRTL features DECC$READDIR_DROPDOTNOTYPE
and DECC$UNIX_FILENAME_REPORT is in effect, there will not be a trailing
dot on UNIX names returned by readdir().
cwd.pm changes are more interesting.
With OpenVMS future that supports symbolic links, there will be a
I have not tested this or anything on 5.8.7, I am in the process of
moving my changes over to 5.8.7.
In this case it is a simple change, in when VMS is in UNIX mode, it
needs to get the tempfile name returned to it in UNIX mode.
-John
[EMAIL PROTECTED]
Personal Opinion Only
---
A quick and dirty hack for spec.t so that tests will produce valid
results when the CRTL is in UNIX mode. I am sure that there is a better
way to do this.
I had the same problem with the the file that becomes vmsfspec.t, but
was unable to find a way to modify it to work with the CRTL in
I have not tested this or anything on 5.8.7, I am in the process of
moving my changes over to 5.8.7.
When the CRTL is in UNIX REPORT mode, the file specification for $^X is
returned as UNIX, and can not be passed as a parameter to MCR.
In most cases, the fix is simply to remove the VMS
I have not tested this or anything on 5.8.7, I am in the process of
moving my changes over to 5.8.7.
chdir.t
This is just something I found while testing, chdir.t needs to clean up
it's changes to SYS$LOGIN so it does not mess up the VMS session when it
is run outside of the Perl test
I have not tested this or anything on 5.8.7, I am in the process of
moving my changes over to 5.8.7.
t/pod/find.t
If you want to do a VMS specific compare of directory names, you need to
make sure that the directory specification is in VMS format.
t/x2p/s2p.t
It is required to VMSIFY some
I have not tested this or anything on 5.8.7, I am in the process of
moving my changes over to 5.8.7.
I have seen no changes in 5.8.7 from the files I started with on my
5.8.6 basis.
These changes should be at most harmless until the rest of the VMS Perl
catches up with them, or at worse,
Michael G Schwern wrote:
On Thu, Jul 14, 2005 at 12:03:01PM -0400, John E. Malmberg wrote:
Ya know, if there's this many differences between your flavor of VMS
and the more traditional flavor rather than trying to wedge them both
into File::Spec::VMS and MM_VMS you should probably make a new
Michael G Schwern wrote:
On Fri, Jul 15, 2005 at 12:49:01AM -0400, John E. Malmberg wrote:
Ya know, if there's this many differences between your flavor of VMS
and the more traditional flavor rather than trying to wedge them both
into File::Spec::VMS and MM_VMS you should probably make a new
E-mail sent offline quoting, and pointing him to, the %ENV section of PERLVMS.
Thanks. I am a bit overwhelmed by the amount of Perl documentation and
have not been able to absorb all of it yet, and dealing with the %ENV
hash is not something I have fully worked out the internals with, other
Tom Edelson wrote:
One thing to consider (again from PERLVMS):
PERL_ENV_TABLES is translated once when Perl starts up; any changes you make
while Perl is running do not affect the behavior of %ENV .
That can be dealt with in several ways.
1. It can be properly set before running Perl that
Craig A. Berry wrote:
At 5:41 PM -0400 7/15/05, John Malmberg wrote:
But it seems that the need for eliminate_macros would go completely
away if Perl was setting the DCL symbols instead of the logical names,
because then MMS/MMK would see them. And I think that it does not look
hard to make
Nicholas Clark wrote:
However, VMS is currently failing to build even miniperl, due to its C
compiler being more stringent about const consistency than anything else
on the planet.
Being that stringent is important to be able to optimize code for modern
CPU chips.
If it is not easy to fix
Abe Timmerman wrote:
Hi all,
Blead on VMS is still not building. This is on the hp-testdrive machine
SPE180:
CC/DECC/NOANSI_ALIAS /Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj/
NoList/float=ieee/ieee=denorm/Define=PERL_CORE DOIO.C
if (UNLINK(s))
^
How do I reproduce this?
I pulled down perl-5.9.2 and started a build and it fails with:
CC/DECC/NOANSI_ALIAS
/Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj/List
#$d_sitecustomize USE_SITECUSTOMIZE /**/
.^
%CC-W-BADDIRECTIVE, $d_sitecustomize is an invalid
Nicholas Clark wrote:
On Sat, Jul 23, 2005 at 03:36:39PM -0400, John E. Malmberg wrote:
How do I reproduce this?
I pulled down perl-5.9.2 and started a build and it fails with:
CC/DECC/NOANSI_ALIAS
/Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj/List
#$d_sitecustomize
Abe Timmerman wrote:
Hi all,
Blead on VMS is still not building. This is on the hp-testdrive machine
SPE180:
CC/DECC/NOANSI_ALIAS /Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj/
NoList/float=ieee/ieee=denorm/Define=PERL_CORE DOIO.C
if (UNLINK(s))
^
John E. Malmberg wrote:
Abe Timmerman wrote:
Hi all,
Blead on VMS is still not building. This is on the hp-testdrive
machine SPE180:
CC/DECC/NOANSI_ALIAS
/Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj/
NoList/float=ieee/ieee=denorm/Define=PERL_CORE DOIO.C
Craig A. Berry wrote:
At 5:48 PM -0400 7/24/05, John E. Malmberg wrote:
if (UNLINK(s))
^
%CC-W-NOTCONSTQUAL, In this statement, the
And this should take care of it. Accidentally left out of my patch of two hours
ago.
--- doio.c_orig Sat Jul 23 18:54:47
John E. Malmberg wrote:
Craig A. Berry wrote:
At 5:48 PM -0400 7/24/05, John E. Malmberg wrote:
if (UNLINK(s))
^
%CC-W-NOTCONSTQUAL, In this statement, the
And this should take care of it. Accidentally left out of my patch of
I would strongly
Michael G Schwern wrote:
On Sun, Jul 24, 2005 at 07:58:27PM -0400, John E. Malmberg wrote:
Has VMS.C changed any from Perl 5.8.7?
Between bleadperl and 5.8.7? Yes. Looks like mostly elimination of
5.005threads and consting and some of that char * casting you don't like.
You can get a copy
Ok,
Here are the patches to vms.c and vmsish.h that when combined with the
other patches that I have posted will allow bleadperl to compile on VMS
up to the creation of miniperl.
I did not include the fix for the buffer high-water mark overrun as my
notes on that are at work.
The link of
Michael G Schwern wrote:
On Sun, Jul 24, 2005 at 08:57:52PM -0400, John E. Malmberg wrote:
Might I suggest you check your local copies of Perl into a local version
control system? I usually use RCS for small changes to small groups of files
or I dump the whole thing into darcs for larger
Craig A. Berry wrote:
At 11:00 PM -0400 7/24/05, John E. Malmberg wrote:
The link of miniperl is failing because of an undefined symbol in the transfer
vector.
Perl_stashpv_hvname_match.
It appears that when USE_ITHREADS is not defined, either that transfer vector
entry should
When I pulled down a new copy today, for some reason the vms/vmsish.h
was missing some of the required const prototypes in order to compile
vms.c, so I am confused as to how it seemed to be building yesterday.
I suppose I should change the subject as it is against a different days
blead, but
See note below about an issue where I may have some corrupted files
affecting the test results.
EAGLE search blead_test.log fail
t/run/exitFAILED at test 3
t/run/switchesFAILED
--unexpected output at test 15
John E. Malmberg wrote:
EAGLE search blead_test.log fail
t/run/exitFAILED at test 3
This test is failing because ${^CHILD_ERROR_NATIVE} contains a 1 and 0
is expected.
If I understand this, for VMS the native error code is a 1 for success
unless special
The existing code in the fopen() call aways fails with an invalid
argument, so the if clause following it has never been run since this
version of the code was in place.
Fixing this bug may expose other side effects as it is assuming that the
first 4 bytes of an executable are not printable.
In the code path below, the execution of the HEK_FLAGS(hek) causes the
memory for a different allocated structure to be modified, which then
causes an access violation when the corrupted value is used as an index.
This is in the module HV, routine S_share_hek_flags().
len has a value if 19 in
Nicholas Clark wrote:
On Sat, Jul 30, 2005 at 12:27:43AM -0400, John E. Malmberg wrote:
The address 10439704 was already a part of the structure that
Perl_hv_iternext_flags() had pointed a variable named iter at.
DBG exam *iter
*HV\Perl_hv_iternext_flags\iter
xhv_name: 1162633044
This test is exiting before running any tests with an undefined value
being referenced if $Config{u64size} is not defined.
-John
[EMAIL PROTECTED]
Personal Opinion Only
--- t/op/pack.t_blead Sun Jul 31 22:12:12 2005
+++ t/op/pack.t Sun Jul 31 21:59:45 2005
@@ -43,7 +43,7 @@
}
for my
The script 03examples.t is failing at test 1 because the includes seem
to be set wrong for VMS.
--- ext/compress/zlib/t/03examples_t.blead Sun Jul 31 22:54:06 2005
+++ ext/compress/zlib/t/03examples.tSun Jul 31 22:54:12 2005
@@ -42,7 +42,7 @@
my $Inc = '' ;
if ($^O eq 'VMS') {
-
Rafael Garcia-Suarez wrote:
Paul Marquess wrote:
- $Inc = '-I[.blib.lib] -I[.blib.arch]';
+ $Inc = '-I[-.lib] -I[-.arch]';
}
elsif ($^O eq 'MSWin32') {
foreach (@INC)
Is this the layout needed for running these tests when Compress::Zlib is in
the core only? Is the use of blib still
Paul Marquess wrote:
From: John E. Malmberg [mailto:[EMAIL PROTECTED]
The script 03examples.t is failing at test 1 because the includes seem
to be set wrong for VMS.
snip - answered in previous discussion
This gets the script passing up to test 10 which causes the subsequent
tests
Rafael Garcia-Suarez wrote:
John E. Malmberg wrote:
This requires fixing in multiple places.
perl.h, util.c, and embed.fnc, and this seems to require a running perl
to rebuild proto.h
Thanks, applied as change #25251.
Change #25218 needs to be backed out. Adding the (char *) cast
This bug is in the routine mp_to_vmsspec(). If it is passed a name like
/foo where foo is a logical name, with no other directories or file
names in the path, after the translation, the null terminator was always
being skipped over, and what ever was previously in that memory would
get
John E. Malmberg wrote:
Rafael Garcia-Suarez wrote:
Paul Marquess wrote:
- $Inc = '-I[.blib.lib] -I[.blib.arch]';
+ $Inc = '-I[-.lib] -I[-.arch]';
}
elsif ($^O eq 'MSWin32') {
foreach (@INC)
Is this the layout needed for running these tests when Compress::Zlib
is in
the core only
Rafael Garcia-Suarez wrote:
I think I've applied them correctly as change #25257, including backing
out the patches you mentioned.
http://public.activestate.com/cgi-bin/perlbrowse?patch=25257
(not having access to a VMS box, and being a bit in a hurry since I'll
be leaving soon for
Abe Timmerman wrote:
Hi all,
The build stops here:
Running Mkbootstrap for B::C ()
MCR BLDROOT:[00]miniperl.exe -I[---.lib] -I[---.lib]
-MExtUtils::Comman
d -e chmod 644 C.BS
MCR BLDROOT:[00]miniperl.exe -I[---.lib] -I[---.lib]
-MExtUtils::Comman
d -e cp C.bs [---.LIB.AUTO.B.C]C.BS
Here are some miscellaneous VMS specific things that need to be fixed
for VMS to work with the VMS C Run-Time Library (CRTL) UNIX filename
mode that do not require any other changes to Perl for implementation.
When the VMS CRTL is in UNIX filename mode, the VMS C library calls
return
I am looking for some feedback as I try to put the ODS-5, UNIX and POSIX
modes in to BLEAD-Perl on VMS.
The correctness and efficiency of the vmsify() and related routines that
convert possibly UNIX filenames to VMS format can be enhanced if the
caller of the routines can pass some additional
Paul Marquess wrote:
From: John E. Malmberg
much snipping
From what I have seen of the other tests, the INC setting when running
these tests is usually inherited from the parent, and I have seen the
tests use a test when deciding to use blib or not.
I did not know the correct fix, just what
Paul Marquess wrote:
From: John E. Malmberg [mailto:[EMAIL PROTECTED]
Paul Marquess wrote:
From: John E. Malmberg
much snipping
OK, I'll remove that code from my development copy.
This leaves the case where C::Zlib is built away from the core, which is
what the original code did
John E. Malmberg wrote:
Abe Timmerman wrote:
Hi all,
The build stops here:
Running Mkbootstrap for B::C ()
MCR BLDROOT:[00]miniperl.exe -I[---.lib] -I[---.lib]
-MExtUtils::Comman
d -e chmod 644 C.BS
MCR BLDROOT:[00]miniperl.exe -I[---.lib] -I[---.lib]
-MExtUtils::Comman
d -e cp
John E. Malmberg wrote:
John E. Malmberg wrote:
Abe Timmerman wrote:
Hi all,
The build stops here:
Running Mkbootstrap for B::C ()
MCR BLDROOT:[00]miniperl.exe -I[---.lib] -I[---.lib]
-MExtUtils::Comman
d -e chmod 644 C.BS
MCR BLDROOT:[00]miniperl.exe -I[---.lib] -I[---.lib
Sorry, my buggy rsync did not bring over the .patches file.
t/run/exitFAILED--unexpected output at
test 3
Fixes to the mapping of VMS (NATIVE) status codes to PERL (UNIX) in
progress. Changes needed to vms.c,perl.h,pp_sys.c and t/run/exit.t so far.
Abe Timmerman wrote:
Op een mooie zomerdag (Friday 05 August 2005 01:33),schreef John E. Malmberg:
John E. Malmberg wrote:
Abe Timmerman wrote:
d -e chmod 644 [---.LIB.AUTO.B.C]C.BS
%MMS-F-ABORT, For target SUBDIRS, CLI returned abort status: %X10EE8180.
%MMS-F-ABORT, For target DYNEXT
Second try:
Here are some miscellaneous VMS specific things that need to be fixed
for VMS to work with the VMS C Run-Time Library (CRTL) UNIX filename
mode that do not require any other changes to Perl for implementation.
When the VMS CRTL is in UNIX filename mode, the VMS C library calls
Michael G Schwern wrote:
On Fri, Aug 12, 2005 at 05:05:47PM -0400, John E. Malmberg wrote:
I think your patch is backwards.
It is. The corrected patch is attached.
To avoid these sort of mistakes in the future I'd suggest using RCS on the
files you edit rather than diffing copies.
I do
This allows lib/config/extensions.t to run with out errors on VMS.
Currently VMS does not appear to have any non-xs extensions being built
automatically.
-John
[EMAIL PROTECTED]
Personal Opinion Only
--- configure.com_24292 Sat Aug 13 10:16:55 2005
+++ configure.com Sat Aug 13 00:46:18
Tests 7 and 8 for this script are failing on VMS.
Test 7 is failing because normally on VMS, unless you specify otherwise,
you get exclusive access to the file, so the second open is failing.
The logical name DECC$FILE_SHARING defined as ENABLE will change VMS
behavior to that of UNIX which
Yitzchak Scott-Thoennes wrote:
John E. Malmberg wrote:
It seems that I need to fix configure.com to set the nonxs_ext
configuration item. For now the fix will be to just set it to an empty
string as it appears that there are no nonxs_ext modules that are being
built on VMS.
Not Errno
sebb wrote:
On 14/08/05, John E. Malmberg [EMAIL PROTECTED] wrote:
Tests 7 and 8 for this script are failing on VMS.
Test 7 is failing because normally on VMS, unless you specify otherwise,
you get exclusive access to the file, so the second open is failing.
The logical name DECC
Jim Cromie wrote:
John E. Malmberg wrote:
The patch that I submitted is needed to eliminate a data corruption
issue that should be affecting more than just VMS.
If I have diagnosed this wrong, please let me know.
just a wild conjecture from the peanut gallery. There are some pretty
subtle
Michael G Schwern wrote:
On Tue, Aug 16, 2005 at 12:39:00PM +0930, Jeremy Begg wrote:
Where exactly is the problem here? It looks like Install.PM is assuming the
case of the filenames returned by File::Find is going to match the package
names declared in those files, but is that improper
Michael G Schwern wrote:
On Sat, Aug 13, 2005 at 10:33:45PM -0400, John E. Malmberg wrote:
There does not seem to be a method of explicitly closing or flushing the
output stream being written to by Test::Builder.
Any ideas on how to resolve this?
I can change the test to write to a tied
This test script was not using the same names for the VMS specific files
descrip.mms and descrip.mms_old that the rest of Makemaker was doing.
-John
[EMAIL PROTECTED]
Personal Opinion Only
--- lib/ExtUtils/t/Constant.t_25305 Thu Aug 18 20:33:20 2005
+++ lib/ExtUtils/t/Constant.t Thu Aug
Two problems found so far.
1. The compiler can not find the header file when run.
This is because last /INCLUDE directive on the command line is the only
one used, and there was already an /INCLUDE in the configuration options.
The same is the case for /DEFINE and the other qualifiers.
A
Andy Lester wrote:
- rename $makefile_rename, $makefile
+ rename $makefile_rename, $makefile . $makefile_ext
or die Can't rename '$makefile_rename' to '$makefile': $!;
Shouldn't that be
or die Can't rename '$makefile_rename' to '$makefile$makefile_ext': $!
Something like that. I
Nicholas Clark wrote:
Sorry about the delay in replying. I've had a lot on, and wanted to find
the time to confirm my suspicions.
On Sat, Jul 30, 2005 at 09:50:40PM -0400, John E. Malmberg wrote:
What I have found is that in this case is that the allocation size for
the sv_u.svu_array member
Nicholas Clark wrote:
On Sat, Aug 20, 2005 at 01:08:07AM -0400, John E. Malmberg wrote:
Nicholas Clark wrote:
I can only reproduce this on one instance of one test, but on that test
it can be reproduced every time.
In your previous messages I couldn't spot whether you said which test
Nicholas Clark wrote:
On Sat, Aug 20, 2005 at 01:08:07AM -0400, John E. Malmberg wrote:
Nicholas Clark wrote:
I can only reproduce this on one instance of one test, but on that test
it can be reproduced every time.
As of [EMAIL PROTECTED], I can not reproduce the corruption anymore
Initial results on 25308 blead on OpenVMS/Alpha.
EAGLE search blead.log failed
t/op/arithFAILED--expected 145 tests,
saw 144
t/op/goto.FAILED at test 53
t/op/gv...FAILED at test 67
If VMS is configured to use IEEE float, test 145 was not run.
-John
[EMAIL PROTECTED]
Personal Opinion Only
--- t/op/arith.t_25309 Sat Aug 6 12:23:11 2005
+++ t/op/arith.tSat Aug 20 23:08:14 2005
@@ -289,18 +289,22 @@
try $T++, abs($t1000 -1000 * $t) = 2000;
}
-if ($^O eq 'vos')
Fix for correct names for the descrip.mms file used with MMS/MMK on VMS.
Per review of Andy Lester, also fixed the error message from failed renames.
Also preparation for use of other make programs on VMS with the
assumption that no there will be no port of MMK to other platforms even
though
Nicholas Clark wrote:
On Sat, Aug 20, 2005 at 05:25:02PM -0400, John E. Malmberg wrote:
Bah.
If you still have the build tree for the version that reliably shows it,
what happens if you apply just patch 25297 to it, and recompile:
No, it is gone.
I'm wondering if it was something about
On every blead perl I have seen, the following bug is present on VMS and
is causing the script t/op/magic.t to fail at test 7.
In the Perl debugger, before running any script if you issue the command
'x keys(%ENV), the entry for index 0, also shows up as index 1.
DB1 x keys(%ENV)
0
The test lib/math/bigint/t/mbi_rand needs a larger PERL_MBX_SIZE than
the default of 512 bytes.
A setting of 1024 seems to make the test pass.
This logical name needs to be set before running the test, so it either
needs to be put somewhere in [.vms]test.com or in the TEST perl script
that
Craig A. Berry wrote:
At 11:20 PM -0400 8/22/05, John E. Malmberg wrote:
snip
You're really better off just changing all the print statements of the form:
print foo, \n;
to
print foo . \n;
That way you'll have a single I/O that won't generate a record
boundary in the mailbox underlying
Craig A. Berry wrote:
At 10:35 PM -0400 8/22/05, John E. Malmberg wrote:
On every blead perl I have seen, the following bug is present on
VMS and is causing the script t/op/magic.t to fail at test 7.
In the Perl debugger, before running any script if you issue the
command 'x keys(%ENV
At 10:35 PM -0400 8/22/05, John E. Malmberg wrote:
On every blead Perl I have seen, the following bug is present on
VMS and is causing the script t/op/magic.t to fail at test 7.
In the Perl debugger, before running any script if you issue the
command 'x keys(%ENV), the entry for index 0
According to the code in mg.c / Perl_magic_clear_all_env() the last
three tests can not be done on VMS, EPOC, and SYMBIAN.
I do not know how to test for EPOC or SYMBIAN, but this patch will
handle the VMS case.
-John
[EMAIL PROTECTED]
Personal Opinion Only
--- t/op/magic.t_25334 Sat Aug 27
The dump of [EMAIL PROTECTED] on VMS produces the following output that
is different from the expected.
In particular, there is no trailing null on the value on the resulting
value, and it has the additional flags of READONLY and FAKE.
What I do not know is if this is an intended behavior on
This fixes test 21 on blead-perl to pass on VMS. The hash set by VMS
now has the READONLY and FAKE attributes, and two of the three VMS
resources that are represented by ENV hashes are not null terminated and
can contain binary values.
-John
[EMAIL PROTECTED]
Personal Opinion Only
---
John E. Malmberg wrote:
Initial results on 25308 blead on OpenVMS/Alpha.
EAGLE search blead.log failed
t/op/goto.FAILED at test 53
Appears to be known issue with VMS adding extra new lines to piped
output.
t/op/gv...FAILED
Test 20 of lib/File/Copy.t is failing on VMS because the copied file has
not inherited the creation date from the original file.
This is consistent with the way that the COPY command works from the DCL
command shell on VMS.
While I can change VMS to follow this behavior, I am concerned that
Craig A. Berry wrote:
At 7:51 PM -0400 8/31/05, John E. Malmberg wrote:
Test 20 of lib/File/Copy.t is failing on VMS because the copied
file has not inherited the creation date from the original file.
Unless I'm looking at the wrong test, it's not creation time, but
rather mtime, which
These are the patches needed for the tests FIRST_MAKEFILE.t and
PL_FILES.t to pass on VMS.
There are also two typo fixes in MM_Unix.pm and MM_VMS.pm that are
already in [EMAIL PROTECTED] but not in the 6.30_01 tarball.
In lib/ExtUtils/MM_Unix.pm, $^X is a complete specification on VMS, and
John E. Malmberg wrote:
Initial results on 25308 blead on OpenVMS/Alpha.
EAGLE search blead.log failed
t/op/goto.FAILED at test 53
Appears to be known issue with VMS adding extra new lines to piped
output.
t/op/gv...FAILED
This patch is needed for the lib/ExtUtils/ParseXS.t/basic.t test to pass
on VMS.
In lib/ExtUtils/CBuilder/Platform/VMS.pm, VMS needs to have a pre-link
file generated.
In lib/ExtUtils/CBuilder/Base.pm:
VMS can only have one /include qualifier on the CC command, and the last
one wins, so if
Ken Williams wrote:
Hi John,
After my last email I reworked the patch so that all the modifications
are in Platform/VMS.pm. Could you confirm that it still works for you
and I haven't broken it?
I will not be able to get to it for at least 10 hours, and it will
probably be a bit longer,
John E. Malmberg wrote:
Ken Williams wrote:
Hi John,
After my last email I reworked the patch so that all the
modifications are in Platform/VMS.pm. Could you confirm that it
still works for you and I haven't broken it?
First I discovered that I had a bug in my patch to base.pm
This is the status of Blead 25366 (Sept 9, 2005 download) on VMS.
Only the ZLIB test is failing for unknown reasons. Paul, if your
changes got applied to blead, then they are still not working.
Otherwise, I have pulled down the latest ZLIB from CPAN and will try
that one out.
This is with
::_do_link($type, %args, objects = $objects);
}
sub arg_nolink { return; }
===
On Sep 7, 2005, at 6:59 PM, John E. Malmberg wrote:
This patch is needed for the lib/ExtUtils/ParseXS.t/basic.t test to
pass on VMS.
In lib/ExtUtils
Paul Marquess wrote:
From: Abe Timmerman [mailto:[EMAIL PROTECTED]
Op een mooie zomerdag (Sunday 11 September 2005 19:14),schreef Paul
Marquess:
This is with 5.8.6 on Alpha:
t/14gzopen..
# Failed test (t/14gzopen.t at line 421)
# Failed test (t/14gzopen.t at line 424)
#
Paul Marquess wrote:
Thanks John. I've CCed Tom Hughes for the IO:Zlib results.
I did not realize at the time that I did the tests that they were not
the same ZLIB module.
I see that the majority of the failures match those that Abe Timmerman
reported earlier today. Apart from running with
Paul Marquess wrote:
From: John E. Malmberg [mailto:[EMAIL PROTECTED]
Paul Marquess wrote:
Sorry if I'm showing my ignorance of VMS, but does this mean that when you
run Perl on VMS you will/do have the choice of running the C library under
UNIX emulation mode or in VMS native mode
I finally got a download of 2.00_03, and I have locally patched vms.c to
fix the fstat()/Perl_cando() issue.
So here are the results.
I probably will not have time to investigate the failure tonight as I
need to submit the patch to vms.c.
ext/Compress/Zlib/t/01version.t 2 of 2
Ken Williams wrote:
Thanks, John. I've applied your patch (in a slightly modified form) and
released a new beta, 0.13_01. It would be great if you (and/or a couple
other people on the vmsperl list) could try it out, and then I can
release 0.14 when it checks out.
It is not yet showing up
The VMS specific Perl_cando() on open file handles was returning the
results for a previous file that a stat()/lstat() that was done instead
of for the open file.
This was causing failures in the Compress-Zlib tests on my system.
-John
[EMAIL PROTECTED]
Personal Opinion Only
---
Ken Williams wrote:
On Sep 12, 2005, at 11:12 PM, John E. Malmberg wrote:
It looks like I am finally close to starting to get the file spec
handling in Perl up to speed with current VMS versions.
In File::Spec::VMS, would it be appropriate to use a syntax like
below to switch VMS
Tim Maher wrote:
On Tue, Sep 13, 2005 at 09:53:15AM -0400, John E. Malmberg wrote:
Ken Williams wrote:
Extended characters in pathnames: The traditional VMS mode ...
[0..9],[A..Z],[-$_]
I'm admittedly a few decades past the peak of my expertise in VMS,
but shouldn't the ; preceding
Paul Marquess wrote:
From: John E. Malmberg [mailto:[EMAIL PROTECTED]
I finally got a download of 2.00_03, and I have locally patched vms.c to
fix the fstat()/Perl_cando() issue.
So here are the results.
ext/Compress/Zlib/t/16oneshot.t fails at 1460 and dies.
not ok 1460 - Compressed ok
John E. Malmberg wrote:
Paul Marquess wrote:
Editing 16oneshot.t to remove the './' from the $tmpdir and re-running
the script makes it pass all 2544 tests.
It appears something is wrong with glob() on VMS.
glob(./tmpdir/a*.tmp) is returning t/tmpdir/a1.tmp when the current
working
Nicholas Clark wrote:
With respect to the odd corruption seen previously on VMS, but now no longer
visible, might this patch have had something to do with it? I believe that
the change I made was correct. If so, then because it removed a large over-
allocation, it will show up any other code
John E. Malmberg wrote:
These are the patches needed for the tests FIRST_MAKEFILE.t and
PL_FILES.t to pass on VMS.
I have seen no response to the patch in the message I am replying to, is
there a problem with it?
There are also two typo fixes in MM_Unix.pm and MM_VMS.pm that are
already
John E. Malmberg wrote:
Michael G Schwern wrote:
On Sat, Aug 13, 2005 at 10:33:45PM -0400, John E. Malmberg wrote:
I can change the test to write to a tied filehandle or I can make sure
the
new Test::Builder object which outputs to some_file is destroyed before I
read from some_file
Craig A. Berry wrote:
At 7:36 PM -0400 9/16/05, John E. Malmberg wrote:
John E. Malmberg wrote:
It appears something is wrong with glob() on VMS.
glob(./tmpdir/a*.tmp) is returning t/tmpdir/a1.tmp
when the current working directory is t.
glob(tmpdir/a*.tmp) is returning tmpdir/a1.tmp
Paul Marquess wrote:
From: John E. Malmberg [mailto:[EMAIL PROTECTED]
Did you have to make any changes to globmapper.t? It passes ./ to glob and
it uses [] to mean a character class, not a VMS directory.
No, but I have made a note on my personal TO DO list about that.
What is needed is some
101 - 200 of 663 matches
Mail list logo