sebb <[EMAIL PROTECTED]> wrote on 08/15/2005 08:34:31 PM:
> > > Would it not be better to fix the VMS Perl open() call so it works
the
> > > same as on other OSes?
>
> I meant for READ access only here.
The performance impact of altering perl's open() to use the CRTL
shr would be significant.
"John E. Malmberg" <[EMAIL PROTECTED]> wrote on 07/11/2005 11:14:22 PM:
> Correct. Remember my diffs are against the perl 5.8.6 release.
>
> Is 5.8.7 a release kit now?
stable.tar.gz from CPAN is 5.8.7.
Peter Prymmer
"Craig A. Berry" <[EMAIL PROTECTED]> wrote on 07/11/2005 10:38:34 PM:
> At 6:43 PM -0400 7/11/05, John Malmberg wrote:
>
> >Perl_setup.com is optionally built such that it defines perl_root based
on
> the directory it currently resides in, as a step toward being able to
build a
> binary distributi
"Craig A. Berry" <[EMAIL PROTECTED]> wrote on 07/11/2005 10:13:56 PM:
> >+$ IF (tmp .GES. "8.2") .AND. (f$getsyi("HW_MODEL") .GE. 1024)
>
> Last time I checked, Itanium systems return zero for
> f$getsyi("HW_MODEL"). The archname symbol should already have one of
> VMS_VAX, VMS_AXP, or VMS_IA64,
Michael G Schwern <[EMAIL PROTECTED]> wrote on 07/11/2005 02:58:55 PM:
> On Mon, Jul 11, 2005 at 02:17:04PM -0400, [EMAIL PROTECTED] wrote:
> > In the resultant output only tests 1 through 136 actually ran (missing
> > tests
> > 137 through 142). There were so many failures that it might be bette
Michael G Schwern <[EMAIL PROTECTED]> wrote on 07/11/2005 02:46:14 AM:
> vms/ext/Filespec.pm is out of date and broken.
Indeed. It appears that filespec.t is not run on Solaris for example
(IIRC that test used to be run on Unix automatically).
Here are the shell commands I just had to run to co
Michael G Schwern <[EMAIL PROTECTED]> wrote on 07/08/2005 08:09:40 PM:
> I'm examining the feasibility of making VMS::Filespec available to all
> installations (makes testing File::Spec::VMS a whole lot easier) and
> ran vms/ext/filespec.t on my OS X box. I got some failures but none
> of them se
Michael G Schwern <[EMAIL PROTECTED]> wrote on 03/29/2005 05:23:16 PM:
> Yes it is. That indicates the test module never got built. Doesn't say
> why though... If you're feeling adventurous could you step into setup()
> on line 25 of PL_FILES.t and poke around?
One could either modify setup o
d: 0
# Failed test (t/PL_FILES.t at line 38)
t/PL_FILES..NOK 3# got: '256'
# expected: '0'
# make: Fatal error: No arguments to build
# Current working directory /home/pprymmer/testit/ExtUtils-MakeMaker-6.26
_01/t
# Failed test (t/PL_FILES.t at li
Craig Berry <[EMAIL PROTECTED]> wrote on 03/15/2005 11:38:18 AM:
> On Tuesday, March 15, 2005, at 08:56AM, John E. Malmberg
> <[EMAIL PROTECTED]> wrote:
> >Is there a perl script that will identify all files that are present in
> >the unpacked directory except for the ones in the manifest or wher
Ken Williams <[EMAIL PROTECTED]> wrote on 03/14/2005 04:23:10 PM:
> Thanks, applied verbatim (except that I moved the system() call into a
> my_system() subroutine in case I want to use it again later).
Hmm - well I suppose I should mention a few tricky aspects
of using MCR on VMS. Perhaps most
Ken Williams <[EMAIL PROTECTED]> wrote on 03/12/2005 10:35:22 PM:
> On Mar 12, 2005, at 7:18 PM, Ken Williams wrote:
> >
> > Excellent. I just have one question, then, about the following line:
> >
> > my @lddlflags = $args{lddl} ? ($cf->{lddlflags}."=$out") :
> > ("/exe=$out");
> >
> > What is
Ken Williams <[EMAIL PROTECTED]> wrote on 03/06/2005 10:50:17 AM:
> Care to try 0.09_01, which is now hitting CPAN? I've split out the
> generation of command-line switches so it can easily be overridden for
> VMS. So compile() might work now. link() and friends haven't been
> touched, though.
Michael G Schwern <[EMAIL PROTECTED]> wrote on 03/04/2005 06:12:36 PM:
> CC/DECC -Iperl_root:[lib.VMS_AXP.5_8_0.CORE] -c
/Include=[]/Standard=Relaxed_ANS
> I/Prefix=All/Obj=.obj /NOANSI_ALIAS/float=ieee/ieee=denorm_results
/NoList -o US
> ER1:[SCHWERN]compilet.obj USER1:[SCHWERN]compilet.c
> %DCL-
Thomas R Wyant_III <[EMAIL PROTECTED]> wrote on 02/22/2005
03:34:59 PM:
> I was trying to get VMS::Stat going under VMS 7.1-1. Unfortunately, that
> version doesn't have fab$v_erl (a.k.a. the "erase" bit). I was going to
> develop a patch, but I'm having trouble establishing which version
> introd
Michael G Schwern <[EMAIL PROTECTED]> wrote on 02/08/2005 09:31:48 AM:
> Its time for another MakeMaker alpha! This one is mostly VMS fixes
though
> I also discovered a conflict with Module::Install and undid an accidental
> change that broken Archive::Zip. As far as I know all outstanding issue
"John E. Malmberg" <[EMAIL PROTECTED]> wrote on 02/15/2005
03:21:01 PM:
> If anyone has any suggestions on an easy way to do this, please let me
> know.
I'd recommend rewriting config.h before you compile perl under GNV, later
you could modify the Configure script itself to recognize GNV as a
dis
Thomas R Wyant_III <[EMAIL PROTECTED]> wrote on 02/08/2005
10:54:34 AM:
> This doesn't exhaust the list by any means. The main omission I know of
is
> f$file_attributes. The Perl stat () function handles the portable portion
> of this, but not the RMS-specific part.
VMS::Stat handles many f$file
Peter Prymmer/FactSet wrote on 01/05/2005 11:18:01 AM:
> was buildable by it. If 6.25_08 gets released I'll see
> about patching it, otherwise I may try to prepare a patch
> for 6.25_07 (but don't wait too long for me).
I have tried to browse over to
http://www.pobox.com/~schwern/src/ExtUtils-Ma
Peter Prymmer/FactSet wrote on 01/05/2005 11:18:01 AM:
> That is not quite correct. As it turns out $(MMS$SOURCE_LIST) is a comma
> separated list of filenames without types (in the language of RMS file
parsing
> TYPEs are also known as "extensions" in the Windows centric world). This
> differen
Michael G Schwern <[EMAIL PROTECTED]> wrote on 01/04/2005 05:12:32 PM:
> Ahh, $(MMS$SOURCE_LIST) is a list of all dependencies. I think it can be
> safely removed. The logic is this:
>
> if ($self->{MYEXTLIB}) {
> push(@m,"\t",'Library/Object/Replace $(MMS$TARGET)
$(OBJECT)',"\n");
>
Michael G Schwern <[EMAIL PROTECTED]> wrote on 01/04/2005 04:44:50 PM:
> On Fri, Dec 31, 2004 at 12:41:38PM -0500, [EMAIL PROTECTED] wrote:
> > Which looks like a problem with DBI code not MakeMaker.
>
> Did DBI work with 6.17?
DBI 1.45 would build with 6.17, but as Craig pointed out
the Makefile
Michael G Schwern <[EMAIL PROTECTED]> wrote on 01/04/2005 04:46:54 PM:
> > -$(INST_STATIC) : $(OBJECT) $(MYEXTLIB)
$(INST_ARCHAUTODIR)$(DFSEP).exists
> > +$(INST_STATIC) : $(OBJECT) $(MYEXTLIB)
> > ';
> > # If this extension has its own library (eg SDBM_File)
> > # then copy that to $(I
Michael G Schwern <[EMAIL PROTECTED]> wrote on 01/03/2005 02:41:17 PM:
> Do these guys charge for upgrades or something?
They might.
Peter Prymmer
Michael G Schwern <[EMAIL PROTECTED]> wrote on 01/01/2005 06:50:43 PM:
> I don't quite understand what 6.17 has to do with it. MakeMaker builds
> itself using itself, not the installed version.
Sorry - I did not realize that.
> > With that installed a second attempt to build it with mms 3.2-01
Michael G Schwern <[EMAIL PROTECTED]> wrote on 01/01/2005 07:38:57 PM:
> My bad. I left in a / when I unified the VMS tool_xsubpp(). Its better
> solved by changing $(XSUBPPDIR)/xsbupp to $(XSUBPPDIR)$(DFSEP)xsubpp.
I can confirm that this solution would be fine for VMS since
DFSEP contains an
Peter Prymmer/FactSet wrote on 01/03/2005 10:54:24 AM:
> I'll see about restoring the cleaning of .opt files next.
OK here is a patch that implements this extra clean target file
cleanup.
--- ExtUtils-MakeMaker-6_25_07/lib/ExtUtils/MM_VMS.pm;-3Mon Jan 3 10:43:10
2005
+++ ExtUtils-MakeMaker
Peter Prymmer/FactSet wrote on 12/31/2004 04:36:31 PM:
> I have not yet found how to fix the .exists into OLB
> problem nor the trouble with MMS V3.2-01 reported earlier.
I forgot to mention that *.opt files are not being cleaned
on VMS as another problem that persists.
I seem to have solved the
[EMAIL PROTECTED] wrote on 12/31/2004 12:41:38 PM:
> This is beginning to look like a problem with the XSUBPP macros.
I've found a workwaround for this specific problem that I'll
enclose as a diff. Since an OS specific hack inside of
MM_Unix.pm seems completely counter to the whole "put override
"Craig A. Berry" <[EMAIL PROTECTED]> wrote on 12/31/2004 03:34:14 PM:
> I think this one is an old problem specific to DBI, and IIRC it's
> because it expects dbiproxy.PL to be a different file from
> dbiproxy.pl.
Indeed it seems that this is the case. I am sorry for having
reported a spurious p
[EMAIL PROTECTED] wrote on 12/31/2004 01:01:12 PM:
> One other oddity noted with 6.25_07:
>
> $ mmk distclean
>
> Not in MANIFEST: dbi.opt
>
> I am fairly certain that it used to be able to delete the
> linker options files that it wrote out before.
I failed to mention this one before but it app
[EMAIL PROTECTED] wrote on 12/31/2004 01:01:12 PM:
> [EMAIL PROTECTED] wrote on 12/31/2004 12:41:38 PM:
>
> > I hope that provides some useful feedback. Sorry I do not yet
> > have a path for the XSUBPP problems on VMS.
>
> One other oddity noted with 6.25_07:
Here is another oddity. The .exist
[EMAIL PROTECTED] wrote on 12/31/2004 12:41:38 PM:
> I hope that provides some useful feedback. Sorry I do not yet
> have a path for the XSUBPP problems on VMS.
One other oddity noted with 6.25_07:
$ mmk distclean
Not in MANIFEST: dbi.opt
I am fairly certain that it used to be able to delete
Michael G Schwern <[EMAIL PROTECTED]> wrote on 12/30/2004 05:22:30 PM:
> On Thu, Dec 30, 2004 at 04:47:18PM -0500, [EMAIL PROTECTED] wrote:
> > I might even get to my big module collection test with this
>
> Wait for the next alpha. I have to fix that IGNORE problem first.
Warning: this mess
Michael G Schwern <[EMAIL PROTECTED]> wrote on 12/31/2004 03:59:29 AM:
> http://www.pobox.com/~schwern/src/ExtUtils-MakeMaker-6.25_07.tar.gz
Test obtained. First using perl 5.8.6 and mmk V3.9-6:
All tests successful, 7 tests and 94 subtests skipped.
Files=38, Tests=639, 239 wallclock secs ( 0.0
Michael G Schwern <[EMAIL PROTECTED]> wrote on 12/30/2004 03:55:15 PM:
> Try out the attached patch.
With the patch applied I obtained a bare bones mmk test result:
All tests successful, 7 tests and 91 subtests skipped.
Files=38, Tests=633, 239 wallclock secs ( 0.00 cusr + 0.00 csys = 0.00
CPU
Michael G Schwern <[EMAIL PROTECTED]> wrote on 12/29/2004 10:33:02 PM:
> Its also hideously insecure. You're running a shell script that could do
> anything. A problem with any self-extracting archive.
>
> From shar(1).
>
> SECURITY CONSIDERATIONS
> It is easy to insert trojan horses into s
"Craig A. Berry" <[EMAIL PROTECTED]> wrote on 12/29/2004 01:09:58 PM:
> 4.) The following macro is defined and is used in the shdist target:
>
> SHAR = vms_share
>
> There is no such native command as vms_share. If I knew more about the
> intention, I might be able to suggest an alternative.
shar
[EMAIL PROTECTED] wrote on 12/18/2004 08:31:28 AM:
> On VMS V7.3-2, Compaq C S6.5-002, MadGoat Make Utility V3.9-6,
> against perl 5.8.1:
>
> All tests successful, 7 tests and 87 subtests skipped.
> Files=36, Tests=603, 156 wallclock secs ( 0.00 cusr + 0.00 csys = 0.00
> CPU)
>
> Later I'll try
Michael G Schwern <[EMAIL PROTECTED]> wrote on 12/17/2004 09:41:47 PM:
> http://svn.schwern.org/svn/CPAN/ExtUtils-MakeMaker/trunk
> or
> svn://svn.schwern.org/CPAN/ExtUtils-MakeMaker/trunk
> or
> http://www.pobox.com/~schwern/src/ExtUtils-MakeMaker-6.25_01.tar.gz
> or
> a CPAN near you.
>
> Kicked
Michael G Schwern <[EMAIL PROTECTED]> wrote on 11/23/2004 12:00:21 AM:
> Ok, I'm working on MakeMaker again and I'm trying to shove a 6.22 out the
> door. Something that works so the core can update from 6.17.
I am glad to hear that.
> I can't remember what the critical problems were preventing
"H.Merijn Brand" <[EMAIL PROTECTED]> wrote on 11/01/2004 09:57:06 AM:
> On Sat 30 Oct 2004 19:42, "H.Merijn Brand" <[EMAIL PROTECTED]> wrote:
> > On Fri 29 Oct 2004 04:58, Steve Peters <[EMAIL PROTECTED]> wrote:
> > Since I don't know what VMS actually has, and configure.com doesn't
have
> > comm
"Craig A. Berry" <[EMAIL PROTECTED]> wrote on 08/06/2004 03:31:16 PM:
> Not on OpenVMS Alpha 7.2-2. That would only bite you on VAX or on
> pre-7.2 Alpha. The 8-level restriction may have even been lifted on
> VAX in 7.3, but I don't remember for sure.
Yes the 8 limit no longer obtains in r
"John E. Malmberg" <[EMAIL PROTECTED]> wrote on 05/09/2004 11:34:36 PM:
> Craig A. Berry wrote:
> >
> > Read the instructions in README.vms :-).
>
> > . where it will tell you
> >
> > $ @[.vms]test .exe "" -"v" [-.lib.extutils.t]basic.t
> >
> > though the second argument should be "ndbg"
"Dr. Martin P.J. Zinser" <[EMAIL PROTECTED]>
wrote on 04/28/2004 06:56:10 PM:
> subject says it all:-) I am looking for a place to find the VMS::Logicals
> module (vmsbox.cjb.net does not work for me), as well as for information
> on its current status.
You bring up an important topic. The
"John E. Malmberg" <[EMAIL PROTECTED]> wrote on 04/11/2004 11:37:38 PM:
> To bring this list up to date, Craig Berry and I have been discussing
> patches needed to use Perl to build the GTK+ package as part of Mozilla.
Thanks for posting this.
> * Case needs to be preserved.
>Currently P
IvorW <[EMAIL PROTECTED]> wrote on 04/11/2004 05:39:18 PM:
> If you haven't got DECnet running, you can do
>
>$ telnet 0 /log=file
>
> Note that there is no default file name.
>
> Also this probably depends on using TCPIP Services for OpenVMS (UCX)
> as your IP stack, I think that Tcpware
If you have DECnet running on the machine in question one way to
log the output of a @configure "-des" interactive run would be to use:
set host 0/log
and the resulting sethost.log file will contain the full content of the
interactive
session, which you'll be able to view when you logout
[EMAIL PROTECTED] wrote on 04/06/2004 12:01:28 PM:
> I have a pattern matching problem that isn't strictly VMS related
(although I
> amd running on VMS perl).
>
> I want to make a perl regexp that will match an @ starting at the
beginning of
> the string followed by any characters. (Actually I
Indeed there is (a layered PSPA product, but in the DCLTABLES nonetheless).
So I should have recommended:
$ perforc*e == "$disk:[dir]p4.exe"
Or perhaps:
$ pfou*r == "$disk:[dir]p4.exe"
Peter Prymmer
"BAZLEY, Sebastian" <[EMAIL PROTECTED]> wrote on
02/16/2004 08:55:48 AM:
> >-Original
"Craig A. Berry" <[EMAIL PROTECTED]> wrote on 02/12/2004 11:24:54 PM:
> At 4:47 AM -0500 2/7/04, IvorW wrote:
> >
> >This thread has set me thinking, and I am reminded of something that VMS
> >handles rather better than Unix. VMS uses the ellipsis [...] to stand
for
> >"and any directory path
"$PERL_ROOT:[00]PERL.EXE "-MVMS::Filespec" "-MFile::Path"
-e "File::Path::rmtree(unixify(shift))""
that works like so:
$ show default
USER:[PPRYMMER]
$ create/dir [.fluff]
$ copy login.com [.fluff]/log
%COPY-S-COPIED, USER:[PPRYMMER]LOGIN.COM;13 copied
"Craig A. Berry" <[EMAIL PROTECTED]> wrote on 12/06/2003 04:35:12 PM:
> At 2:12 PM -0500 12/6/03, Henderson, Jordan (Contractor) (DAASC) wrote:
>
> >If a f$search-like capability is desired, then a VMS:: module
> should probably be
> >instituted that includes this capability.
>
> Such as Forre
Greetings,
The newish ODS-5 file system type mountable on
VMS may require certain workarounds for building
perl on VMS. The enclosed documentation patch
was mentioned prior to the release of perl 5.8.1 but
too late to make it in:
http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/2003-09/msg00
Here is the tail end of the output of "mmk test":
t/vmsish
ok
t/writemakefile_args
ok
Failed Test Stat Wstat Total Fail Failed List of Failed
---
t/inst_prefix.t 44 1024526 11.54%
"Craig A. Berry" <[EMAIL PROTECTED]> wrote on 12/19/2003 09:19:39 AM:
> Peter wrote:
> > >An impressively small patch. It looks good.
>
> Thanks. It would have been a good bit smaller except for the
> following hardware model on the testdrive system:
>
> $ write sys$output f$getsyi("HW_MODEL"
"Craig A. Berry" <[EMAIL PROTECTED]> wrote on 12/18/2003 07:19:43 PM:
> Earlier today HP released the OpenVMS v8.1 evaluation kit. This is the
> second early adopter's kit of VMS on Itanium but the first one to
> include native compilers. I'm pleased to say that with the attached
> patch to bl
Michael G Schwern <[EMAIL PROTECTED]> wrote on 12/15/2003 07:27:40 PM:
> On Mon, Dec 15, 2003 at 04:52:13PM -0500, [EMAIL PROTECTED] wrote:
> > These test failures are partially due to the "recompile
> > everything" property of generated descrip.mms files
>
> Apply this until I get 6.22 out th
[EMAIL PROTECTED] wrote on 12/15/2003 03:29:21:
> I grabbed the pre 5.8.3 kit mentioned in:
>
>
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2003-12/msg00588.html
>
> compiled with: Compaq C S6.5-002 on OpenVMS Alpha V7.3-1
> and obtained these test failures:
>
> lib/ExtUtils/t/Const
Greetings,
I grabbed the pre 5.8.3 kit mentioned in:
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2003-12/msg00588.html
compiled with: Compaq C S6.5-002 on OpenVMS Alpha V7.3-1
and obtained these test failures:
lib/ExtUtils/t/Constant..FAILED at test 27
lib/ExtUtils/t/
Greetings,
There appears to be a problem that ExtUtils::Install.pm is having
finding .packlist files on VMS as can be seen by this sequence
using VMS 7.3-1, perl 5.8.1,
$ perl "-MExtUtils::MakeMaker" -e "print $ExtUtils::MakeMaker::VERSION"
6.17
$ perl "-MExtUtils::Install" -e "print $ExtUtil
Andy Lester <[EMAIL PROTECTED]> wrote on 12/12/2003 04:17:36 PM:
> > I have been asked to support your WWW::Mechanize module
> > on an installation of perl on a VMS system. I found that despite
>
> I would be glad to get this in there. Would you please be so kind as to
> remail your mail and
Greetings Andy,
I have been asked to support your WWW::Mechanize module
on an installation of perl on a VMS system. I found that despite
the great care that you took specifying files with File::Spec -
I presume so as to be as cross platform as possible - that a few
Unix and Windows shell cons
"Henderson, Jordan (Contractor) (DAASC)" <[EMAIL PROTECTED]> wrote
on 12/06/2003 02:12:36 PM:
> My 2 cents.
>
> I would prefer that glob, being a core function, be as close as possible
in
> semantics between VMS and other systems. This will ease, but not
eliminate
> issues with, portability o
"Craig A. Berry" <[EMAIL PROTECTED]> wrote on 12/06/2003 12:14:51 PM:
> Well, doh, the magic number is (as I should have realized) 127. I
> just had a hard time believing we've never had the result of a glob
> longer than that. Here are the length values we are actually using
> as we approac
"Craig A. Berry" <[EMAIL PROTECTED]> wrote on 11/21/2003 10:28:23 AM:
> You are correct that if you see a test failure in a feature you are
> going to depend on, then it's not the overall score that matters.
> But let's look at the two test failures Saku is reporting. One has
> to do with a t
Greetings Gisle,
When building HTML-Parser-3.34 on VMS 7.3-1
against Perl 5.8.1 I answered 'y' to the following question:
Do you want decoding on unicode entities? [no] y
I then started the make utility but the compilations
died on about three separate "unsigned char" versus
"char" type inc
8.2 either.
Unfortunately I have not had time to trim it down to a small
reproducable test case. Basically a simple script whose wanted()
sub routine prints out $File::Find::name will, when run from my login
directory USER:[PPRYMMER], occasionally jump up and report
finding files from places like user:[otheru
Greetings,
I found that I had to modify the Makefile.PL in the Crypt::SSLeay 0.51
distribution
from CPAN in order to get it built under perl 5.8.1 using Compaq C
S6.5-002.
Enclosed please find a patch to the Makefile.PL as well as to the README
file that mentions platform particulars:
diff -r
"Barry Treahy, Jr." <[EMAIL PROTECTED]> wrote on 09/25/2003 02:16:50 PM:
> This is great news, thank you. I'm new to Perl on VMS, not to Perl in
> general, and I've already completed the 5.8.0 build on a VAX running VMS
> 7.2. The problem I'm running into, appears to be VMS related. For
> ex
"Craig A. Berry" <[EMAIL PROTECTED]> wrote on 09/25/2003 01:27:04 PM:
> We can now say shipped, past tense, which means that your very good
> doc patch is too late for 5.8.1.
Thanks for the announcement (I have been patiently waiting for
5.8.1 :-)
> Hang on there. Since multiple dots in a f
"Craig A. Berry" <[EMAIL PROTECTED]> wrote on 09/25/2003 01:33:52 AM:
> All filenames in the Perl distribution are ODS-2 safe except for the
> name of the top-level directory, whose multiple dots in the portion
> containing the Perl version number cause the problem you note. The
> problem was
It has only recently been reported that
a perl build might have trouble on ODS-5.
Although I recall testing it a few years ago
I suspect things might have changed and I only
recently ran into the problem when extracting
perl-5.8.1-RC5.tar.gz onto an ODS-5
volume (the release kits that unpack in
Configured with:
@configure "-des"
`mmk test` obtained:
All tests successful.
u=118.18 s=0 cu=0 cs=0 scripts=736 tests=75864
This was with:
Compaq C S6.5-002 on OpenVMS Alpha V7.3-1
MadGoat Make Utility V3.9-6
MultiNet V4.4 Rev A-X
ODS-2 Volume.
With the kit's multiple periods in
TCP/IP Services for OpenVMS Alpha Version V5.3 - ECO 2
ODS-5 volume, vms tar V3.4, kit extracted with command:
tar/extract/verbose/date=none user:[pprymmer]perl_21297.tar
where user happened to be an ODS-2 volume.
I have none of the DECC* logical names for ODS-5 in
my environment. I do
Configured with:
@ Configure "-des"
`mmk test` obtained:
All tests successful.
u=39.56 s=0 cu=0 cs=0 scripts=729 tests=75817
Other system specifics:
Compaq C S6.5-002 on OpenVMS Alpha V7.3-1
MadGoat Make Utility V3.9-6
TCP/IP Services for OpenVMS Alpha Version V5.3 - ECO 2
ODS-2 vo
I mentioned to Michael Schwern
recently that I'd look into seeing if we could
support a "test_harness" target in the VMS
build. Enclosed is a patch that provides it
but running:
mmk test_harness
runs into a lot of "spurious" failures
and does not even appear as nice
as running harness by
[EMAIL PROTECTED] wrote on 09/17/2003 01:38:52 PM:
> installation tests not yet completed.
After running `mmk install` for the perl build tree
and [EMAIL PROTECTED] a run of the four line module
installation (on another DISK volume) for Text::CSV_XS
0.23 from CPAN went fine including mmk targe
Configure with:
@configure "-des"
`mmk test` returned:
All tests successful.
u=87.07 s=0 cu=0 cs=0 scripts=736 tests=75854
Compaq C S6.5-002 on OpenVMS Alpha V7.3-1,
MadGoat Make Utility V3.9-6
ODS-2 build volume
installation tests not yet completed.
Peter Prymmer
And in a run configured with:
@ configure "-Dusevmsdebug" "-des"
I obtain:
All tests successful.
u=105.76 s=0 cu=0 cs=0 scripts=734 tests=75780
For what it is worth this may fix the problem of the extraneous files
generated during "mmk test" (I do not know why this problem
affects V
Configured with:
@ Configure "-des"
mmk test results:
All tests successful.
u=97.34 s=0 cu=0 cs=0 scripts=734 tests=75780
The only extraneous files now piling up in my sys$scratch:
directory are these sdbm test files:
MD711367815.SDBM_DIR;1
0 15-SEP-2
ot;> build obtained:
All tests successful.
u=90.1 s=0 cu=0 cs=0 scripts=734 tests=75736
and, having deleted all of the previous SYS$SCRATCH:PERLIO_%%.;*
files I now see only these:
$ dir/since/date/size sys$scratch:
Directory USER:[PPRYMMER]
FILE-SPEC-0_85_01.DIR;1
he tests failed - possible vmspipe.com issue too).
As of this morning I now have three new unwanted files:
$ dir/date/size/since sys$scratch:
Directory S1:[PPRYMMER]
FILE-SPEC-0_85_01.DIR;1
1 12-SEP-2003 09:18:50.66
FILE-SPEC-0_85_01.TAR;1
280
xtUtils/t/basic.FAILED at test 22
lib/ExtUtils/t/Constant..FAILED at test 5
Failed 2 test scripts out of 728, 99.73% okay.
In sum this patch has been tested with:
x86 linux 2.4.18-14smp:
sh Configure -Dprefix=/home/pprymmer/my/miniperl -des
build of Text-CSV_XS 0.23
Martin P.J. Zinser wrote recently:
Hello,
!I am in contact with Hoff about submitting a few entries for the upcoming
!freeware CD. While discussing the feasability of getting some Perl Modules
!on it, we finally came to the conclusion that it would be best to have a
!full Perl Build on the CD
John Peacock wrote in reply to me:
!I had dozens of failures as well the testing itself failing to complete.
I
!wound up running out of diskspace while trying to build a second copy, so
I
!deleted all of the files from the earlier run (include the failed test
logs).
!I'm going to start from sc
John Peacock wrote:
!In my own defense, I normally build/test Perl in my home directory, using
a
!rooted logical. That seemed to be causing problems, so I just tried to do
the
!build in the future home of Perl, which my user doesn't ordinarily have
rights
!to, hence the use of 'set proc' in t
Michael Schwern wrote:
!Oh, I got it backwards.
!
!--- MM_Unix.pm 2 Sep 2003 20:50:02 - 1.186
!+++ MM_Unix.pm 2 Sep 2003 20:50:29 -
!@@ -2324,7 +2324,7 @@
! my $thisperl = $self->canonpath($^X);
! $thisperl .= $Config{exe_ext} unless
!
cript "$_.bat" } @SCRIPTS;
+}
+else {
+@EXE_FILES = map { script $_ } @SCRIPTS;
+}
## The test-script to execute regression tests (note that the
End of possible patch.
Unfortunately I do not know if that patch is correct
for windows. You'd have to check with a wind
Michael Schwern wrote a reply to me:
!Ah ha! That's this logic failing:
!$thisperl .= $Config{exe_ext} unless $thisperl =~
m/$Config{exe_ext}$/i;
!
!Its not expecting the ;1 on the end. It doesn't effect other platforms
!because they don't have those semantics.
That is good.
You also s
Greetings,
The enclosed patch taken w.r.t. [EMAIL PROTECTED] modifies
only the installperl script for use on VMS to:
1. install perl_setup.com into perl_root:[00] always
2. correct problems with the installation of a2p for the
usevmsdebug build
I note that 1. has the tempting a
Michael G. Schwern wrote:
!Its not supposed to fix the core build.
!
!Try installing MM as a CPAN module with that patch against your installed
!ndbgperl. If that works then I know how to fix the core build properly.
I had tried to include an illustration of the inability
to build Pod2VMSHlp
logical name.
The behavior of now favoring return values that are more often
absolute specs makes the behavior more like File::Spec::Win32
which will return values like so when run from cygwin:
$ pwd
/cygdrive/c/Documents and Settings/pprymmer
$ ls ntuser.ini
ntuser.ini
$ perl -MFile::Spec -e '
Greetings,
Enclosed please find a patch to the File::Spec implementation
that shipped with the [EMAIL PROTECTED] pre-5.8.1 release kit.
For me I can now run the test:
perl lib/File/Spec/t/rel2abs2rel.t
after either having issued:
set default DKA200:[USERS.PERL]
Or making use of the USER
Michael G. Schwern wrote last week:
!If MakeMaker isn't finding the perl you ran Makefile.PL with then there's
!a bug in find_perl() for sure.
Indeed. When I first noticed the problem I too started looking at
MM_VMS.pm::find_perl(). Eventually I realized that the $names array
reference deri
tail end of a run of "make test > test.out"
appeared as:
t/x2p/s2p....ok
All tests successful.
u=2.51 s=0.8 cu=201.83 cs=19.82 scripts=759 tests=76371
make[2]: Leaving directory `/home/pprymmer/perl_20760/perl'
make[1]: Leaving directory `/home/pprymm
Here is a fairly clear illustration of the bug:
$ show logical e0
"E0" = "DKA104:[USERS.]" (LNM$SYSTEM_TABLE)
$ show default
E0:[PERL.581RC.PERL_20760_PATCHED_B1]
$ perl "-MFile::Spec" -e "print File::Spec->abs2rel($^X)"
[---.users.perl.581rc.perl_20760_patched_b1]ndbgperl.exe;3
$ perl -
Michael Schwern wrote in response to me:
!I missed your response to this. My answer is: because there's no need
for
!it to be. During the build process we control the name of the perl
!executable. Once perl has been installed, we get the name of the perl
Indeed we do control the name of t
Michael Schwern wrote:
!Do you think it would be hard to add a test_harness target into
!descrip_mms.template? It would help a lot diagnosing the VMS test
failures.
I think it should be possible to add such a target, but I do not have
a working copy yet...
!> lib/ExtUtils/t/basic...
Craig Berry wrote in reply to Michael G. Schwern:
>>There's really no reason it has to use META.yml. I was just being
>>lazy and reusing the existing MANIFEST.
>>
>>Try this simpler patch instead.
>
>Schwern's simpler patch works for me and gets all
>tests passing for 20760 on OpenVMS Alpha 7
1 - 100 of 366 matches
Mail list logo
