On 7/22/2014 7:13 AM, Craig A. Berry wrote:
On Jul 21, 2014, at 7:41 PM, John E. Malmberg wb8...@qsl.net wrote:
On 7/21/2014 7:06 PM, Craig A. Berry wrote:
DECC$FILENAME_UNIX_REPORT has nothing at all to do with exit statuses.
Well, I wouldn't think it did, but for some reason the two
On 7/21/2014 7:06 PM, Craig A. Berry wrote:
On Jul 20, 2014, at 3:50 PM, John E. Malmberg wb8...@qsl.net wrote:
If you define PERL_VMS_POSIX_EXIT or DECC$FILENAME_UNIX_REPORT, it
is supposed to behave the way that you would normally expect.
That depends on what you normally expect
On 7/20/2014 2:52 PM, John Dite wrote:
1.) A failed lookup in %ENV sets errno / vaxc$errno in our getenv
implementation (specifically Perl_vmstrenv in [.vms]vms.c). This is
normal and as it should be.
2.) die() (specifically Perl_my_failure_exit in perl.c) retrieves the
most recent value of
On 3/7/2014 8:18 AM, Craig A. Berry wrote:
On Feb 26, 2014, at 11:35 PM, John E. Malmberg
malmb...@encompasserve.org wrote:
On 2/25/2014 7:02 PM, Craig A. Berry wrote:
On Feb 24, 2014, at 11:33 PM, John E. Malmberg
malmb...@encompasserve.org wrote:
I can not seem to do a rmdir
On 2/25/2014 7:02 PM, Craig A. Berry wrote:
On Feb 24, 2014, at 11:33 PM, John E. Malmberg malmb...@encompasserve.org
wrote:
I can not seem to do a rmdir() of an absolute or relative Unix
path with Perl 5.18.1.
It works unless DECC$FILENAME_UNIX_REPORT is defined. That's not
particularly
I am trying to get the GNU make 4.0.90 self tests run on VMS, and they
are written in perl.
I am making some progress, but have found some issues.
I can not seem to do a rmdir() of an absolute or relative Unix path with
Perl 5.18.1.
I have worked around the issue by replacing the rmdir()
On 9/20/2013 8:05 PM, Craig A. Berry wrote:
On Sep 20, 2013, at 6:01 PM, John E. Malmberg
malmb...@encompasserve.org wrote:
After all, if you are going to always use Perl to invoke it, why
add the hack to make it work as a command file?
Because you may not use Perl to invoke it. You
On 9/21/2013 12:48 PM, Craig A. Berry wrote:
On Sep 21, 2013, at 11:02 AM, John E. Malmberg malmb...@encompasserve.org
wrote:
On 9/20/2013 8:05 PM, Craig A. Berry wrote:
On Sep 20, 2013, at 6:01 PM, John E. Malmberg
malmb...@encompasserve.org wrote:
After all, if you are going
The perldoc command looks weird on VMS, and I do not know the origin of
that convention.
VMS does not support shebangs.
Passing parameters on the command line to a program require that either
the DCL shell command tables be modified to know about that command, or
a foreign command to be
On 9/19/2013 1:36 PM, Nicholas Clark wrote:
If I delete the perldoc.com, I get this:
$ perldoc
Can't open perl script perl_root:[utils]perldoc.com: no such file or directory
%SYSTEM-F-ABORT, abort
(mail client may wrape the line)
LION show sym perldoc
PERLDOC == $PERL_ROOT:[00]PERL.EXE
On 8/8/2013 2:31 AM, Nicholas Clark wrote:
I think these changes are sane. Once upon a time, the CRTL did not
support /dev/null as an alias for the native _NLA0:.
I would have to build up a VMS 5.5-2 system on a SimH emulator to be
sure of the behavior back at the beginning of the current
On 8/7/2013 12:23 PM, Nicholas Clark wrote:
I have this commit pushed to a smoke-me branch. It doesn't cause any test
failures on the HP VMS testdrive system. Am I making bad assumptions?
Specifically, is it filesystem dependant whether this code as-is will pass?
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
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
On 12/22/2012 8:07 AM, Craig A. Berry wrote:
MCR SYS$DISK:[]generate_uudmap.exe uudmap.h bitcount.h mg_data.h
Action did not update target BITCOUNT.H
Action did not update target MG_DATA.H
I'm not sure if this is a problem or not.
Don't think so. MMS and MMK feel the need to tell you that
Bash 4.2.39 is the current release and patch level of the GNU bash
project and is now available for OpenVMS.
Items of specific interest to the to the VMS Perl community are:
Recent versions of Perl will go into a UNIX mode when run under Bash
4.2.39. This support of GNV is not 100 % complete
Before I go through the trouble of writing this, is anyone aware of a
perl script that can be run on VMS using the DROPBOX.COM perl API to
keep a VMS directory in synchronization?
Currently I use NFS served disks on my local systems which are backed up
/ replicated to dropbox.
What I am
On 10/26/2012 6:04 AM, Vorländer, Martin wrote:
Parrot wants dynamic PMCs as dynamically loadable files, i.e. shared images.
Building of these already works, but of course a lib$find_image_symbol won't
find any symbols (as I don't yet have a SYMBOL_VECTOR).
So I'm now diving into the process
VMS Engineering has given us some feedback on SCP:
The pscp program from Linux putty tools package will work with the VMS
SCP program.
I tested this and it work.
This package does not appear to be available for Mac OS-X, so I do not
have a solution there.
Regards,
-John
On 5/22/2012 3:18 PM, Mark Berryman wrote:
Instead, I simply built libssh2 on the unix box and used the example
program sftp_write.c
I just tried the sftp program in Scientific Linux 6.1 and it can upload
files. The help for it says that it can recursively upload a directory.
It looks
On 5/19/2012 2:56 AM, Nicholas Clark wrote:
Yes, this is the fun, and why it turns out that scp from VMS out to *nix
works, but not the other way. Pretty much every *nix is using OpenSSH,
whereas the VMS ssh is commercial ssh. OpenSSH has the original scp
command, which I think is actually the
I have submitted a list of issues about the HP OpenSource cluster that
Nicholas posted, and a few others that I noticed to the Office of
OpenVMS programs e-mail address and a received a reply that they will be
looking at getting these resolved.
Regards,
-John
Personal Opinion Only
On 5/15/2012 12:52 PM, Carl Friedberg wrote:
At this very moment, all 3 of my VMS servers are unreachable,
but normally they are accessible.
I have two (pretty ancient) AlphaServer 800's, single 500mhz
processor, 2 Gb memory, running recent VMS with hobbyist
licenses. I also have an Itanium
On 8/8/2011 5:25 AM, Nicholas Clark wrote:
On Sun, Aug 07, 2011 at 01:44:23PM -0700, Father Chrysostomos wrote:
If I change the quotes at the top of the *.c files in the perl source code to
use UTF-8 instead of Latin-1, would anyone object?
I have my text editor set to use UTF-8 by default,
Fabio Ciampi wrote:
Hi
I'm a newbie of VMS. I've tried to build perl 5.10.1 on my IA64
Welcome to VMS.
I see a couple of newbie mistakes below, but they probably are not
causing the issues that you are seeing, just additional issues.
And these are somethings that people with experience
On 6/24/2010 2:03 PM, Mark Berryman wrote:
On Jun 24, 2010, at 12:08 PM, Craig A. Berry wrote:
4. Too many extensions like to use labels that differ only in
case or reference external libraries that are built with
/names=(as_is,short). By editing 3 include files in Perl, extern.h,
perl.h,
martin.zin...@deutsche-boerse.com wrote:
Hello Colleagues,
I am currently trying to drag our development team kicking and screaming
into the century of the fruitbat, but what looks like a bug in 5.10.1 and
5.12.0 is a stumbling block.
Problem description:
If you open a text file with
Nicholas Clark wrote:
Currently the core uses File::Spec inside the test running script, t/TEST,
that VMS uses. If I understand perlvms.pod correctly, perl on VMS can
understand Unix-like pathnames directly.
I'd like to remove File::Spec from t/TEST, as it's something complex run too
early in
Nicholas Clark wrote:
On Mon, Aug 24, 2009 at 08:40:44AM -0500, John E. Malmberg wrote:
Nicholas Clark wrote:
Currently the core uses File::Spec inside the test running script, t/TEST,
that VMS uses. If I understand perlvms.pod correctly, perl on VMS can
understand Unix-like pathnames directly
Craig A. Berry wrote:
On Jul 24, 2009, at 3:40 PM, Nicholas Clark wrote:
On Fri, Jul 24, 2009 at 03:35:33PM -0500, Craig A. Berry wrote:
I've finally got Test::Smoke mostly working on VMS except for my local
mail configuration, thus the manual attachment here. It shows the
Ooh. ooh. ooh.
Craig A. Berry wrote:
It's looking like we'll get a release candidate for Perl 5.10.1 in the
next week or two. Indications are it will be the best ever Perl on VMS
release, but it would be helpful if the so-called perldelta, the changes
since the previous release, could be updated for
Craig A. Berry wrote:
On Jul 15, 2009, at 9:45 PM, John E. Malmberg wrote:
An update to the pod is in order for the PERL_VMS_POSIX_EXIT logical
name. That should help you with what to put in the delta file.
Thanks, John, this is in blead at
http://perl5.git.perl.org/perl.git/commitdiff
I seem to have made some progress with GIT.
I have it building now, but I am confused as the program execs image
names slightly different than the ones that the build procedure creates
and installed.
If I rename the module to match the name that git uses, that seems to work.
The only thing
John E. Malmberg wrote:
Here is the latest attempt. Still not fully tested.
And the results are that with this new change, I am getting failures in
the UNIX mode with: lib/File/Compare.t,
lib/File/Spec/t/Crossplatform.t, lib/File/Temp/t/object.t,
lib/Module/Build/t/compat.t, lib/vmsish.t
Thomas Pfau wrote:
John E. Malmberg wrote:
We really need to get some sort of logical name support that we can
count on being bundled with Perl on VMS.
My VMS::Logical module appears to work. I don't think I ever uploaded it
to CPAN but I could do that.
http://axp1.nbpfaus.net/~pfau/perl
Craig A. Berry wrote:
On Jun 10, 2009, at 7:29 PM, John E. Malmberg wrote:
There is considerable interest currently in removing extensions from the
core and reluctance to add them. This derives from somewhat of a binge
in adding new extensions in recent years that add to the maintenance
John E. Malmberg wrote:
Craig A. Berry wrote:
I went back to my original test case (not the narrower one you ended
up fixing) and it looks like we are half-way there. If both
DECC$EFS_CHARSET and DECC$FILENAME_UNIX_REPORT are defined, this works:
$ perl -MFile::Spec::Functions -e print
Craig A. Berry wrote:
On Jun 8, 2009, at 1:42 AM, John E. Malmberg wrote:
Below inline:
John E. Malmberg wrote:
Craig A. Berry wrote:
I went back to my original test case (not the narrower one you ended
up fixing) and it looks like we are half-way there. If both
DECC$EFS_CHARSET
Here is the latest attempt. Still not fully tested.
The VMS format of logical foo:bar, such as sys$scratch:foo seems to be
causing all sorts of problems.
catpath(sys$scratch:,,foo.bar) can not work. The catpath method can
not deal with an empty directory, so will treat 'foo.bar' as a
Craig A. Berry wrote:
I went back to my original test case (not the narrower one you ended up
fixing) and it looks like we are half-way there. If both
DECC$EFS_CHARSET and DECC$FILENAME_UNIX_REPORT are defined, this works:
$ perl -MFile::Spec::Functions -e print
This patch fixes an issue that Craig Berry found in the handling of
logical names of the form foo = device:[dir] when the EFS character
set is enabled.
Regards,
-John
wb8...@qsl.net
Personal Opinion Only
--- /rsync_root/perl/vms/vms.c Sun Feb 22 21:22:09 2009
+++ vms/vms.c Tue Jun 2
Craig A. Berry wrote:
On Thu, Jun 4, 2009 at 9:18 AM, Craig A. Berry craigbe...@mac.com wrote:
On Jun 4, 2009, at 8:46 AM, John E. Malmberg wrote:
This patch fixes an issue that Craig Berry found in the handling of
logical names of the form foo = device:[dir] when the EFS character set
Craig A. Berry wrote:
Thanks. The blead build is currently broken so don't synch first.
Hopefully we'll get it all sorted out soonish.
I just tried to sync up with blead and it stopped at writing Descrip.mms
for Attribute::Handlers.
Is that the issue that you are seeing?
-John
Craig A. Berry wrote:
With current blead, if I define both DECC$EFS_CHARSET and
DECC$EFS_FILENAME_UNIX_REPORT, I see the following:
$ perl -MFile::Spec::Functions -e print catfile(File::Spec-tmpdir(),
'bar');
./bar
Obviously it should be giving me '/sys$scratch/bar'.
With only
John E. Malmberg wrote:
Craig A. Berry wrote:
With current blead, if I define both DECC$EFS_CHARSET and
DECC$EFS_FILENAME_UNIX_REPORT, I see the following:
$ perl -MFile::Spec::Functions -e print
catfile(File::Spec-tmpdir(), 'bar');
./bar
Obviously it should be giving me '/sys$scratch/bar
Craig A. Berry wrote:
On Jun 2, 2009, at 8:39 AM, John E. Malmberg wrote:
John E. Malmberg wrote:
The bug is in vms.c, not File::Spec. These two one liners
demonstrate it:
EAGLE perl -e print 'true' if -w '/sys$scratch'
EAGLE perl -e print 'true' if -w 'sys$scratch:'
true
Something
The lib/file/compare.t test has never been correct for VMS, but the bugs
where mostly hidden until testing on a ODS-5 volume with that allows
filenames with more characters in them than VMS traditionally allows.
This is known as EFS_CHARSET mode.
This also exposes that the vmsify() routine in
Craig A. Berry wrote:
On May 30, 2009, at 12:39 PM, John E. Malmberg wrote:
The lib/file/compare.t test has never been correct for VMS, but the
bugs where mostly hidden until testing on a ODS-5 volume with that
allows filenames with more characters in them than VMS traditionally
allows
Dave Mitchell wrote:
On Sun, May 24, 2009 at 04:38:15PM -0500, John E. Malmberg wrote:
Craig A. Berry wrote:
I think that some of my patches to allow the ExtUtils modules to work
with the Extended Character sets on ODS-5 volumes and the UNIX report
modes have not yet made it into the CPAN
John E. Malmberg wrote:
Dave Mitchell wrote:
On Sun, May 24, 2009 at 04:38:15PM -0500, John E. Malmberg wrote:
Craig A. Berry wrote:
I think that some of my patches to allow the ExtUtils modules to
work with the Extended Character sets on ODS-5 volumes and the UNIX
report modes have
This patches Magic.t to remove the $ENV{foo} it created on VMS.
This environment variable interferes with running other tests including
CPAN tests.
-John
wb8...@qsl.net
Personal Opinion Only
--- /rsync_root/perl/t/op/magic.t Fri May 22 11:40:09 2009
+++ t/op/magic.tMon May 25
This patch fixes lib/perl5db.t to not leave a db.out file behind on VMS
after a test run.
-John
wb8...@qsl.net
Personal Opinion Only
--- /rsync_root/perl/lib/perl5db.t Fri Dec 19 03:14:10 2008
+++ lib/perl5db.t Mon May 25 16:02:21 2009
@@ -85,5 +85,5 @@
# clean up.
END {
-
This patch fixes lib/Pod/text-options.t to not leave tmp.pod and out.tmp
files behind on VMS.
-John
wb8...@qsl.net
Personal Opinion Only
--- /rsync_root/perl/lib/Pod/t/text-options.t Fri Dec 19 03:14:10 2008
+++ lib/Pod/t/text-options.tMon May 25 16:23:28 2009
@@ -69,7 +69,7 @@
Craig A. Berry wrote:
With everything default except -Duseithreads, I see:
Failed 6 tests out of 1564, 99.62% okay.
[-.lib.CPANPLUS.Dist.Build.t]02_CPANPLUS-Dist-Build.t
[-.lib.CPANPLUS.t]19_CPANPLUS-Dist.t
[-.lib.ExtUtils.t]basic.t
[-.lib.Module.Build.t]compat.t
Craig A. Berry wrote:
On May 18, 2009, at 11:54 PM, John E. Malmberg wrote:
John E. Malmberg wrote:
The trail has taken me to the following lines just below the comment
with the tag AMS 20010810.
while(mg) {
const MGVTBL * const vtbl = mg-mg_virtual;
if (!(mg-mg_flags MGf_GSKIP
John E. Malmberg wrote:
The trail has taken me to the following lines just below the comment
with the tag AMS 20010810.
while(mg) {
const MGVTBL * const vtbl = mg-mg_virtual;
if (!(mg-mg_flags MGf_GSKIP) vtbl vtbl-svt_get) {
CALL_FTPR(vtbl-sv_get)(aTHX_ sv, mg
Nicholas Clark wrote:
On Tue, May 19, 2009 at 08:18:17AM -0500, John E. Malmberg wrote:
Craig A. Berry wrote:
So you're saying that these lines in Perl_magic_get in mg.c:
case '?':
{
sv_setiv(sv, (IV)STATUS_CURRENT);
#ifdef COMPLEX_STATUS
LvTARGOFF(sv
Some progress:
I have not been able to find a connection between the code 44 returned
by the system() routine and the memory getting corrupted.
By putting in code to periodically check the Ibody_root[7] linked list,
the data corruption is occurring in SvSetMagic/Perl_pp_assign which is
Craig A. Berry wrote:
On May 10, 2009, at 4:27 PM, Dave Mitchell wrote:
On Thu, May 07, 2009 at 08:52:54PM -0500, John E. Malmberg wrote:
Craig A. Berry wrote:
With a -Duseithreads build using HP C V7.3-018 on OpenVMS IA64
V8.3-1H1, I get:
ext/Cwd/t/cwd
Mark Berryman wrote:
I need to install the Net::SSH::Perl module in Perl V5.10.0 on VMS V8.3
which means I need the Math::Pari module. Unfortunately, the build code
for this module generates extensive Unix syntax and I don't know enough
about the build process within Perl to fix it. This is
Craig A. Berry wrote:
With a -Duseithreads build using HP C V7.3-018 on OpenVMS IA64 V8.3-1H1,
I get:
ext/Cwd/t/cwd.FAILED at
test 23
lib/Archive/Extract/t/01_Archive-Extract..FAILED at
test 74
John E. Malmberg wrote:
Craig A. Berry wrote:
On May 3, 2009, at 9:20 PM, John E. Malmberg wrote:
John E. Malmberg wrote:
Perl_sv_upgrade(pTHX_ register SV *const sv, svtype new_type)
case SVt_PVMG:
...
new_body_inline(new_body, new_type);
new_type = SVt_PVMG,
SVt_PVMG has a value
Craig A. Berry wrote:
On May 3, 2009, at 9:20 PM, John E. Malmberg wrote:
John E. Malmberg wrote:
Perl_sv_upgrade(pTHX_ register SV *const sv, svtype new_type)
case SVt_PVMG:
...
new_body_inline(new_body, new_type);
new_type = SVt_PVMG,
SVt_PVMG has a value of 7.
new_body = 44
John E. Malmberg wrote:
John E. Malmberg wrote:
Nicholas Clark wrote:
On Mon, Apr 27, 2009 at 12:27:02AM -0500, John E. Malmberg wrote:
I just started looking into a failure of 19_CPANPLUS-Dist. I have
not determined what exactly is wrong, and am out of time for the
moment.
I will try
John E. Malmberg wrote:
Nicholas Clark wrote:
On Mon, Apr 27, 2009 at 12:27:02AM -0500, John E. Malmberg wrote:
I just started looking into a failure of 19_CPANPLUS-Dist. I have
not determined what exactly is wrong, and am out of time for the moment.
I will try to get some more information
Nicholas Clark wrote:
On Mon, Apr 27, 2009 at 12:27:02AM -0500, John E. Malmberg wrote:
I just started looking into a failure of 19_CPANPLUS-Dist. I have not
determined what exactly is wrong, and am out of time for the moment.
I will try to get some more information later.
It is failing
Craig A. Berry wrote:
On Apr 27, 2009, at 8:40 AM, Nicholas Clark wrote:
On Mon, Apr 27, 2009 at 12:27:02AM -0500, John E. Malmberg wrote:
I just started looking into a failure of 19_CPANPLUS-Dist. I have not
determined what exactly is wrong, and am out of time for the moment.
I will try
Module::Build needs a patch to get the last test to pass on VMS.
https://rt.cpan.org/Ticket/Display.html?id=45461
-John
wb8...@qsl.net
Personal Opinion Only
I just started looking into a failure of 19_CPANPLUS-Dist. I have not
determined what exactly is wrong, and am out of time for the moment.
I will try to get some more information later.
It is failing from an access violation in SV.C.
ok 57 -Perl version not high enough
%SYSTEM-F-ACCVIO,
The VMS pipe bug inserts blank lines in places that can prevent the
leader from being seen.
So on the leader line, read in the rest of the line.
Related VMS TODO: The VMS/test.com procedure is passing an uppercase
path specification instead of exact case or forced to lowercase.
This can
Craig A. Berry wrote:
On Apr 10, 2009, at 9:55 PM, John E. Malmberg wrote:
[Dropping some names off the distribution as similar information has
been sent to them]
John E. Malmberg wrote:
Craig A. Berry wrote:
On Apr 10, 2009, at 4:20 PM, Michael G Schwern wrote:
GNV should
[Dropping some names off the distribution as similar information has
been sent to them]
John E. Malmberg wrote:
Craig A. Berry wrote:
On Apr 10, 2009, at 4:20 PM, Michael G Schwern wrote:
GNV should not be assigning that logical name and later versions than
the one they've got there don't
Craig A. Berry wrote:
On Apr 10, 2009, at 4:20 PM, Michael G Schwern wrote:
GNV should not be assigning that logical name and later versions than
the one they've got there don't. It should be safe just to deassign it.
$ @gnv$gnu:[lib]gnv_setup.com
$ show log bin
BIN = GNV$GNU:[BIN]
Michael G Schwern wrote:
John E. Malmberg wrote:
It is only the case where something is building a VMS specific Make
script or building a DCL command file that a filename needs to
specifically be converted to VMS path syntax.
Ok, then build it into the MakeMaker File::Spec overrides and use
Michael G Schwern wrote:
John E. Malmberg wrote:
Are you going to have time to look at the patches that I submitted to
MakeMaker and Test::Simple?
These are to support VMS when the DECC$FILENAME_UNIX_REPORT and
DECC$EFS_CHARSET and related options are active.
These options make Perl on VMS
Craig A. Berry wrote:
On Dec 9, 2008, at 10:30 PM, John E. Malmberg wrote:
Tainting DCL$PATH has no effect on Perl on VMS.
But DCL$PATH will be used by DCL after invoking system() or backticks in
a manner very similar to how PATH is used on other systems. Tainting is
specifically
Tainting DCL$PATH has no effect on Perl on VMS.
That logical name is not currently used internal to Perl so it never
gets checked to see if it is tainted.
So even when the /tmp directory exists and is world writable, these
tests will not pass.
-John
[EMAIL PROTECTED]
Personal Opinion Only
John E. Malmberg wrote:
The mp_do_pathify_dirspec needed enhancements to more accurately parse
VMS file specifications, and also to handle UNIX file specifications the
same way that mp_do_tovmspath() does.
It was simpler to replace than to try to modify the existing routine.
In addition
The VMS parsing routines were failing on files that the process
currently did not have access to, instead of falling back to a syntax
only check.
We may want to consider always falling back to a syntax only check as
there may be more non-fatal return codes of these type.
-John
[EMAIL
This patch makes a version of unixify available for calling with out an
implicit context, which is needed for threaded perl as several routines
do not have a thread context.
This is the second of a multi-part conversion to remove access
violations when internal perl warning and error
Craig A. Berry wrote:
On Dec 7, 2008, at 12:46 PM, John E. Malmberg wrote:
Point taken,
Attached is vms/ext/filespec.t that changes those tests to be passing.
The documentation for VMS::Filespec::pathify says, the file type and
version, if specified, must be .DIR;1. For compatibility
This patch makes a version of vmsify and vmspath available for calling
with out an implicit context, which is needed for threaded perl as
several routines do not have or need an implicit context.
This is the fourth of a multi-part conversion to remove access
violations when internal perl
This patch makes a version of fileify available for calling with out an
implicit context, which is needed for threaded perl as several routines
do not have or need an implicit context.
This is the fifth of a multi-part conversion to remove access violations
when internal perl warning and
This patch makes a version of rmsexpand available for calling with out
an implicit context, which is needed for threaded perl as several
routines do not have or need an implicit context.
This is the sixth of a multi-part conversion to remove access violations
when internal perl warning and
In the test to see what happens if you try to create a file with the
same name as a directory, catdir is used to create the file
specification instead of catfile.
The operation is expected to fail usually.
However on VMS, directories and files can appear to have the same name,
especially
The mp_do_pathify_dirspec needed enhancements to more accurately parse
VMS file specifications, and also to handle UNIX file specifications the
same way that mp_do_tovmspath() does.
It was simpler to replace than to try to modify the existing routine.
In addition this is the start of fixing
In trim_unixpath, the wrong free routine was being used resulting in
data corruption.
-John
[EMAIL PROTECTED]
Personal Opinion Only
--- /rsync_root/perl/vms/vms.c Sun Nov 23 22:54:17 2008
+++ vms/vms.c Wed Dec 3 19:05:18 2008
@@ -9345,10 +9345,10 @@
char def[NAM$C_MAXRSS+1], *st;
Craig A. Berry wrote:
On Nov 30, 2008, at 6:04 PM, John E. Malmberg wrote:
Test 04_Resolved_Issues was failing on VMS because it was translating
.. to __. Use vmspath() instead so that dots are escaped if needed.
Also filed as:
http://rt.cpan.org/Public/Bug/Display.html?id=41329
configure.com needs a little more work to implement usedevel.
-John
[EMAIL PROTECTED]
Personal Opinion Only
--- /rsync_root/perl/configure.com Fri Nov 28 01:53:05 2008
+++ configure.com Fri Nov 28 11:12:21 2008
@@ -6520,6 +6520,7 @@
$ WC usedebugging_perl='+use_debugging_perl+'
$ WC
Craig A. Berry wrote:
On Nov 28, 2008, at 11:31 AM, John E. Malmberg wrote:
configure.com needs a little more work to implement usedevel.
-John
[EMAIL PROTECTED]
Personal Opinion Only
--- /rsync_root/perl/configure.comFri Nov 28 01:53:05 2008
+++ configure.comFri Nov 28 11:12:21 2008
Craig A. Berry wrote:
On Nov 24, 2008, at 8:32 PM, John E. Malmberg wrote:
In lib/File/Compare.t :
The tests with the filename having a trailing space was not working
correctly on VMS in the traditional mode, and was leaving one of the
temporary files behind.
With VMS in the Extended
purnima bhandari wrote:
Hi All,
Thanks for all the help...
I am able to link by adding my own .com fine which is defining the
compiler's needed logical.I added that one in the descrip.mms file into
the .FIRST location for MMK and i also modified the descrip_mms.template
for Perl5.10.0.
In lib/File/Compare.t :
The tests with the filename having a trailing space was not working
correctly on VMS in the traditional mode, and was leaving one of the
temporary files behind.
With VMS in the Extended File System (EFS) character set mode, the test
fails because it requires two
Readdir() on VMS, when opening a directory with a UNIX file
specification, should return all the files in UNIX format.
This includes dropping the .DIR from the directory specifications.
Because traditionally Perl has not done this, this fix will only be done
when the DECC$EFS_CHARSET feature
Craig A. Berry wrote:
On Wed, Nov 12, 2008 at 10:13 PM, Michael G Schwern [EMAIL PROTECTED] wrote:
John E. Malmberg wrote:
Putting a print STDERR statement shows that is not the case, that the
methods of those names contained in File::Spec::VMS are used unless they
are called by MM_VMS
The comments for eliminate_macros() and fixpath() in File::Spec::VMS
imply that they are only used in older versions of Make Maker that does
not contain them.
Putting a print STDERR statement shows that is not the case, that the
methods of those names contained in File::Spec::VMS are used
Michael G Schwern wrote:
John E. Malmberg wrote:
The comments for eliminate_macros() and fixpath() in File::Spec::VMS
imply that they are only used in older versions of Make Maker that does
not contain them.
Putting a print STDERR statement shows that is not the case, that the
methods of those
Craig A. Berry wrote:
On Thu, Oct 30, 2008 at 11:03 AM, Craig A. Berry
[EMAIL PROTECTED] wrote:
On Wed, Oct 29, 2008 at 10:21 PM, John E. Malmberg [EMAIL PROTECTED] wrote:
Resubmitting for review.
I removed the setup_cmddsc, and the unneeded readdir stuff, so this patch is
what is needed
This is part of the patch previously submitted as part of a multi-part
patch.
This removes a trailing . that results in ODS-5 mode when converting a
Unix foo/bar specification to be [.foo]bar..
This is incompatible with having setup_cmddsc searching for the
resulting binary by appending
Ok,
Resubmitting for review.
I removed the setup_cmddsc, and the unneeded readdir stuff, so this
patch is what is needed for getting the symbolic links to be encoded and
decoded properly in VMS.C and for CWD in pathtools.
-John
[EMAIL PROTECTED]
Personal Opinion Only
---
1 - 100 of 663 matches
Mail list logo
