Craig A. Berry wrote:
The attached provides the special handling needed for C compiler defines
in ExtUtils::CBuilder. This is against blead but I'm hoping the right
number after -p supplied to patch will apply cleanly to the CPAN version
(which is separately maintained, right?).
I just applied
Paul Marquess wrote:
From: John E. Malmberg [mailto:[EMAIL PROTECTED]
Paul Marquess wrote:
I was afraid of that. I guess I need to do a massive delete of that
tree and then refresh it and see if that helps.
Yep, sounds like a good plan.
Ok,
I deleted all of the Zlib directory trees
Craig A. Berry wrote:
With the attached changes to DistGen, we can actually run all the tests,
and with the changes to Module::Build::Base, we get one step closer to
doing some basic things like running Perl one-liners. After this and the
CBuilder patch just posted, I get the following
John E. Malmberg wrote:
John E. Malmberg wrote:
Craig A. Berry wrote:
At 12:32 AM -0500 3/5/06, John E. Malmberg wrote:
Here is what vms.c needs to get it to build with threads.
Thanks, applied as #27385.
I just did a full build with that vms.c patch previously submitted and blead
The test scripts:
ext/Compress/Zlib/t/05examples.t and
ext/Compress/IO/Zlib/t/010examples.t are both failing on OpenVMS
apparently because they can not find the file:
auto/Compress/Raw/Zlib/autosplit.ix.
The only place I can find a like file is in
auto/Compress/ZLIB/autosplit.ix.
The test script ext/threads/shared.t is failing on OpenVMS Alpha with a
stack overflow when it is attempting to do a Perl_clone().
Unless a stack is explicitly specified when the thread is created, on
OpenVMS only 8K bytes is allocated.
It looks like this is no longer enough to clone perl in
This is from a quick look at the failures of MODULE BUILD on OpenVMS.
lib/Module/Build/t/basic...FAILED--expected 55 tests, saw 13
Can't cd to PROJECT_ROOT:[PERL-BLEAD.t._tmp.Simple]: no such file or
directory
Seems to be deleting directories and then trying to set default to the
John E. Malmberg wrote:
Craig A. Berry wrote:
At 12:32 AM -0500 3/5/06, John E. Malmberg wrote:
Here is what vms.c needs to get it to build with threads.
Thanks, applied as #27385.
And here is what it takes to get it to pass the tests except for test 4
of t/op/threads.t which
Nicholas Clark wrote:
On Thu, Mar 09, 2006 at 10:01:52AM +, Dave Mitchell wrote:
On Tue, Mar 07, 2006 at 10:50:45PM -0500, John E. Malmberg wrote:
In util.c the routines Perl_safesysmalloc and friends are updating a
linked list.
There does not seem to be any protection from a different
Peter Prymmer wrote:
Peter Prymmer [EMAIL PROTECTED] wrote on 03/07/2006 11:42:38 PM:
Sorry but I have made no progress on this problem. I am concerned.
I now suspect that there is a VMS specific bug in File::Path::mkpath.
If I add a diagnostic print statement to that module like so:
$
Craig A. Berry wrote:
At 12:32 AM -0500 3/5/06, John E. Malmberg wrote:
Here is what vms.c needs to get it to build with threads.
Thanks, applied as #27385.
And here is what it takes to get it to pass the tests except for test 4
of t/op/threads.t which consistently hangs for me, and did
As I am troubleshooting an issue with threads and memory allocation on
OpenVMS, I have noticed a couple of things.
In util.c the routines Perl_safesysmalloc and friends are updating a
linked list.
There does not seem to be any protection from a different thread also
updating the same linked
Peter Prymmer wrote:
Craig A. Berry [EMAIL PROTECTED] wrote on 03/05/2006 10:46:17 PM:
At 8:30 PM -0500 3/5/06, Peter Prymmer wrote:
and changed the output of the sig_name_init back to the write/symbol
so as to avoid possible very long symbol output problems that are
germane to DCL
Except
John E. Malmberg wrote:
John E. Malmberg wrote:
Craig A. Berry wrote:
At 6:29 PM -0500 3/4/06, John E. Malmberg wrote:
Thanks, applied as #27376.
It is not going to be enough. I found another case in vms.c that
needs fixing, and then miniperl died with an access violation when I
John E. Malmberg wrote:
John E. Malmberg wrote:
John E. Malmberg wrote:
Craig A. Berry wrote:
At 6:29 PM -0500 3/4/06, John E. Malmberg wrote:
Thanks, applied as #27376.
It is not going to be enough. I found another case in vms.c that
needs fixing, and then miniperl died
Craig A. Berry wrote:
At 8:42 PM +0100 3/4/06, Abe Timmerman wrote:
fp = Perl_vms_start_glob(tmpglob, io);
.^
%CC-W-PTRMISMATCH, In this statement, the referenced type of the pointer value
tmpglob is struct sv, which is not compatible with struct interpreter.
at
Craig A. Berry wrote:
At 6:29 PM -0500 3/4/06, John E. Malmberg wrote:
Thanks, applied as #27376.
It is not going to be enough. I found another case in vms.c that needs
fixing, and then miniperl died with an access violation when I restarted
the MMK build.
So I just did a MMK realclean
John E. Malmberg wrote:
Craig A. Berry wrote:
At 6:29 PM -0500 3/4/06, John E. Malmberg wrote:
Thanks, applied as #27376.
It is not going to be enough. I found another case in vms.c that needs
fixing, and then miniperl died with an access violation when I restarted
the MMK build
[EMAIL PROTECTED] wrote:
Is there any way to turn off the period to underscore translation in the VMSIFY
routine?
I am using the HP kit of Perl 5.8.6 and as the following example shows, a
period in a directory name is being converted to an underscore.
Which kit? The special one for the
Abe Timmerman wrote:
Op een mooie winterdag (Wednesday 15 February 2006 05:33),schreef Craig A.
Berry:
Thanks, applied as #27187.
Test-Drive (td180/ODS-5) isn't happy with it though:
CC/DECC/NOANSI_ALIAS /Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj/
In vms/vms.c:
Fix code for translating Unicode and escaped hex filenames from VMS to
UNIX to compile on the newer compiler with optimization on.
This bug was introduced with patch 27187.
Change code to do the rmdir and kill_file to be able to use long pathnames.
In mp_do_tounixspec, use
Previous filetest.t failure turned out to be a stale foo/ directory left
over from apparently from other troubleshooting. I will need to do a
complete test run again to be totally sure that one of the tests is not
leaving something behind.
EAGLE search build.log failed
t/comp/opsubs...FAILED at test 22
t/op/filetest...FAILED at test 10
ext/B/t/concise-xs..FAILED at test 15
Adam Kennedy wrote:
Hi guys
I've just (hand) merged the previously reported patch to add VMS support
to Module::Install, and I've got a few questions.
Most of the items were ok, but I have a question regarding
.author-_author.
Lets assume for the moment I'm not changing the default
Craig A. Berry wrote:
At 10:12 AM -0500 2/20/06, John E. Malmberg wrote:
If Scalar::Util is dynamically loaded, I will have a hard time
setting a breakpoint in it to debug it at C level to see what is
going on.
You might be able to set a breakpoint for my_find_image_symbol in
dl_vms.c
Nicholas Clark wrote:
On Sun, Feb 19, 2006 at 07:49:06PM -0500, John E. Malmberg wrote:
Nicholas Clark wrote:
Change 27228 by [EMAIL PROTECTED] on 2006/02/19 18:57:35
To make arithmetic on tainted dualvars work properly requires that
sv_2nv uses SvIVX in preference to SvPVX
Nicholas Clark wrote:
On Mon, Feb 20, 2006 at 10:12:33AM -0500, John E. Malmberg wrote:
Run a second time with tainting, and fails.
EAGLE mcr [-]ndbgperl -T -I[-.lib] [-.t.op]taint.t2
SV = PVMG(0x2c6d00) at 0x2e9740
REFCNT = 1
FLAGS = (PADMY,GMG,SMG,pPOK)
IV = 0
NV = 0
PV = 0x339ce0
Nicholas Clark wrote:
Change 27228 by [EMAIL PROTECTED] on 2006/02/19 18:57:35
To make arithmetic on tainted dualvars work properly requires that
sv_2nv uses SvIVX in preference to SvPVX, if SVp_IOK is true.
Is this test supposed to work on VMS?
not ok 246 - Arithmetic on
In t/io/fs.t:
The tmp directory may be created with out having delete protection, so
the spawned DCL command fails to delete it. This can cause extra output
in the test.
In doio.c:
Remove the VMS specific code and replace with a subroutine call to it's
new location in VMS.C.
In vms.c:
Craig A. Berry wrote:
On Saturday 04 February 2006 22:04, John E. Malmberg wrote:
This patch allows the Perl user to set a logical name
PERL_EXCEPTION_DEBUG that causes Perl to invoke the VMS debugger before
having the default fatal exception handler in Perl cause a fatal exit.
Thanks
in vms/vmsish.h:
Change the field vms_wantversions to be a flag field to also indicate if
the input file specification was UNIX format, so the read file names
should be also in UNIX format.
In vms/vms.c:
Add static routine copy_expand_vms_filename_escape() to copy and
optionally expand '^'
For OpenVMS long filename support, I will need to set the macro
MAXPATHLEN to the proper size of either 256 or 4096 depending on the
platform and version.
In order to do that through other macros, rmsdef.h would need to be
included in vmsish.h instead of in vms.h and other modules.
Also to
Chris Sharman wrote:
Alpha VMS 7.3-1, DEC C 6.5-001, MMK 3.9-6, MMS 3.4-3.
Just a default build.
I can't upgrade VMS (I need appletalk to work), and the prebuilt
binaries are for vms 7.3-2 up.
I want a copy of perl to massage VMS/RMS data files into a format
suitable for load into mysql.
Peter Prymmer wrote:
When I run:
@configure -des
mmk
I get to a point where the action commands:
%COPY-S-COPIED, USER:[PPRYMMER.PERL.PERL.VMS]SOCKADAPT.H;1 copied to
USER:[PPRYMMER.PERL.PERL]SOCKADAPT.H;1078 (10 blocks)
CC/DECC/NOANSI_ALIAS
[EMAIL PROTECTED] wrote:
I'm only commenting on the name of the variable you have chosen here, not the
patch itself. I wonder, if it is such a VMS specific operation, whether the
name of the OS would not be better to be included somehow, something like:
PERL_EXCEPTION_VMS_DEBUG
Just a
John E. Malmberg wrote:
Peter Prymmer wrote:
When I run:
@configure -des
mmk
I get to a point where the action commands:
%COPY-S-COPIED, USER:[PPRYMMER.PERL.PERL.VMS]SOCKADAPT.H;1 copied to
USER:[PPRYMMER.PERL.PERL]SOCKADAPT.H;1078 (10 blocks)
CC/DECC/NOANSI_ALIAS
/Include
This patch allows the Perl user to set a logical name
PERL_EXCEPTION_DEBUG that causes Perl to invoke the VMS debugger before
having the default fatal exception handler in Perl cause a fatal exit.
The two files when renamed to being .com and .ini allow a test to be
done with that feature. I
Craig A. Berry wrote:
At 9:59 PM -0500 2/2/06, John E. Malmberg wrote:
I am currently building a patch that allows Perl to enter the
OpenVMS debugger when an exception occurs, if the the logical name
PERL_EXCEPTION_DEBUG is present.
What I could use some help in creating a perl script
I am currently building a patch that allows Perl to enter the OpenVMS
debugger when an exception occurs, if the the logical name
PERL_EXCEPTION_DEBUG is present.
What I could use some help in creating a perl script that would cause an
exception to be signaled so that I can verify that it
Mark Berryman wrote:
It is available on V7.3-2. I don't have anything older than that to
check. It does require 64-bit file support but that has been around
for quite a while.
You are right, it showed up in V7.3-2, but since I am not using 7.3-2 on
any of my build/test systems, I was not
All tests successful.
u=97.59 s=0.00 cu=0.00 cs=0.00 scripts=1085 tests=157304
1-FEB-2006 00:16:32.03 User: MALMBERGProcess ID: 658D
Node: EAGLE Process name: MALMBERG_204
Accounting information:
Buffered I/O count:751979 Peak working set
Mark Berryman wrote:
I am curious. Why would you not want to simply define _USE_STD_STAT?
Perl currently is coded to expect only the behavior of the traditional
but non standard compliant stat structure and related calls and then
give an illusion that the stat structure is compliant.
In vmsish.h:
* Fix a typo for vms specific st_fab_mrs macro that was not noticed
because currently nothing uses it.
* Create macros VMS_INO_T_COMPARE and VMS_INO_T_COPY to hide difference
from traditional VMS specific ino_t array type and standard 64 bit ino_t
type.
In vms.c:
1. Set
Craig A. Berry wrote:
At 9:47 PM -0500 1/26/06, John E. Malmberg wrote:
I am also thinking of changing the code that looks up the logical
name DECC_BUG_DEVNULL to default to 1 unless the logical name is
present to turn it off.
So that means doing the old behavior by default?
Yes, until
Craig A. Berry wrote:
At 5:31 PM -0500 1/26/06, John E. Malmberg wrote:
Martin Borgman of the Open Office on VMS team sent me this
information about a problem he had running Perl.
Because he also needs to run Java, his session has the logical name
DECC$ARGV_PARSE_STYLE defined as ENABLE
Yitzchak Scott-Thoennes wrote:
Just a few comments to start with. Have you had a chance to look
at any of this?
On Sat, Jan 21, 2006 at 07:16:08PM -0600, Craig A. Berry wrote:
I tested it against [EMAIL PROTECTED] Complete harness output is below.
It may not be as bad as it looks in that it
Martin Borgman of the Open Office on VMS team sent me this information
about a problem he had running Perl.
Because he also needs to run Java, his session has the logical name
DECC$ARGV_PARSE_STYLE defined as ENABLE.
When this is set, the unquoted parameters are passed in exact case to
perl,
Craig A. Berry wrote:
So now we're getting to the problem that was Yitzchak's first theory,
namely that it's a case problem, more specifically, the case-leveled
names returned from File::Find do not match the case-preserved names
in the hash, so we delete the files because they are not
John E. Malmberg wrote:
I just got a reproduced crash with an instrumented vms.c.
The access violation is occurring inside the stat() call in the CRTL.
According to the debugger, nothing is wrong with the arguments to
function, and I am referring this over to HP.
We can use the logical
Hello Craig,
It appears that there is something wrong with nntp.perl.org so until
this evening I have limited access to e-mails.
I've attached a patch which I'm still testing that addresses this and
a couple of other stat-related nits. After applying it, I don't get
the accvio when running
Craig A. Berry wrote:
I've attached a patch which I'm still testing that addresses this and
a couple of other stat-related nits. After applying it, I don't get
the accvio when running the stat.t test any more. I'm not entirely
convinced we've found the bug, as copying 8 bytes when we only
I just got a reproduced crash with an instrumented vms.c.
Here is the code fragment:
my $Null = '_NLA0:';
print STDERR # stat.t1 step 7 - Null = $Null\n\n;
#SKIP: {
#skip No null device to test with, 1 unless -e $Null;
my $isnull1 = -e '/dev/null';
print STDERR # stat.t1 step 8.1\n\n;
my
Craig A. Berry wrote:
At 11:03 PM -0500 1/22/06, John E. Malmberg wrote:
John E. Malmberg wrote:
Craig A. Berry wrote:
At 8:15 PM -0500 1/21/06, John E. Malmberg wrote:
$ perl harness [.op]stat.t
[.op]statdubious
Test returned status 12 (wstat 1024, 0x400)
(VMS
Craig Berry wrote:
On Monday, January 23, 2006, at 09:18AM, John E. Malmberg [EMAIL PROTECTED] wrote:
The puzzling thing is that the statement -e $Null will only cause an
access violation for $Null = '_NLA0:'. Replacing it with -e '_NLA0:'
eliminates the access violation.
Now the one
Craig A. Berry wrote:
At 8:15 PM -0500 1/21/06, John E. Malmberg wrote:
$ perl harness [.op]stat.t
[.op]statdubious
Test returned status 12 (wstat 1024, 0x400)
(VMS status is 12)
FAILED--1 test script could be run, alas--no output ever seen
%SYSTEM-F-ACCVIO, access
John E. Malmberg wrote:
Craig A. Berry wrote:
At 8:15 PM -0500 1/21/06, John E. Malmberg wrote:
$ perl harness [.op]stat.t
[.op]statdubious
Test returned status 12 (wstat 1024, 0x400)
(VMS status is 12)
FAILED--1 test script could be run, alas--no output ever seen
All tests successful.
u=141.39 s=0.00 cu=0.00 cs=0.00 scripts=1084 tests=157283
lib/ExtUtils/t/ManifestFAILED at test 26
Failed 4 test scripts out of 1083, 99.63% okay.
Retest after bringing blead up to 26913:
EXT/DEVEL/PPPORT/T/PPPHTESTok
EXT/DIGEST/SHA/T/6-DUMP-LOADok
EXT/LIST/UTIL/T/P_TAINTEDok
Means only 1 test failing for blead on
Yitzchak Scott-Thoennes wrote:
On Thu, Jan 19, 2006 at 06:34:30AM -0500, John E. Malmberg wrote:
lib/ExtUtils/t/ManifestFAILED at test 26
Would you be able to try out the patch adding Module::Build?
It's at http://zipcon.net/~sthoenna/mbaddfull123.patch
To prevent
Yitzchak Scott-Thoennes wrote:
On Thu, Jan 19, 2006 at 08:48:51AM -0500, John E. Malmberg wrote:
Yitzchak Scott-Thoennes wrote:
On Thu, Jan 19, 2006 at 06:34:30AM -0500, John E. Malmberg wrote:
lib/ExtUtils/t/ManifestFAILED at test 26
Would you be able to try
Yitzchak Scott-Thoennes wrote:
On Thu, Jan 19, 2006 at 04:19:04PM -0500, John E. Malmberg wrote:
Yitzchak Scott-Thoennes wrote:
Would you be able to try out the patch adding Module::Build?
Specifically I was wondering if it would fix the result of the
lib/Extutils/t/Manifest.t test
EAGLE search blead.log failed
ext/Devel/PPPort/t/ppphtestFAILED at test 2
ext/Digest/SHA/t/2-nist-sha-oo.FAILED--expected 3 tests, saw 2
ext/Digest/SHA/t/6-dump-load...FAILED--expected 4 tests, saw 0
ext/List/Util/t/p_tainted..FAILED--no leader found
Craig A. Berry wrote:
At 7:46 AM -0500 1/18/06, John E. Malmberg wrote:
ext/Digest/SHA/t/2-nist-sha-oo - not investigated yet.
Now:
EXT/DIGEST/SHA/T/2-NIST-SHA-OOok
ext/Digest/SHA/t/6-dump-load - bug found.
Merging VMS path with UNIX path with string concatenation.
#26899 may fix
Craig A. Berry wrote:
Actually, we explicitly turn it off in configure.com:
I only looked in the descrip_mms.template so I missed that.
-John
[EMAIL PROTECTED]
Personal Opinion Only
Craig A. Berry wrote:
At 10:23 PM -0500 1/6/06, John E. Malmberg wrote:
[-.lib.ExtUtils.t]Manifest.t44 1024492 4.08% 26 29
[-.lib.ExtUtils.t]PL_FILES.t44 1024 95 55.56% 3-7
I think that these are failing because of the issue addressed by
the patch
Steve Peters wrote:
Change 26632 by [EMAIL PROTECTED] on 2006/01/04 03:43:20
Added snprintf() and vsnprintf() to configure.com as 'undef'.
TODO, these routines are present on OpenVMS 7.3-2 and later.
http://h71000.www7.hp.com/doc/82FINAL/5763/5763pro_072.html
-John
[EMAIL PROTECTED]
This buffer overrun bug in vms.c/mp_do_fileify_dirspec has been there
for a while and was made more visible by the recent changes to allow
support of longer file names.
This patch should also be applied to the maint and upcoming 5.8 streams.
-John
[EMAIL PROTECTED]
Personal Opinion Only
---
I needed to add this const qualifier for utf8.c to compile.
-John
[EMAIL PROTECTED]
Personal Opinion Only
--- /rsync_root/perl/utf8.c Sun Jan 1 05:45:21 2006
+++ ./utf8.cSun Jan 1 21:41:43 2006
@@ -2236,7 +2236,7 @@
register const U8 *p1 = (const U8*)s1;
register const U8
I am testing a fix for this problem, and I am seeing a hang on the test
[.t.op]threads.t
Is this a known problem?
1..4
ok 1 - fresh_perl - delete() under threads
ok 2 - fresh_perl - weaken ref under threads
ok 3 - fresh_perl - weaken ref \#2 under threads
# parent 471639: continue
# parent
John E. Malmberg wrote:
Craig A. Berry wrote:
At 11:21 PM -0500 12/14/05, John E. Malmberg wrote:
The bug seems to be in *mp_do_fileify_dirspec.
while (*cp1 != ':') *(cp2++) = *(cp1++);
With this value of esa, the while statement just runs away, and
will eventually cause *cp2
Craig A. Berry wrote:
At 11:21 PM -0500 12/14/05, John E. Malmberg wrote:
The bug seems to be in *mp_do_fileify_dirspec.
while (*cp1 != ':') *(cp2++) = *(cp1++);
With this value of esa, the while statement just runs away, and
will eventually cause *cp2 to write over something unless
The bug seems to be in *mp_do_fileify_dirspec.
else { /* This is a top-level dir. Add the MFD to the path. */
if (buf) retspec = buf;
else if (ts) Newx(retspec,retlen+16,char);
else retspec = __fileify_retbuf;
cp1 = esa;
cp2 = retspec;
Craig A. Berry wrote:
Since applying this patch, Perl builds up to the point where it tries
to run the Makefile.PL for the first extension, at which point it
rapidly consumes all available stack space (after apparently writing
a complete descrip.mms). This is with a thread-enabled build.
Craig A. Berry wrote:
At 4:46 PM -0500 12/13/05, John E. Malmberg wrote:
Obviously we are so far not having the desired effect of reducing
stack space usage.
Obviously I have an error somewhere.
I do see one example of allocating a long filename on the stack:
$ SEARCH/EXACT vms.c tmp
embed.h is ending up with a bad definition of unlnk() when
UNLINK_ALL_VERSIONS is defined which is causing a compile error on VMS
when a threaded perl is being built.
It is not happening when non-threaded perls are being built.
-John
[EMAIL PROTECTED]
Personal Opinion Only
Craig A. Berry wrote:
$ @configure -Dusedevel -Dusevmsdebug -Duseithreads -des
Ok, I will try again.
I just completed a build with:
$ @configure -Duselargefiles -Dcf_email=SYSTEM -Dusevmsdebug
-Dusethreads -de
No problems with the build once I removed the -Dunlink_all_versions
-John
John E. Malmberg wrote:
I just completed a build with:
$ @configure -Duselargefiles -Dcf_email=SYSTEM -Dusevmsdebug
-Dusethreads -de
No problems with the build once I removed the -Dunlink_all_versions
Correction, doing the MMK REALCLEAN is resulting in miniperl generating
all sorts
Ken Williams wrote:
On Dec 6, 2005, at 11:46 AM, John E. Malmberg wrote:
Ken Williams wrote:
I was thinking we could add those as TODO tests, but I was unaware of
the problems with VAX legacy stuff.
There are some bugs that are in the legacy stuff that I am concerned if
I change
Is there any real reason that commands are being truncated if they have
an embedded new line?
Removing these lines makes test t/op/gv.t work on OpenVMS and improves
some other tests that are still failing for other reasons.
The way that parameters are passed to sub-processes on OpenVMS will
Ken Williams wrote:
Hi John,
Thanks for the patch, I've applied it. Could I trouble you to also add
a few tests to Spec.t to exercise these dead bugs?
Someone already did with a recent change to Spec.t, which made them show
up as failed at the same time I made a significant change to
In abs2rel() fix handling of directory trees so that the test $file =
File::Spec::VMS-abs2rel('[t1.t2.t3]file', '[t1.t2.t3]') returns 'file'
instead of an empty string.
In canonpath(), fix case where '[]' was totally optimized away instead
of just returning '[]'.
$file =
Cwd.pm will need an update for OpenVMS past version 8.2, for supporting
symbolic links and the UNIX emulation modes.
Using the realpath routine in Cwd.pm has a very significant performance
penalty as compared to using the realpath() routine that will be
provided by OpenVMS.
OpenVMS can
Carl Friedberg wrote:
Hi,
This is probably a FAQ, but I am trying to
resurrect the VMS SMG module.
Please look at the Readline support in Perl and the Perl debugger after
you get it resurrected.
If you can get Perl to use SMG for the readline support, it looks like a
trivial change to
Rafael Garcia-Suarez wrote:
On 11/29/05, John E. Malmberg [EMAIL PROTECTED] wrote:
I can not find where the file bar.tar is being created in this test.
Actually it's created by 00_setup.t. As tests are supposed to be
executed in asciibetical order, this should be fine. Is 00_setup.t
failing
I can not find where the file bar.tar is being created in this test.
The test is failing on VMS because it does not exist at the read phase.
ok 14 - Object created - read
ok 15 - The object isa Archive::Tar
# type = [.src.short]bar.tar
# state = uncompressed
Could not create filehandle for
The file ext/List/Util/t/p_tainted.t is assuming a UNIX format pathname
is returned by __FILE__.
This is a quick fix for VMS.
A proper fix needs use the routines to either generate a relative
pathname or concatenate paths.
Also I need to find out is where __FILE__ is being set because I
Rafael Garcia-Suarez wrote:
On 11/22/05, John E. Malmberg [EMAIL PROTECTED] wrote:
The file ext/List/Util/t/p_tainted.t is assuming a UNIX format pathname
is returned by __FILE__.
__FILE__ is initially set from PL_origfilename in perl.c. It's saved
as CopFILE in each cop (control op
t/op/array.t is failing on OpenVMS because it is calling reset 'b',
and perl can not reset %ENV hash values on VMS.
-John
[EMAIL PROTECTED]
Personal Opinion Only
--- /rsync_root/perl/t/op/array.t Wed Oct 19 17:18:03 2005
+++ t/op/array.tMon Nov 21 20:45:47 2005
@@ -61,7 +61,7 @@
t/op/pat.t is failing on OpenVMS because it is calling reset 'X', and
perl can not reset %ENV hash values on VMS.
That reset 'X' or other letters will generate a warning on OpenVMS would
seem to make this routine not useful on it.
-John
[EMAIL PROTECTED]
Personal Opinion Only
---
Peter Prymmer wrote:
This bug:
$ perl -e print defined(VMS::Filespec::vmspath('perlshr'))
$ perl -e print defined(VMS::Filespec::vmspath('perlshr_not_logical'))
1
Is causing trouble for sub init_main in ExtUtils::MakeMaker::MM_Unix.pm
which calls catfdir() to turn a NAME into a FULLEXT macro.
A rule needs to be added so that $(CORECFLAGS) is used for compiling
mathoms.c. Otherwise some needed macros are not defined.
Todo:
1. Should building mathoms.c be a configure option on VMS?
Or just dropped.
2. The definition of do_exec() macro needs to be determined.
Currently there
Abe Timmerman wrote:
This patch seems a logical follow up for 25969 on VMS (cando stuff)
Also needed is the attached vmsish.h patch.
-John
[EMAIL PROTECTED]
Personal Opinion Only
diff -ruN perl-blead/vms/vms.c perl-current/vms/vms.c
--- perl-blead/vms/vms.cWed Oct 26 15:54:10 2005
Abe Timmerman wrote:
Hi,
I get this warning on VMS:
# define do_exec(cmd) do_exec3(cmd,0,0)
..^
%CC-W-MACROREDEF, The redefinition of the macro do_exec conflicts with a
current definition because the number of parameters is different. The
redefinition is
The File::Basename::dirname('foo') is returning the current working
directory instead of File::Spec-cur_dir as would be the behavior on
other platforms.
Is this something that can be changed with out breaking other things?
The current behavior silently breaks a UNIX based perl script that is
In vms.c:
For platforms/versions that support it, a new do_mp_rmsexpand() that can
support longer filenames.
Fix memory leaks in old do_mp_rmsexpand() when it gets an apparent UNIX
format path that it can not translate.
Replace memcpy() with memmove() if there is a possibility of an
BG - Ben Armstrong wrote:
I'm interested in the work John and others are doing on VMSish issues,
particularly the recent work on pipes, because I will likely need this
for the VMS port of Ruby I seem to have inherited when the former
maintainer dropped off the scene. Is any portion of this
In vms/perlvms.pod :
Document traditional VMS behavior of Cdie, and also document the
latent POSIX_EXIT behavior changes for Cdie and C$?.
In perl.c:
Fixes to generate both the traditional and latent POSIX_EXIT VMS
behaviors and provide comments about why they are so different from
Rafael Garcia-Suarez wrote:
John E. Malmberg wrote:
In vms/perlvms.pod :
Document traditional VMS behavior of Cdie, and also document the
latent POSIX_EXIT behavior changes for Cdie and C$?.
Thanks, applied as #25849 (with change #25839 backed out).
Your doc changes are a bit difficult
John E. Malmberg wrote:
Which the code that is failing is:
$exit_arg = 42;
$exit = run(END { \$? = $exit_arg });
$exit_arg = (44 7) if $^O eq 'VMS';
is( $exit 8, $exit_arg, 'Changing $? in END block' );
The severity for 42 is ERROR and apparently on VMS, changing the
status
I think I have found it.
The old default behavior is in effect when the VMS specific macro
MY_POSIX_EXIT evaluates to 0.
When setting $? in mg.c, as a side effect, if $? is not 0, then default
VMS behavior is to set STATUS_NATIVE to SS$_ABORT.
When Perl_my_exit() is called with other than
301 - 400 of 663 matches
Mail list logo
