5.8.8-dor on cygwin status
Failed Test Stat Wstat Total Fail Failed List of Failed --- ../lib/File/Temp/t/mktemp.t255 65280 98 88.89% 6-9 ../lib/File/Temp/t/object.t255 6528026 42 161.54% 6-26 ../lib/File/Temp/t/security.t 136 46.15% 3 5 7 11-13 ../lib/File/Temp/t/tempfile.t 255 6528022 34 154.55% 6-22 io/tell.t 281 3.57% 28 op/filetest.t 101 10.00% 8 51 tests and 213 subtests skipped. Failed 6/973 test scripts, 99.38% okay. 50/101291 subtests failed, 99.95% okay. -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using Perl 5.6.2, 5.8.6, 5.8.7, 5.9.2 on HP-UX 10.20, 11.00 11.11, AIX 4.3, SuSE 9.2, SuSE 9.3, and cygwin. http://www.cmve.net/~merijn Smoking perl: smokers@perl.org, perl QA: http://qa.perl.org reports to: [EMAIL PROTECTED],perl-qa@perl.org
Re: [EMAIL PROTECTED] Add hard link and V8.2 crtl support to VMS.
On Tue, 20 Sep 2005 01:22:24 -0400, John E. Malmberg [EMAIL PROTECTED] wrote: This patch adds the ability to build Perl on 64 bit VMS V8.2 with support for hard links, and the newer CRTL features. Thanks, All three applied in change #25507 Changes to configure.com: 1. Protect the link operations for the tests from someone aliasing the link command to default for a /DEBUG build. 2. Allow override of the make being chosen. Currently only MMK or MMS are known to work for the build procedure. 3. Three prompts were waiting for input even when no additional prompt operation is selected. With output redirected to a command file, there was no explanation of what was being prompted for. Now no additional prompt mode really has no additional prompts. 4. Remove /00 from UNIX format names of VMS root directories. These should not be there as if they are passed to a C library routine they are an illegal syntax. vmsify() knows to remove these and this is why they usually have not caused problems. 5. Selecting maximal 64 bit mode also enables large file operation. 6. Removed second check for strtoq. 7. Add tests to see if hard links are enabled on the build volume and supported by the version of VMS and if pass enable hard links. 8. Add tests for symbolic link support for future version of VMS, which will only be enabled if large file operation is also enabled. 9. Add VMS 7.3-2 CRTL routines: getgrdid_r, getpgid, getpgrp, getpwnam_r, getpwuid_r, setgrent, ttyname_r, but only on 64 bit VMS 8.2 because I am not able to test the builds on earlier versions. 10. Prep for future support of seteuid, setpgid, setpgrp, seetregid, setreuid, setsid found in 7.3-2. 11. Add support for 64 bit VMS 8.2 fstatvfs and sockpair routine. 12. Add dormant support for _USE_STD_STAT option. Currently the values returned by stat() functions on VMS are not POSIX compliant, and Perl on VMS has some hacks to make it look like they are POSIX compliant. In the future it may be needed to for Perl to use the C library standard stat instead of the VMS hacks. This makes the support easy to add later. 13. Better Posix/UNIX filename support in VMS 8.2 requires using the CRTL provided dirent.h header definition. 14. Optional (and mostly undocumented) method of generating a PERL_SETUP.COM that can be put in a binary distribution kit. Changes to vms/descrip_mms.template: 1. Add support for _USE_STD_STAT option. 2. cleanup of extra.pods was missing from the REALCLEAN target. Changes to x2p/s2p.PL: 1. $0 parameter on VMS could be in unknown case, so it needs to be lower cased to for parameter to work when VMS is in case sensitive or case preserved mode. 2. The link command needs to use the same filename as the fall back copy command. -- H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/) using Perl 5.6.2, 5.8.0, 5.8.5, 5.9.2 on HP-UX 10.20, 11.00 11.11, AIX 4.3 5.2, SuSE 9.2 9.3, and Cygwin. http://www.cmve.net/~merijn Smoking perl: http://www.test-smoke.org,perl QA: http://qa.perl.org reports to: [EMAIL PROTECTED],perl-qa@perl.org
Signature.t failure
Because I installed Test::Pod and Test::Pod::Coverage (requiring a whole
chain of other modules) and Devel::Cover, I also had to install
Module::Signature somewhere along the line, and this causes the 5.8.8 tests
to fail. After reading Module::Signature's docs, I propose the following
patch to blead (and maint):
Failed Test Stat Wstat Total Fail Failed List of Failed
---
../lib/CPAN/t/signature.t11 100.00% 1
53 tests and 207 subtests skipped.
Failed 1/971 test scripts, 99.90% okay. 1/101205 subtests failed, 100.00% okay.
lt09:/pro/3gl/CPAN/perl-5.8.x-dor 108 diff -pu lib/CPAN/t/signature.t{,.new}
--- lib/CPAN/t/signature.t 2003-07-31 22:56:23.0 +0200
+++ lib/CPAN/t/signature.t.new 2005-09-20 09:35:08.0 +0200
@@ -3,7 +3,10 @@
use strict;
print 1..1\n;
-if (!eval { require Module::Signature; 1 }) {
+if (!-s 'SIGNATURE') {
+ print ok 1 # skip - No signature file found\n;
+}
+elsif (!eval { require Module::Signature; 1 }) {
print ok 1 # skip - no Module::Signature found\n;
}
elsif (!eval { require Socket; Socket::inet_aton('pgp.mit.edu') }) {
Exit 1
lt09:/pro/3gl/CPAN/perl-5.8.x-dor 109
--
H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/)
using Perl 5.6.2, 5.8.0, 5.8.5, 5.9.2 on HP-UX 10.20, 11.00 11.11,
AIX 4.3 5.2, SuSE 9.2 9.3, and Cygwin. http://www.cmve.net/~merijn
Smoking perl: http://www.test-smoke.org,perl QA: http://qa.perl.org
reports to: [EMAIL PROTECTED],perl-qa@perl.org
Re: Smoke [5.8.7] 25494 FAIL(m) MSWin32 WinXP/.Net SP2 (x86/2 cpu)
Steve Hay wrote: Automated smoke report for 5.8.7 patch 25494 Mugwump.uk.radan.com: Intel(R) Pentium(R) 4 CPU 3.40GHz(~3391 MHz) (x86/2 cpu) onMSWin32 - WinXP/.Net SP2 using ? unknown cc version smoketime 2 minutes 46 seconds (average 8.300 seconds) Summary: FAIL(m) ..\mg.c(1771) : error C2275: 'STRLEN' : illegal use of this type as an expression ..\mg.c(1771) : error C2146: syntax error : missing ';' before identifier 'n_a' ..\mg.c(1771) : error C2065: 'n_a' : undeclared identifier The above error has since been fixed by 25506, but I now have errors from perlio.c: ..\perlio.c(1005) : warning C4013: 'PERLIO_FUNCS_DECL' undefined; assuming extern returning int ..\perlio.c(1005) : error C2065: 'tab' : undeclared identifier ..\perlio.c(1005) : error C2100: illegal indirection ..\perlio.c(1005) : warning C4047: '=' : 'int ' differs in levels of indirection from 'struct _PerlIO_funcs *' ..\perlio.c(1005) : error C2106: '=' : left operand must be l-value ..\perlio.c(1007) : warning C4047: '=' : 'int ' differs in levels of indirection from 'struct _PerlIO_funcs *' ..\perlio.c(1012) : error C2223: left of '-name' must point to struct/union ..\perlio.c(1013) : error C2223: left of '-name' must point to struct/union ..\perlio.c(1013) : error C2198: 'PerlIO_find_layer' : too few actual parameters ..\perlio.c(1050) : error C2072: 'PERLIO_FUNCS_DECL' : initialization of a function ..\perlio.c(1086) : error C2065: 'osLayer' : undeclared identifier ..\perlio.c(1086) : error C2100: illegal indirection These seem to have been introduced by 25495 -- reverting to 25494 (plus the fix for mg.c above) fixes them. Not sure what its problem with PERLIO_FUNCS_DECL is -- it looks the same as that in blead to me. Radan Computational Ltd. The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.
Re: Problems building 64-bit Perl 5.8.7 on AIX 5.2
On Mon, Sep 19, 2005 at 01:10:00PM -0700, Alan Olsen wrote: I am trying to build Perl 5.8.7 on AIX 5.2. I can build Perl as long as I do not define use 64-bit all. If I try and build a version with full 64-bit support I get the following error somewhere down in the compile: CCCMD = cc_r -DPERL_CORE -c -D_ALL_SOURCE -D_ANSI_C_SOURCE -D_POSIX_SOURCE -qmaxmem =-1 -qnoansialias -DUSE_NATIVE_DLOPEN -DNEED_PTHREAD_INIT -I/usr/local/inclu de -q64 -DUSE_64_BIT_ALL -q64 -O cc_r -brtl -bdynamic -bmaxdata:0x8000 -L/usr/local/lib -q64 -b64 -o miniperl_nonshr miniperlmain.o \ opmini.o libperl_nonshr.a -lbind -lnsl -ldl -lld -lm -lcrypt -lpthreads -lc -lbsd ld: 0711-317 ERROR: Undefined symbol: .flock ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information. make: *** [miniperl_nonshr] Error 8 Any idea what is going on here? I am building with threads, but building without threads gives the same error. Hi, This is actually supposed to work. It might help to know the exact Configure arguments you are using, as well as the compiler version and operating system patch maintenance level. Try oslevel -r to determine the AIX level. There are a number of different compilers around, try something like lslpp -l | grep -i compiler to find out what you have. Regards, -- $_ = Campo Weijerman [rfc822://nl.ibm.com/] and tr-[:]/-@-d and print;
Re: Signature.t failure
H.Merijn Brand wrote:
Because I installed Test::Pod and Test::Pod::Coverage (requiring a whole
chain of other modules) and Devel::Cover, I also had to install
Module::Signature somewhere along the line, and this causes the 5.8.8 tests
to fail. After reading Module::Signature's docs, I propose the following
patch to blead (and maint):
blead hasn't signature.t. I removed it, due to the lack of Module::Signature.
Moreover, the SIGNATURE file is actually there, in lib/CPAN, but not
found because the tests are run from t/.
Failed Test Stat Wstat Total Fail Failed List of Failed
---
../lib/CPAN/t/signature.t11 100.00% 1
53 tests and 207 subtests skipped.
Failed 1/971 test scripts, 99.90% okay. 1/101205 subtests failed, 100.00%
okay.
lt09:/pro/3gl/CPAN/perl-5.8.x-dor 108 diff -pu lib/CPAN/t/signature.t{,.new}
--- lib/CPAN/t/signature.t 2003-07-31 22:56:23.0 +0200
+++ lib/CPAN/t/signature.t.new 2005-09-20 09:35:08.0 +0200
@@ -3,7 +3,10 @@
use strict;
print 1..1\n;
-if (!eval { require Module::Signature; 1 }) {
+if (!-s 'SIGNATURE') {
+ print ok 1 # skip - No signature file found\n;
+}
+elsif (!eval { require Module::Signature; 1 }) {
print ok 1 # skip - no Module::Signature found\n;
}
elsif (!eval { require Socket; Socket::inet_aton('pgp.mit.edu') }) {
Exit 1
lt09:/pro/3gl/CPAN/perl-5.8.x-dor 109
PATCH for #37138: using XSUB as DB::DB causes perl to crash
Hi, the attached patch solves bug #37138, that was causing perl to crash when using an XSUB as DB::DB(). Cheers, - Salvador __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com db_db_xsub-0.patch Description: 2604567955-db_db_xsub-0.patch
[perl #37202] FW: IPC::Open3 failures
# New Ticket Created by [EMAIL PROTECTED] # Please include the string: [perl #37202] # in the subject line of all future correspondence about this issue. # URL: https://rt.perl.org/rt3/Ticket/Display.html?id=37202 #!/bin/perl use strict; use IPC::Open2; # # This fails under Win32 when input redirection is in effect, # for example tstopen2.pl NUL: # my $child_pid = open2(\*CMD_OUT, \*CMD_IN, ipconfig); # When the above execute, you get this error: # open2: Can't call method close on an undefined value at # C:/Perl/lib/IPC/Open3.pm line 341. # # # On the other hand, this works: # # use IPC::Open3; # my $child_pid = open3(\*CMD_IN, \*CMD_OUT, \*CMD_ERR, ipconfig); -Original Message- From: Nicholas Clark [mailto:[EMAIL PROTECTED] On Behalf Of Nicholas Clark Sent: Saturday, September 17, 2005 6:11 PM To: Denton, Sam Subject: Re: IPC::Open3 failures On Sat, Sep 17, 2005 at 05:37:41PM -0400, [EMAIL PROTECTED] wrote: I can consistently get this error: C:\tools\ECSCDC_DMX_Hosts.pl -a reveal -h w2pf -s 40 0NUL: open2: Can't call method close on an undefined value at D:/Perl/lib/IPC/Open3.pm line 341. Everything works OK if stdin isn't redirected, but it fails on all re-directions. Adding a test for the value being defined fixes the problem, but I'm unsure why the value isn't defined. Can you reduce this down to a small script that you can send to [EMAIL PROTECTED], the address for reporting core perl bugs to all the developers. Personally I have no Windows experience, and IPC::Open3 is very platform dependent, so I'm not able to help you further on this. Nicholas Clark
Re: PATCH for #37138: using XSUB as DB::DB causes perl to crash
Salvador FandiXo wrote:
the attached patch solves bug #37138, that was causing perl to crash
when using an XSUB as DB::DB().
Thanks. Your patch is suitable for maintperl; I modified it as follows for
bleadperl :
Change 25511 by [EMAIL PROTECTED] on 2005/09/20 09:02:17
Subject: PATCH for #37138: using XSUB as DB::DB causes perl to crash
From: Salvador FandiXo [EMAIL PROTECTED]
Date: Mon, 19 Sep 2005 06:56:39 -0700 (PDT)
Message-ID: [EMAIL PROTECTED]
(adapted to bleadperl)
Affected files ...
... //depot/perl/pp_ctl.c#479 edit
Differences ...
//depot/perl/pp_ctl.c#479 (text)
@@ -1771,13 +1771,24 @@
hasargs = 0;
SPAGAIN;
- PUSHBLOCK(cx, CXt_SUB, SP);
- PUSHSUB_DB(cx);
- cx-blk_sub.retop = PL_op-op_next;
- CvDEPTH(cv)++;
- SAVECOMPPAD();
- PAD_SET_CUR_NOSAVE(CvPADLIST(cv), 1);
- RETURNOP(CvSTART(cv));
+ if (CvXSUB(cv)) {
+ CvDEPTH(cv)++;
+ PUSHMARK(SP);
+ (void)(*CvXSUB(cv))(aTHX_ cv);
+ CvDEPTH(cv)--;
+ FREETMPS;
+ LEAVE;
+ return NORMAL;
+ }
+ else {
+ PUSHBLOCK(cx, CXt_SUB, SP);
+ PUSHSUB_DB(cx);
+ cx-blk_sub.retop = PL_op-op_next;
+ CvDEPTH(cv)++;
+ SAVECOMPPAD();
+ PAD_SET_CUR_NOSAVE(CvPADLIST(cv), 1);
+ RETURNOP(CvSTART(cv));
+ }
}
else
return NORMAL;
Re: BUG: MAKEMAKER 6.30_01 and blead in MM_UNIX.pm for VMS
Michael G Schwern [EMAIL PROTECTED] wrote on 09/19/2005 08:15:51 PM: On Sun, Sep 18, 2005 at 11:52:20PM -0400, John E. Malmberg wrote: As there is no false command on VMS, this is causing rerunning a make to fail. Would adding the following line before the return $m be the fix for this? Or is something else needed to make sure only the last line is removed? $m =~ s/false\n// if $IsVMS; I see a number of uses of false in MM_Unix. Rather than throw in more VMS exceptions (blech) I'll make a $(FALSE) which can be something safe like perl -e 'exit 1' On VMS the construct shown is true since exit 1 is the way to say exit 0. I note the following behavior from the shell on Solaris 10: /home/user/pprymmer false /home/user/pprymmer echo $? 255 Hence you may want to use something like 44 on VMS (noting that a message will be generated): $ perl -e exit 44 %SYSTEM-F-ABORT, abort the non portability of exit values is discussed in perlport.pod. Peter Prymmer
Re: [PATCH blead] Re: [perl #36733] %SIG not properly local-ized
Rick Delaney wrote: This is a bug report for perl from [EMAIL PROTECTED], generated with the help of perlbug 1.35 running under perl v5.8.6. - The construct local %SIG = %SIG; does *not* make an exact local copy of %SIG, as it should. Please look at the following patch. I really don't understand what needs_store is for but keeping it TRUE for %SIG seems to fix this. Anyway, the tests should be good. Thanks, applied as #25515 (although I made the hv.c chunk a bit nicer.)
Re: BUG: MAKEMAKER 6.30_01 and blead in MM_UNIX.pm for VMS
Peter Prymmer wrote: Michael G Schwern [EMAIL PROTECTED] wrote on 09/19/2005 08:15:51 PM: On Sun, Sep 18, 2005 at 11:52:20PM -0400, John E. Malmberg wrote: As there is no false command on VMS, this is causing rerunning a make to fail. I see a number of uses of false in MM_Unix. Rather than throw in more VMS exceptions (blech) I'll make a $(FALSE) which can be something safe like perl -e 'exit 1' On VMS the construct shown is true since exit 1 is the way to say exit 0. I note the following behavior from the shell on Solaris 10: /home/user/pprymmer false /home/user/pprymmer echo $? 255 Hence you may want to use something like 44 on VMS (noting that a message will be generated): $ perl -e exit 44 %SYSTEM-F-ABORT, abort the non portability of exit values is discussed in perlport.pod. A VMS exit 44 will also cause MMS/MMK by default to abort the makefile with MMS/MMK also exiting with an error. If you want a VMS exit code that UNIX programs should interpret as an EXIT 1, then the following (mostly undocumented) hack will work. VMS status code = %x35a000 + (UNIX status * 8), and if this is a success status, add 1, otherwise VMS will interpret it as a warning. EAGLE exit %x35A000 + (1 * 8) + 1 EAGLE x = %x35A000 + (1 * 8) + 1 EAGLE show sym x X = 3514377 Hex = 0035A009 Octal = 00015320011 As of blead-perl, Perl is now automatically translating this code to the expected internal UNIXish status correctly. I think I will have to look at perlport.pod to make sure it is current. I suspect it is not. -John [EMAIL PROTECTED] Personal Opinion Only
Re: [perl #37110] compiling perl 5.8.7 for win32 using free microsoft tools
Steve Hay via RT schrieb: [shay - Mon Sep 19 03:31:42 2005]: OK, I'll do something about updating those links. I've updated the README.win32 in the current development version of Perl. This file can be seen at: http://public.activestate.com/cgi-bin/perlbrowse?file=README.win32rev= Is the delayimp.lib problem resolved now? If so, I'll close this ticket. Yes, please close the ticket. Many thanks for your help. Best regards, Werner
Re: Transliteration operator(tr//)on EBCDIC platform
Hi Sadahiro
All the existing test suite passes. But there are couple of new tests
failing probably due to multibyte representation \x{1000} which is
represented in three byte sequence in EBCDIC . These two tests are
$c = ($a = \x89\x8a\x8b\x8c\x8d\x8f\x90\x91) =~ tr/\x{1000}\x89-\x91/X/;
is($c, 8);
is($a, );
$c = ($a = \xc9\xca\xcb\xcc\xcd\xcf\xd0\xd1) =~ tr/\x{1000}\xc9-\xd1/X/;
is($c, 8);
is($a, );
The output is:
not ok 1
# Failed at t/op/tr_new.t line 32
# got '6'
# expected '8'
not ok 2
# Failed at t/op/tr_new.t line 33
# got 'XXXðýXXX'
# expected ''
not ok 3
# Failed at t/op/tr_new.t line 36
# got '4'
# expected '8'
not ok 4
# Failed at t/op/tr_new.t line 37
# got 'XXôöòõXX'
# expected ''
One observation is that since this unicode appears first in the tr//
as there seemed a problem in \x{100} case, Seems like it doesn't
handle the multibyte (2)
regards
Sastry
On 9/19/05, SADAHIRO Tomoyuki [EMAIL PROTECTED] wrote:
On Thu, 15 Sep 2005 18:31:43 +0530, Sastry [EMAIL PROTECTED] wrote
Hi Sadahiro
Having incorporated the changes in the doop.c and op.c
I strangely get lots of failures and here are the test results. Seems
like the first approach itself fails on tr// and there will certainly
more failures when we run the entire test suite which uses these
functions.
In the second approach, the change seems to be
affecting only tr// . Please let me know your suggestions for the
changes which I can apply in S_scan_const() and see if it works.
regards
Sastry
Here it is.
All newer codes in toke.t are enclosed between #ifdef EBCDIC
and #endif since they are redundant for ASCII platform.
And I add some tests to tr.t.
Regards,
SADAHIRO Tomoyuki
! toke.t t/op/tr.t
diff -ur [EMAIL PROTECTED]/t/op/tr.t [EMAIL PROTECTED]/t/op/tr.t
--- [EMAIL PROTECTED]/t/op/tr.tThu Aug 18 18:27:25 2005
+++ [EMAIL PROTECTED]/t/op/tr.t Sun Sep 18 19:59:13 2005
@@ -6,7 +6,7 @@
require './test.pl';
}
-plan tests = 100;
+plan tests = 120;
my $Is_EBCDIC = (ord('i') == 0x89 ord('J') == 0xd1);
@@ -259,7 +259,6 @@
# UTF8 range tests from Inaba Hiroto
-# Not working in EBCDIC as of 12674.
($a = v300.196.172.302.197.172) =~ tr/\x{12c}-\x{130}/\xc0-\xc4/;
is($a, v192.196.172.194.197.172,'UTF range');
@@ -272,6 +271,15 @@
($a = \x{0100}) =~ tr/\x00-\x{100}/X/;
is($a, X);
+($a = \x{0100}) =~ tr/\x00-\x{101}/X/;
+is($a, X);
+
+($a = \x{0100}\x{0101}) =~ tr/\x00-\x{102}/X/;
+is($a, XX);
+
+($a = \x{0101}\x{0102}) =~ tr/\x00-\x{103}/X/;
+is($a, XX);
+
($a = \x{0100}) =~ tr/\x{}-\x{00ff}/X/c;
is($a, X);
@@ -303,8 +311,16 @@
is($c, 8);
is($a, );
+$c = ($a = \x89\x8a\x8b\x8c\x8d\x8f\x90\x91) =~ tr/\x{1000}\x89-\x91/X/;
+is($c, 8);
+is($a, );
+
+$c = ($a = \xc9\xca\xcb\xcc\xcd\xcf\xd0\xd1) =~ tr/\x{1000}\xc9-\xd1/X/;
+is($c, 8);
+is($a, );
+
SKIP: {
-skip not EBCDIC, 4 unless $Is_EBCDIC;
+skip not EBCDIC, 12 unless $Is_EBCDIC;
$c = ($a = \x89\x8a\x8b\x8c\x8d\x8f\x90\x91) =~ tr/i-j/X/;
is($c, 2);
@@ -313,7 +329,38 @@
$c = ($a = \xc9\xca\xcb\xcc\xcd\xcf\xd0\xd1) =~ tr/I-J/X/;
is($c, 2);
is($a, X\xca\xcb\xcc\xcd\xcf\xd0X);
+
+$c = ($a = \x89\x8a\x8b\x8c\x8d\x8f\x90\x91) =~ tr/\x{1000}i-j/X/;
+is($c, 2);
+is($a, X\x8a\x8b\x8c\x8d\x8f\x90X);
+
+$c = ($a = \xc9\xca\xcb\xcc\xcd\xcf\xd0\xd1) =~ tr/\x{1000}I-J/X/;
+is($c, 2);
+is($a, X\xca\xcb\xcc\xcd\xcf\xd0X);
+
+$c = ($a = \x89\x8a\x8b\x8c\x8d\x8f\x90\x91) =~ tr/i-j\x{1000}/X/;
+is($c, 2);
+is($a, X\x8a\x8b\x8c\x8d\x8f\x90X);
+
+$c = ($a = \xc9\xca\xcb\xcc\xcd\xcf\xd0\xd1) =~ tr/I-J\x{1000}/X/;
+is($c, 2);
+is($a, X\xca\xcb\xcc\xcd\xcf\xd0X);
}
+
+($a = \xfc\xfd\xfe\xff) =~ tr/\x00-\xff/X/;
+is($a, );
+
+($a = \xfc\xfd\xfe\xff) =~ tr/\x{1000}\x00-\xff/X/;
+is($a, );
+
+($a = \xfc\xfd\xfe\xff\x{100}) =~ tr/\x{1000}\x00-\x{100}/X/;
+is($a, X);
+
+($a = \xfc\xfd\xfe\xff\x{100}) =~ tr/\x00-\x{200}/X/;
+is($a, X);
+
+($a = \xfc\xfd\xfe\xff\x{100}) =~ tr/\x{1000}\x00-\xff/X/c;
+is($a, \xfc\xfd\xfe\xffX);
($a = \x{100}) =~ tr/\x00-\xff/X/c;
is(ord($a), ord(X));
diff -ur [EMAIL PROTECTED]/toke.c [EMAIL PROTECTED]/toke.c
--- [EMAIL PROTECTED]/toke.c Wed Sep 14 17:40:19 2005
+++ [EMAIL PROTECTED]/toke.c Mon Sep 19 12:05:41 2005
@@ -1407,6 +1407,7 @@
UV uv;
#ifdef EBCDIC
UV literal_endpoint = 0;
+bool native_range = TRUE; /* turned to FALSE if the first endpoint is
Unicode */
#endif
const char *leaveit = /* set of acceptably-backslashed characters */
@@ -1429,8 +1430,14 @@
I32 i; /* current expanded character
*/
I32 min;/* first character in range */
I32 max;/* last character in range */
-
Re: Transliteration operator(tr//)on EBCDIC platform
On Tue, 20 Sep 2005 15:51:34 +0530, Sastry [EMAIL PROTECTED] wrote
Hi Sadahiro
All the existing test suite passes. But there are couple of new tests
failing probably due to multibyte representation \x{1000} which is
represented in three byte sequence in EBCDIC . These two tests are
$c = ($a = \x89\x8a\x8b\x8c\x8d\x8f\x90\x91) =~ tr/\x{1000}\x89-\x91/X/;
is($c, 8);
is($a, );
$c = ($a = \xc9\xca\xcb\xcc\xcd\xcf\xd0\xd1) =~ tr/\x{1000}\xc9-\xd1/X/;
is($c, 8);
is($a, );
The output is:
not ok 1
# Failed at t/op/tr_new.t line 32
# got '6'
# expected '8'
not ok 2
# Failed at t/op/tr_new.t line 33
# got 'XXXðýXXX'
# expected ''
not ok 3
# Failed at t/op/tr_new.t line 36
# got '4'
# expected '8'
not ok 4
# Failed at t/op/tr_new.t line 37
# got 'XXôöòõXX'
# expected ''
One observation is that since this unicode appears first in the tr//
as there seemed a problem in \x{100} case, Seems like it doesn't
handle the multibyte (2)
regards
Sastry
This newer patch uses NATIVE_TO_ASCII(i) instead of
NATIVE_TO_UTF(i). This is only thing which I found being wrong
about the prev patch; but your result seems different from my
expectation about how the output will be with NATIVE_TO_UTF(i)
in the prev patch...
If newer patch is still wrong, would you set DEBUG
in lib/utf8_heavy.pl to be true (that is to replace the line 5
sub DEBUG () { 0 }
to
sub DEBUG () { 1 }
and run it again? Then many verbose info will be out.
Regards,
SADAHIRO Tomoyuki
diff -ur [EMAIL PROTECTED]/t/op/tr.t perl/t/op/tr.t
--- [EMAIL PROTECTED]/t/op/tr.t Thu Aug 18 18:27:25 2005
+++ perl/t/op/tr.t Sun Sep 18 19:59:13 2005
@@ -6,7 +6,7 @@
require './test.pl';
}
-plan tests = 100;
+plan tests = 120;
my $Is_EBCDIC = (ord('i') == 0x89 ord('J') == 0xd1);
@@ -259,7 +259,6 @@
# UTF8 range tests from Inaba Hiroto
-# Not working in EBCDIC as of 12674.
($a = v300.196.172.302.197.172) =~ tr/\x{12c}-\x{130}/\xc0-\xc4/;
is($a, v192.196.172.194.197.172,'UTF range');
@@ -272,6 +271,15 @@
($a = \x{0100}) =~ tr/\x00-\x{100}/X/;
is($a, X);
+($a = \x{0100}) =~ tr/\x00-\x{101}/X/;
+is($a, X);
+
+($a = \x{0100}\x{0101}) =~ tr/\x00-\x{102}/X/;
+is($a, XX);
+
+($a = \x{0101}\x{0102}) =~ tr/\x00-\x{103}/X/;
+is($a, XX);
+
($a = \x{0100}) =~ tr/\x{}-\x{00ff}/X/c;
is($a, X);
@@ -303,8 +311,16 @@
is($c, 8);
is($a, );
+$c = ($a = \x89\x8a\x8b\x8c\x8d\x8f\x90\x91) =~ tr/\x{1000}\x89-\x91/X/;
+is($c, 8);
+is($a, );
+
+$c = ($a = \xc9\xca\xcb\xcc\xcd\xcf\xd0\xd1) =~ tr/\x{1000}\xc9-\xd1/X/;
+is($c, 8);
+is($a, );
+
SKIP: {
-skip not EBCDIC, 4 unless $Is_EBCDIC;
+skip not EBCDIC, 12 unless $Is_EBCDIC;
$c = ($a = \x89\x8a\x8b\x8c\x8d\x8f\x90\x91) =~ tr/i-j/X/;
is($c, 2);
@@ -313,7 +329,38 @@
$c = ($a = \xc9\xca\xcb\xcc\xcd\xcf\xd0\xd1) =~ tr/I-J/X/;
is($c, 2);
is($a, X\xca\xcb\xcc\xcd\xcf\xd0X);
+
+$c = ($a = \x89\x8a\x8b\x8c\x8d\x8f\x90\x91) =~ tr/\x{1000}i-j/X/;
+is($c, 2);
+is($a, X\x8a\x8b\x8c\x8d\x8f\x90X);
+
+$c = ($a = \xc9\xca\xcb\xcc\xcd\xcf\xd0\xd1) =~ tr/\x{1000}I-J/X/;
+is($c, 2);
+is($a, X\xca\xcb\xcc\xcd\xcf\xd0X);
+
+$c = ($a = \x89\x8a\x8b\x8c\x8d\x8f\x90\x91) =~ tr/i-j\x{1000}/X/;
+is($c, 2);
+is($a, X\x8a\x8b\x8c\x8d\x8f\x90X);
+
+$c = ($a = \xc9\xca\xcb\xcc\xcd\xcf\xd0\xd1) =~ tr/I-J\x{1000}/X/;
+is($c, 2);
+is($a, X\xca\xcb\xcc\xcd\xcf\xd0X);
}
+
+($a = \xfc\xfd\xfe\xff) =~ tr/\x00-\xff/X/;
+is($a, );
+
+($a = \xfc\xfd\xfe\xff) =~ tr/\x{1000}\x00-\xff/X/;
+is($a, );
+
+($a = \xfc\xfd\xfe\xff\x{100}) =~ tr/\x{1000}\x00-\x{100}/X/;
+is($a, X);
+
+($a = \xfc\xfd\xfe\xff\x{100}) =~ tr/\x00-\x{200}/X/;
+is($a, X);
+
+($a = \xfc\xfd\xfe\xff\x{100}) =~ tr/\x{1000}\x00-\xff/X/c;
+is($a, \xfc\xfd\xfe\xffX);
($a = \x{100}) =~ tr/\x00-\xff/X/c;
is(ord($a), ord(X));
diff -ur [EMAIL PROTECTED]/toke.c perl/toke.c
--- [EMAIL PROTECTED]/toke.cWed Sep 14 17:40:19 2005
+++ perl/toke.c Tue Sep 20 23:09:13 2005
@@ -1407,6 +1407,7 @@
UV uv;
#ifdef EBCDIC
UV literal_endpoint = 0;
+bool native_range = TRUE; /* turned to FALSE if the first endpoint is
Unicode */
#endif
const char *leaveit = /* set of acceptably-backslashed characters */
@@ -1429,8 +1430,14 @@
I32 i; /* current expanded character */
I32 min;/* first character in range */
I32 max;/* last character in range */
-
- if (has_utf8) {
+#ifdef EBCDIC
+ UV uvmax = 0; /* last character above byte */
+#endif
+ if (has_utf8
+#ifdef EBCDIC
+!native_range
+#endif
+ ) {
char * const c = (char*)utf8_hop((U8*)d, -1);
char *e = d++;
while (e-- c)
@@ -1443,12
Re: Upgrade MakeMaker in maint
On Mon, Sep 19, 2005 at 05:56:50PM -0700, Michael G Schwern wrote: Maint is still using MakeMaker 6.17 which is now TWO YEARS OLD! Last I checked there was some VMS failure or another possibly tied to File::Find but I don't have details. I really rather 5.8.8 not go out with 6.17 again, 6.30 is good and stable. Can we just take the plunge, put 6.30 into maintperl and work out the glitches? The last thing that I remember was that there was some fun with make distclean on VMS in blead and SDBM_File. Or at least something with SDBM_File I was going to look last week to see if you're most recent version had cured it, but it was the day after testdrive went down for 2 weeks. Is the current version happy on VMS with SDBM_File? Nicholas Clark
Re: BUG: MAKEMAKER 6.30_01 and blead in MM_UNIX.pm for VMS
On Tue, Sep 20, 2005 at 07:15:41AM -0400, Peter Prymmer wrote: perl -e 'exit 1' On VMS the construct shown is true since exit 1 is the way to say exit 0. I thought this only happens with use vmsish 'exit' on. I note the following behavior from the shell on Solaris 10: /home/user/pprymmer false /home/user/pprymmer echo $? 255 Solaris is Weird. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Don't try the paranormal until you know what's normal. -- Lords and Ladies by Terry Prachett
Re: BUG: MAKEMAKER 6.30_01 and blead in MM_UNIX.pm for VMS
On Tue, Sep 20, 2005 at 08:09:56AM -0400, John E. Malmberg wrote: A VMS exit 44 will also cause MMS/MMK by default to abort the makefile with MMS/MMK also exiting with an error. I believe this is the desired behavior. If you want a VMS exit code that UNIX programs should interpret as an EXIT 1, then the following (mostly undocumented) hack will work. VMS status code = %x35a000 + (UNIX status * 8), and if this is a success status, add 1, otherwise VMS will interpret it as a warning. EAGLE exit %x35A000 + (1 * 8) + 1 EAGLE x = %x35A000 + (1 * 8) + 1 EAGLE show sym x X = 3514377 Hex = 0035A009 Octal = 00015320011 I have no idea what any of this means. Anyhow, I don't need to wedge together a single command line for both VMS and Unix. Its easy to have different commands for each. Unless you're talking about that wacky VMS with Unix semantics thing again. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern ...they shared one last kiss that left a bitter yet sweet taste in her mouth--kind of like throwing up after eating a junior mint. -- Dishonorable Mention, 2005 Bulwer-Lytton Fiction Contest by Tami Farmer
Smoke [5.8.7] 25521 FAIL(M) MSWin32 WinXP/.Net SP2 (x86/2 cpu)
Automated smoke report for 5.8.7 patch 25521 Mugwump.uk.radan.com: Intel(R) Pentium(R) 4 CPU 3.40GHz(~3391 MHz) (x86/2 cpu) onMSWin32 - WinXP/.Net SP2 using cl version 12.00.8804 smoketime 30 minutes 25 seconds (average 1 minute 31.250 seconds) Summary: FAIL(M) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = make test-prep 25521 Configuration (common) -DINST_TOP=$(INST_DRV)\Smoke\doesntexist --- - M M M M -Dusemymalloc M M -Duselargefiles M M -Duselargefiles -Dusemymalloc M M -Duseithreads -Uuseimpsys M M -Duseithreads -Uuseimpsys -Dusemymalloc M M -Duseithreads -Uuseimpsys -Duselargefiles M M -Duseithreads -Uuseimpsys -Duselargefiles -Dusemymalloc M M -Duseithreads M M -Duseithreads -Duselargefiles | +- -DDEBUGGING +--- no debugging Locally applied patches: MAINT24637 Compiler messages(MSWin32): ..\doio.c(1736) : warning C4090: 'function' : different 'const' qualifiers ..\doio.c(1736) : warning C4024: 'Perl_whichsig' : different types for formal and actual parameter 2 ..\dump.c(68) : warning C4090: 'function' : different 'const' qualifiers ..\dump.c(68) : warning C4024: 'Perl_dump_sub' : different types for formal and actual parameter 2 ..\dump.c(70) : warning C4090: 'function' : different 'const' qualifiers ..\dump.c(70) : warning C4024: 'Perl_dump_form' : different types for formal and actual parameter 2 ..\dump.c(73) : warning C4090: 'function' : different 'const' qualifiers ..\dump.c(73) : warning C4024: 'Perl_dump_packsubs' : different types for formal and actual parameter 2 ..\dump.c(303) : warning C4090: 'function' : different 'const' qualifiers ..\dump.c(303) : warning C4024: 'Perl_pv_display' : different types for formal and actual parameter 3 ..\dump.c(304) : warning C4090: 'function' : different 'const' qualifiers ..\dump.c(304) : warning C4024: 'Perl_pv_display' : different types for formal and actual parameter 3 ..\dump.c(1184) : warning C4090: 'function' : different 'const' qualifiers ..\dump.c(1184) : warning C4024: 'Perl_pv_display' : different types for formal and actual parameter 3 ..\dump.c(1185) : warning C4090: 'function' : different 'const' qualifiers ..\dump.c(1185) : warning C4024: 'Perl_pv_display' : different types for formal and actual parameter 3 ..\dump.c(1323) : warning C4090: 'function' : different 'const' qualifiers ..\dump.c(1323) : warning C4024: 'Perl_pv_display' : different types for formal and actual parameter 3 ..\gv.c(736) : warning C4090: 'function' : different 'const' qualifiers ..\gv.c(736) : warning C4024: 'Perl_is_utf8_idcont' : different types for formal and actual parameter 2 ..\gv.c(736) : warning C4024: 'Perl_is_utf8_digit' : different types for formal and actual parameter 2 ..\locale.c(535) : warning C4090: 'function' : different 'const' qualifiers ..\locale.c(535) : warning C4024: 'Perl_parse_unicode_opts' : different types for formal and actual parameter 2 ..\op.c(196) : warning C4090: 'function' : different 'const' qualifiers ..\op.c(196) : warning C4024: 'Perl_custom_op_desc' : different types for formal and actual parameter 2 ..\op.c(2456) : warning C4090: 'function' : different 'const' qualifiers ..\op.c(2456) : warning C4024: 'Perl_bytes_to_utf8' : different types for formal and actual parameter 2 ..\op.c(2461) : warning C4090: 'function' : different 'const' qualifiers ..\op.c(2461) : warning C4024: 'Perl_bytes_to_utf8' : different types for formal and actual parameter 2 ..\op.c(2479) : warning C4090: 'function' : different 'const' qualifiers ..\op.c(2479) : warning C4024: 'Perl_utf8n_to_uvuni' : different types for formal and actual parameter 2 ..\op.c(2483) : warning C4090: 'function' : different 'const' qualifiers ..\op.c(2483) : warning C4024: 'Perl_utf8n_to_uvuni' : different types for formal and actual parameter 2 ..\op.c(2537) : warning C4090: 'function' : different 'const' qualifiers ..\op.c(2537) : warning C4024: 'Perl_utf8n_to_uvuni' : different types for formal and actual parameter 2 ..\op.c(2541) : warning C4090: 'function' : different 'const' qualifiers ..\op.c(2541) : warning C4024: 'Perl_utf8n_to_uvuni' : different types for formal and actual parameter 2 ..\op.c(2551) : warning C4090: 'function' : different 'const' qualifiers ..\op.c(2551) : warning C4024: 'Perl_utf8n_to_uvuni' : different types for formal and actual parameter 2 ..\op.c(2555) : warning C4090: 'function' : different 'const' qualifiers ..\op.c(2555) : warning C4024: 'Perl_utf8n_to_uvuni' : different types for formal and actual parameter 2 ..\op.c(4251) : warning C4090: 'function' : different 'const' qualifiers ..\op.c(4251) : warning C4024:
Re: BUG: MAKEMAKER 6.30_01 and blead in MM_UNIX.pm for VMS
Michael G Schwern [EMAIL PROTECTED] wrote on 09/20/2005 01:12:51 PM: On Tue, Sep 20, 2005 at 07:15:41AM -0400, Peter Prymmer wrote: perl -e 'exit 1' On VMS the construct shown is true since exit 1 is the way to say exit 0. I thought this only happens with use vmsish 'exit' on. Oh yes. I am sorry. Cperl -e 'exit 1' on Unix and Cperl -e exit 1 on VMS may give you what you want (below I'll ask why you want it). I note the following behavior from the shell on Solaris 10: /home/user/pprymmer false /home/user/pprymmer echo $? 255 Solaris is Weird. Indeed. By the way, why is `false` desirable to have in a Makefile? Why does MakeMaker need to know how to do it? Thanks. Peter Prymmer
Re: oddity in op.c
On Mon, Sep 19, 2005 at 11:31:19PM +0100, Nicholas Clark wrote:
Merijn notices this line in 5.8.x in S_new_logop
if ((type == OP_AND) == (SvTRUE(((SVOP*)first)-op_sv))) {
It's wonky. It seems to be wrong. But it's been that way since 5.8.0 started.
The corresponding point in blead is
if ((type == OP_AND SvTRUE(((SVOP*)first)-op_sv)) ||
(type == OP_OR !SvTRUE(((SVOP*)first)-op_sv)) ||
(type == OP_DOR !SvOK(((SVOP*)first)-op_sv))) {
This was patched by Marcus Holland-Moritz, changing that == to in the
process:
http://public.activestate.com/cgi-bin/perlbrowse?patch=22625
Presumably '==' is wrong. But if this is a bug, how can it be detected
with a perl level regression test?
== is correct; if both operands are 0 or 1, a == b is equivalent
to !(a ^ b) is equivalent to !(a !b || !a b) is equivlent to
a b || !a !b.
[PATCH] licensing terms for perlglossary.pod
Tim O'Reilly says we can say: --- perl/pod/perlglossary.pod.orig 2005-09-20 11:22:31.480172800 -0700 +++ perl/pod/perlglossary.pod 2005-09-20 11:24:18.453993600 -0700 @@ -3380,4 +3380,4 @@ Based on the Glossary of Programming Perl, Third Edition, by Larry Wall, Tom Christiansen Jon Orwant. Copyright (c) 2000, 1996, 1991 O'Reilly Media, Inc. -Used with permission. +This document may be distributed under the same terms as Perl itself.
Re: BUG: MAKEMAKER 6.30_01 and blead in MM_UNIX.pm for VMS
Michael G Schwern wrote: On Tue, Sep 20, 2005 at 08:09:56AM -0400, John E. Malmberg wrote: A VMS exit 44 will also cause MMS/MMK by default to abort the makefile with MMS/MMK also exiting with an error. I believe this is the desired behavior. I think I should test that out tonight by aliasing the false command to signal a 44 status and see what happens. Somehow I have a feeling that it will cause the entire cleanup operation to be aborted before it completes as the failure code gets signaled back through to the parent processes. Exit codes on VMS are signals, not just status conditions, and they can have side effects unless they are trapped or suppressed by the shell. Having the false command signal a SUCCESS status seems to be working in that the REALCLEAN target works. I have not tried the DISTCLEAN target. If you want a VMS exit code that UNIX programs should interpret as an EXIT 1, then the following (mostly undocumented) hack will work. VMS status code = %x35a000 + (UNIX status * 8), and if this is a success status, add 1, otherwise VMS will interpret it as a warning. EAGLE exit %x35A000 + (1 * 8) + 1 EAGLE x = %x35A000 + (1 * 8) + 1 EAGLE show sym x X = 3514377 Hex = 0035A009 Octal = 00015320011 I have no idea what any of this means. Neither would most VMS programmers, which is why their programs written in C sometimes have random weird side effects. Most of the time they get away with it, and many times the error handling in the DCL shell must be suppressed while those programs are running. The above is a bit ugly. And it is not properly documented either, which is why I probably need to look at what perlport.pod is saying about VMS exit values. Back when the C language was added to VMS, there were a few things that were mis-understood about mapping UNIX concepts to VMS concepts, and this is an example of one of them. -John [EMAIL PROTECTED] Personal Opinion Only
Re: oddity in op.c
what's OP_DOR?
Re: oddity in op.c
On 9/20/05, David Nicol [EMAIL PROTECTED] wrote: what's OP_DOR? //
Re: [PATCH] licensing terms for perlglossary.pod
On 9/20/05, Yitzchak Scott-Thoennes [EMAIL PROTECTED] wrote: Tim O'Reilly says we can say: Woot. Where ? --- perl/pod/perlglossary.pod.orig 2005-09-20 11:22:31.480172800 -0700 +++ perl/pod/perlglossary.pod 2005-09-20 11:24:18.453993600 -0700 @@ -3380,4 +3380,4 @@ Based on the Glossary of Programming Perl, Third Edition, by Larry Wall, Tom Christiansen Jon Orwant. Copyright (c) 2000, 1996, 1991 O'Reilly Media, Inc. -Used with permission. +This document may be distributed under the same terms as Perl itself.
Re: oddity in op.c
On 9/20/05, Rafael Garcia-Suarez [EMAIL PROTECTED] wrote:
On 9/20/05, David Nicol [EMAIL PROTECTED] wrote:
what's OP_DOR?
//
Now that defined-or has an opcode, is
if(defined(EXPR)){...
optimized to use it instead of calling OP_DEFINED?
--
David L Nicol
Abkey, deafghee, jekyll
minopker stoov wixes! -- Big Bird, 1973
Re: oddity in op.c
On 9/20/05, David Nicol [EMAIL PROTECTED] wrote:
what's OP_DOR?
//
Now that defined-or has an opcode, is
if(defined(EXPR)){...
optimized to use it instead of calling OP_DEFINED?
you mean unless(defined(EXPR)) surely... No, it's not, currently.
Re: [PATCH] licensing terms for perlglossary.pod
On Tue, Sep 20, 2005 at 09:14:53PM +0200, Rafael Garcia-Suarez wrote: On 9/20/05, Yitzchak Scott-Thoennes [EMAIL PROTECTED] wrote: Tim O'Reilly says we can say: Woot. Where ? See attached. --- perl/pod/perlglossary.pod.orig 2005-09-20 11:22:31.480172800 -0700 +++ perl/pod/perlglossary.pod 2005-09-20 11:24:18.453993600 -0700 @@ -3380,4 +3380,4 @@ Based on the Glossary of Programming Perl, Third Edition, by Larry Wall, Tom Christiansen Jon Orwant. Copyright (c) 2000, 1996, 1991 O'Reilly Media, Inc. -Used with permission. +This document may be distributed under the same terms as Perl itself. From [EMAIL PROTECTED] Tue Sep 20 09:11:55 2005 Return-Path: [EMAIL PROTECTED] X-Original-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: from mwest.oreilly.com (mwest.oreilly.com [209.204.146.24]) by samwise.efn.org (Postfix) with ESMTP id 275C61704CF for [EMAIL PROTECTED]; Tue, 20 Sep 2005 08:06:15 -0700 (PDT) Received: from [10.2.2.6] (unknown [67.96.213.158]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mwest.oreilly.com (Postfix) with ESMTP id 00A3250556; Tue, 20 Sep 2005 08:06:13 -0700 (PDT) In-Reply-To: [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Mime-Version: 1.0 (Apple Message framework v733) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: [EMAIL PROTECTED] Cc: Nicholas Clark [EMAIL PROTECTED], Laurie Petrycki [EMAIL PROTECTED], Cali Bush [EMAIL PROTECTED], Larry Wall [EMAIL PROTECTED], Tim O'Reilly [EMAIL PROTECTED] Content-Transfer-Encoding: 7bit From: Allison Randal [EMAIL PROTECTED] Subject: Re: Contributing Camel glossary to the perl distribution Date: Tue, 20 Sep 2005 08:06:11 -0700 To: Yitzchak Scott-Thoennes [EMAIL PROTECTED] X-Mailer: Apple Mail (2.733) X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on samwise.efn.org X-Spam-Level: X-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,FCS_URI_NODOTS autolearn=no version=2.63 Status: RO X-Status: A Content-Length: 5487 Lines: 207 Yup. That's fine. The lawyers said O'Reilly can sign a standard Perl contributor agreement when TPF has that in place in the next few months. But you don't need to wait for that. Have you cleaned up the Pod I sent and checked it in already? I'll be glad to see the glossary going in. :) Allison On Sep 20, 2005, at 7:34, Tim O'Reilly wrote: This document may be distributed under the same terms as Perl itself is fine with me. Let that be the last word unless you've had any protest from Larry or any other contributors to the glossary, which I doubt. We don't need lawyers to opine on it. On Sep 19, 2005, at 7:53 PM, Yitzchak Scott-Thoennes wrote: The initial cutoff for what goes in 5.8.8 is approaching (see http://nntp.perl.org/group/perl.perl5.porters/104533 ); any progress on getting specific licensing terms for the glossary? Thanks, Yitzchak (three messages quoted below) On Mon, Jun 20, 2005 at 05:44:11AM -0700, Allison Randal wrote: On Jun 20, 2005, at 1:03, Yitzchak Scott-Thoennes wrote: No, I don't have the POD and would appreciate getting it. I've requested it. It should arrive by the end of the week. I'll cite it that way for now, but now that I think about it more, it should mention what the licensing terms are, not just Used with permission. Would This document may be distributed under the same terms as Perl itself. be acceptable? That's the question I'm trying to work out with the lawyers. Go ahead and include it with just Used with permission, and we can modify it when we have more information. Thanks! Allison On Sun, Jun 19, 2005 at 07:51:35PM -0700, Allison Randal wrote: Do you have the POD for the glossary? If not, I'll get it for you. Use this text in the AUTHOR and COPYRIGHT section: Based on the Glossary of Programming Perl, Third Edition, by Larry Wall, Tom Christiansen Jon Orwant. Copyright (c) 2000, 1996, 1991 O'Reilly Media, Inc. Used with permission. Allison On Sun, Jun 19, 2005 at 06:28:56PM -0700, Allison Randal wrote: Okay, we'll add it to the distribution now and straighten out the paperwork in the next couple of weeks. (It'll be a couple of months before the next stable release of 5.8 anyway.) Allison On Jun 19, 2005, at 5:09, Tim O'Reilly wrote: You know, I'm sure that there are some formalities to be gone through, but I think you can assume that this is OK. On Jun 16, 2005, at 11:41 AM, Yitzchak Scott-Thoennes wrote: Any progress on checking with the authors? Can I add perlglossary to the perl distribution, and what kind of attribution would you like? Something like: =head1 AUTHOR AND COPYRIGHT Based on the Glossary of Programming
Re: oddity in op.c
On Tue, 20 Sep 2005 11:21:40 -0700, Yitzchak Scott-Thoennes
[EMAIL PROTECTED] wrote:
On Mon, Sep 19, 2005 at 11:31:19PM +0100, Nicholas Clark wrote:
Merijn notices this line in 5.8.x in S_new_logop
if ((type == OP_AND) == (SvTRUE(((SVOP*)first)-op_sv))) {
It's wonky. It seems to be wrong. But it's been that way since 5.8.0
started.
The corresponding point in blead is
if ((type == OP_AND SvTRUE(((SVOP*)first)-op_sv)) ||
(type == OP_OR !SvTRUE(((SVOP*)first)-op_sv)) ||
(type == OP_DOR !SvOK(((SVOP*)first)-op_sv))) {
This was patched by Marcus Holland-Moritz, changing that == to in the
process:
http://public.activestate.com/cgi-bin/perlbrowse?patch=22625
Presumably '==' is wrong. But if this is a bug, how can it be detected
with a perl level regression test?
== is correct; if both operands are 0 or 1, a == b is equivalent
to !(a ^ b) is equivalent to !(a !b || !a b) is equivlent to
a b || !a !b.
I just didn't understand why it was changed.
Changes like this (and the scattered const additions, thanks Andy) make
maintaining the dor patch take a lot of time. But it's in working order
again, and it still passes all tests :)
--
H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/)
using Perl 5.6.2, 5.8.0, 5.8.5, 5.9.2 on HP-UX 10.20, 11.00 11.11,
AIX 4.3 5.2, SuSE 9.2 9.3, and Cygwin. http://www.cmve.net/~merijn
Smoking perl: http://www.test-smoke.org,perl QA: http://qa.perl.org
reports to: [EMAIL PROTECTED],perl-qa@perl.org
Re: [PATCH] licensing terms for perlglossary.pod
On 9/20/05, Yitzchak Scott-Thoennes [EMAIL PROTECTED] wrote: Tim O'Reilly says we can say: Woot. Where ? See attached. --- perl/pod/perlglossary.pod.orig 2005-09-20 11:22:31.480172800 -0700 +++ perl/pod/perlglossary.pod 2005-09-20 11:24:18.453993600 -0700 So, thanks, applied as change #25523 to bleadperl. (I'm quite happy about this, even if this means one less interesting flamewar on debian-legal :)
Re: Zlib 2.00_02 on VMS
[ Sorry for the late reaction ] Op een mooie zomerdag (Sunday 11 September 2005 23:39),schreef Paul Marquess: From: Abe Timmerman [mailto:[EMAIL PROTECTED] Op een mooie zomerdag (Sunday 11 September 2005 19:14),schreef Paul Marquess: From: John E. Malmberg [mailto:[EMAIL PROTECTED] 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. No, the changes are only on CPAN. This is the latest snapshot http://search.cpan.org/CPAN/authors/id/P/PM/PMQS/Compress-Zlib- 2.000_02.tar . gz This is with 5.8.6 on Alpha: Thanks Abe. There aren't as many test failing as I was expecting there to be on an OS that is quite different from the Unix variants. The good news is that the tests that John reported as failing with the core Compress::Zlib are indeed fixed with this new version. Also all the tests below are failing (I think) because of non-portable coding in the test suite, not in the code itself. I cannot test any futher now, as TestDrive is down at the moment. Good luck, Abe -- Well, dereferencing that (as CvGV() would do) leads nowhere. Or, as the Ten Commandments for C Programmers quoth, Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end. -- Jarkko Hietaniemi on p5p @ 2002-05-14
Re: BUG: MAKEMAKER 6.30_01 and blead in MM_UNIX.pm for VMS
On Tue, Sep 20, 2005 at 02:02:24PM -0400, Peter Prymmer wrote: By the way, why is `false` desirable to have in a Makefile? Why does MakeMaker need to know how to do it? It appears it wants to make sure certain targets fail when the commands themselves don't necessarily exit with non-zero. Its the make equivalent of return 0. There's only three occurances of this. One is specific to OS/2. One is in MM_Unix-perldepend which appears to be unused. Only this one is actually used in day-to-day Makefiles but it only happens if the Makefile.PL is newer than the Makefile, so its not critical code. # --- MakeMaker makefile section: # We take a very conservative approach here, but it's worth it. # We move Makefile to Makefile.old here to avoid gnu make looping. $(FIRST_MAKEFILE) : Makefile.PL $(CONFIGDEP) $(NOECHO) $(ECHO) Makefile out-of-date with respect to $? $(NOECHO) $(ECHO) Cleaning current config before rebuilding Makefile... -$(NOECHO) $(RM_F) $(MAKEFILE_OLD) -$(NOECHO) $(MV) $(FIRST_MAKEFILE) $(MAKEFILE_OLD) - $(MAKE) $(USEMAKEFILE) $(MAKEFILE_OLD) clean $(DEV_NULL) $(PERLRUN) Makefile.PL $(NOECHO) $(ECHO) == Your Makefile has been rebuilt. == $(NOECHO) $(ECHO) == Please rerun the $(MAKE) command. == false -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Insulting our readers is part of our business model. http://somethingpositive.net/sp07122005.shtml
Re: BUG: MAKEMAKER 6.30_01 and blead in MM_UNIX.pm for VMS
On Tue, Sep 20, 2005 at 02:02:31PM -0700, Michael G Schwern wrote: One is in MM_Unix-perldepend which appears to be unused. I lied, its not unused. Its used when building perl and XS modules so that's probably important. But it only happens when config.h is out of date. And VMS has its own version which doesn't use false. However, MakeMaker using false is not new so I don't know why this is only now an issue. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Ahh email, my old friend. Do you know that revenge is a dish that is best served cold? And it is very cold on the Internet!
Re: BUG: MAKEMAKER 6.30_01 and blead in MM_UNIX.pm for VMS
Michael G Schwern [EMAIL PROTECTED] wrote on 09/20/2005 05:02:31 PM in reply to my question: Why does MakeMaker need to know how to do it? Only this one is actually used in day-to-day Makefiles but it only happens if the Makefile.PL is newer than the Makefile, so its not critical code. # --- MakeMaker makefile section: # We take a very conservative approach here, but it's worth it. # We move Makefile to Makefile.old here to avoid gnu make looping. $(FIRST_MAKEFILE) : Makefile.PL $(CONFIGDEP) $(NOECHO) $(ECHO) Makefile out-of-date with respect to $? $(NOECHO) $(ECHO) Cleaning current config before rebuilding Makefile... -$(NOECHO) $(RM_F) $(MAKEFILE_OLD) -$(NOECHO) $(MV) $(FIRST_MAKEFILE) $(MAKEFILE_OLD) - $(MAKE) $(USEMAKEFILE) $(MAKEFILE_OLD) clean $(DEV_NULL) $(PERLRUN) Makefile.PL $(NOECHO) $(ECHO) == Your Makefile has been rebuilt. == $(NOECHO) $(ECHO) == Please rerun the $(MAKE) command. == false OK then replacing that last line with: $(PERLRUN) -e exit 1 might do the trick for most unixes (I presume MacOS X) and VMS. I am not too sure about dmake or nmake on Windows (and cannot easily test it out here). I guess the docs recommend editing a Makefile.PL to solve problems, hence the dependency problem obtains even for folks who are not CPAN developers. BTW a descrip.mms generated by 6.17 has no command at that spot. If I run the moral eqivalent of the following: $ mmk $ (the return to the shell prompt indicates this directory is already built) $ touch makefile.pl $ mmk $ mmk Descrip.MMS out-of-date with respect to MAKEFILE.PL,PERL_ROOT:[LIB.VMS_AXP.5_8_1]CONFIG.PM,PERL_ROOT:[LIB.VMS_AXP.5_8_1.CORE]CONFIG.H Cleaning current config before rebuilding Descrip.MMS ... Rename/NoConfirm Descrip.MMS Descrip.MMS_old MMK /Descrip=Descrip.MMS_old clean MCR $dka300:[perl.perl-5_8_1_root]perl.exe -MExtUtils::Command -e rm_f *.Map *.Dmp *.Lis *.cpp *.exe *.obj *.olb *.Opt XPath.bso .MM_Tmp MCR $dka300:[perl.perl-5_8_1_root]perl.exe -MExtUtils::Command -e rm_rf pm_to_blib blib [.blib.arch.auto.XML.XPath]extralibs.all perlmain.c MCR $dka300:[perl.perl-5_8_1_root]perl.exe -MExtUtils::Command -e rm_rf pm_to_blib.ts Makeaperl.MMS [.blib.arch.auto.XML.XPath]extralibs.ld MCR $dka300:[perl.perl-5_8_1_root]perl.exe Makefile.PL Checking if your kit is complete... Looks good Writing Descrip.MMS for XML::XPath Descrip.MMS has been rebuilt. Please run MMK to build the extension. cp [.xpath]step.pm [.blib.lib.xml.xpath]step.pm cp [.xpath.node]attribute.pm [.blib.lib.xml.xpath.node]attribute.pm cp [.xpath]parser.pm [.blib.lib.xml.xpath]parser.pm cp [.xpath.node]element.pm [.blib.lib.xml.xpath.node]element.pm cp [.xpath]node.pm [.blib.lib.xml.xpath]node.pm cp [.xpath]variable.pm [.blib.lib.xml.xpath]variable.pm cp [.xpath]number.pm [.blib.lib.xml.xpath]number.pm cp [.xpath]perlsax.pm [.blib.lib.xml.xpath]perlsax.pm cp [.xpath]root.pm [.blib.lib.xml.xpath]root.pm cp [.xpath.node]namespace.pm [.blib.lib.xml.xpath.node]namespace.pm cp [.xpath]locationpath.pm [.blib.lib.xml.xpath]locationpath.pm cp [.xpath.node]pi.pm [.blib.lib.xml.xpath.node]pi.pm cp [.xpath]literal.pm [.blib.lib.xml.xpath]literal.pm cp [.xpath]builder.pm [.blib.lib.xml.xpath]builder.pm cp [.xpath.node]text.pm [.blib.lib.xml.xpath.node]text.pm cp [.xpath.node]comment.pm [.blib.lib.xml.xpath.node]comment.pm cp xpath.pm [.blib.lib.xml]xpath.pm cp [.xpath]boolean.pm [.blib.lib.xml.xpath]boolean.pm cp [.xpath]function.pm [.blib.lib.xml.xpath]function.pm cp [.xpath]expr.pm [.blib.lib.xml.xpath]expr.pm cp [.xpath]xmlparser.pm [.blib.lib.xml.xpath]xmlparser.pm cp [.xpath]nodeset.pm [.blib.lib.xml.xpath]nodeset.pm Copy/NoConfirm [.examples]xpath [.blib.script]xpath %COPY-S-COPIED, USER:[PPRYMMER.CPAN_MODULES.XML-XPATH-1_13.EXAMPLES]XPATH.;1 copied to USER:[PPRYMMER.CPAN_MODULES.XML-XPATH-1_13.BLIB.SCRIPT]XPATH.;1 (3 blocks) $ So it is falling through to the default all (build) target and running executing that section. It did not error out back to DCL with the admonishment to rerun MMK. By the way, touch is not a native VMS/DCL shell command. If I change the makefile section to have the C\t$(PERLRUN) -e exit 1 final command I see the following after I touch makefile.pl: $ mmk Descrip.MMS out-of-date with respect to MAKEFILE.PL,PERL_ROOT:[LIB.VMS_AXP.5_8_1]CONFIG.PM,PERL_ROOT:[LIB.VMS_AXP.5_8_1.CORE]CONFIG.H Cleaning current config before rebuilding Descrip.MMS ... Rename/NoConfirm Descrip.MMS Descrip.MMS_old MMK /Descrip=Descrip.MMS_old clean MCR $dka300:[perl.perl-5_8_1_root]perl.exe -MExtUtils::Command -e rm_f *.Map *.Dmp *.Lis *.cpp *.exe *.obj *.olb *.Opt XPath.bso .MM_Tmp MCR $dka300:[perl.perl-5_8_1_root]perl.exe -MExtUtils::Command -e rm_rf pm_to_blib [.blib.arch.auto.XML.XPath]extralibs.ld pm_to_blib.ts perlmain.c blib MCR $dka300:[perl.perl-5_8_1_root]perl.exe -MExtUtils::Command -e rm_rf [.blib.arch.auto.XML.XPath]extralibs.all Makeaperl.MMS MCR
Re: BUG: MAKEMAKER 6.30_01 and blead in MM_UNIX.pm for VMS
Michael G Schwern wrote: On Tue, Sep 20, 2005 at 02:02:24PM -0400, Peter Prymmer wrote: By the way, why is `false` desirable to have in a Makefile? Why does MakeMaker need to know how to do it? It appears it wants to make sure certain targets fail when the commands themselves don't necessarily exit with non-zero. Its the make equivalent of return 0. There's only three occurances of this. One is specific to OS/2. One is in MM_Unix-perldepend which appears to be unused. Only this one is actually used in day-to-day Makefiles but it only happens if the Makefile.PL is newer than the Makefile, so its not critical code. # --- MakeMaker makefile section: # We take a very conservative approach here, but it's worth it. # We move Makefile to Makefile.old here to avoid gnu make looping. $(FIRST_MAKEFILE) : Makefile.PL $(CONFIGDEP) $(NOECHO) $(ECHO) Makefile out-of-date with respect to $? $(NOECHO) $(ECHO) Cleaning current config before rebuilding Makefile... -$(NOECHO) $(RM_F) $(MAKEFILE_OLD) -$(NOECHO) $(MV) $(FIRST_MAKEFILE) $(MAKEFILE_OLD) - $(MAKE) $(USEMAKEFILE) $(MAKEFILE_OLD) clean $(DEV_NULL) $(PERLRUN) Makefile.PL $(NOECHO) $(ECHO) == Your Makefile has been rebuilt. == $(NOECHO) $(ECHO) == Please rerun the $(MAKE) command. == false According to the above, it is also triggered by $(CONFIGDEP) being newer than $(FIRST_MAKEFILE) which seems to happen on the VMS rebuilds I do quite a bit. I seem to also remember seeing it being triggered by using the REALCLEAN target on the main VMS DESCRIP.MMS, but maybe I am mistaken about that. If the false command causes MMK/MMS to abort, it kills the entire VMS rebuild. Having the false command not exist is good enough for that. If the false command returns a SUCCESS on VMS, then the VMS build procedure does re-run the $(MAKE) command and successfully builds. This only occurs on a rebuild and not on the initial build. As near as I can tell, the creation time of the PERLSHR.EXE or DBGPERLSHR.EXE or something created by their rebuild seems to trigger the make files for all the extensions to be rebuilt on VMS. Or it could be that the VMS build always rebuilds the makefiles, and until this false command tried to be executed, I did not notice. -John [EMAIL PROTECTED] Personal Opinion Only
Re: BUG: MAKEMAKER 6.30_01 and blead in MM_UNIX.pm for VMS
John E. Malmberg [EMAIL PROTECTED] wrote on 09/20/2005 08:09:56 AM: A VMS exit 44 will also cause MMS/MMK by default to abort the makefile with MMS/MMK also exiting with an error. I think Michael mentioned explicitly that was what was wanted. If you want a VMS exit code that UNIX programs should interpret as an EXIT 1, then the following (mostly undocumented) hack will work. VMS status code = %x35a000 + (UNIX status * 8), and if this is a success status, add 1, otherwise VMS will interpret it as a warning. EAGLE exit %x35A000 + (1 * 8) + 1 EAGLE x = %x35A000 + (1 * 8) + 1 EAGLE show sym x X = 3514377 Hex = 0035A009 Octal = 00015320011 A specific $? shell status returned by a specific Unix vendor's implementation of the false command is not necessarily what is needed. Rather an indication of failure is what is asked for and Michael's proposed perl -e exit 1 will suit the task. Although the exit 44 I had suggested could also work on VMS, the exit 1 will work there too (despite the doubt I might have spread by my earlier statement). Peter Prymmer
Re: BUG: MAKEMAKER 6.30_01 and blead in MM_UNIX.pm for VMS
Michael G Schwern wrote: On Tue, Sep 20, 2005 at 02:02:31PM -0700, Michael G Schwern wrote: One is in MM_Unix-perldepend which appears to be unused. I lied, its not unused. Its used when building perl and XS modules so that's probably important. But it only happens when config.h is out of date. And VMS has its own version which doesn't use false. However, MakeMaker using false is not new so I don't know why this is only now an issue. It only shows up on VMS in blead perl if you are rebuilding, not on the initial build. So unless you are modifying things on VMS after an initial build, it would not be an issue. When I started on blead on VMS there were so many things that were not working, this one got lost in the noise because I added a false command to work around it. I was kinda hoping that once I got the other issues resolved that this issue would have gone away. -John
Smoke [5.8.7] 25516 FAIL(F) openbsd 3.7 (i386/1 cpu)
Automated smoke report for 5.8.7 patch 25516 mccoy.peters.homeunix.org: Intel Pentium III (GenuineIntel 686-class, 512KB L2 cache) (i386/1 cpu) onopenbsd - 3.7 using cc version 3.3.5 (propolice) smoketime 10 hours 44 minutes (average 1 hour 4 minutes) Summary: FAIL(F) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = make test-prep 25516 Configuration (common) none --- - F - F - -Uuseperlio F F F F F F F F -Duse64bitint F F F F -Duseithreads F F F F -Duseithreads -Duse64bitint | | | +- PERLIO = perlio -DDEBUGGING | | +--- PERLIO = stdio -DDEBUGGING | +- PERLIO = perlio +--- PERLIO = stdio Failures: [stdio] -Uuseperlio [stdio] -DDEBUGGING -Uuseperlio [stdio/perlio] [stdio/perlio] -DDEBUGGING [stdio/perlio] -Duse64bitint [stdio/perlio] -DDEBUGGING -Duse64bitint [stdio/perlio] -Duseithreads [stdio/perlio] -DDEBUGGING -Duseithreads [stdio] -Duseithreads -Duse64bitint [stdio] -DDEBUGGING -Duseithreads -Duse64bitint ../lib/filetest.t...FAILED 12-15 [perlio] -Duseithreads -Duse64bitint ../lib/filetest.t...FAILED 12-15 Inconsistent test results (between TEST and harness): ../lib/ExtUtils/t/Constant.tFAILED at test 229 [perlio] -DDEBUGGING -Duseithreads -Duse64bitint ../lib/filetest.t...FAILED 12-15 Inconsistent test results (between TEST and harness): ../ext/B/t/bytecode.t...FAILED at test 16 -- Report by Test::Smoke v1.19#716 running on perl 5.8.6 (Reporter v0.016 / Smoker v0.015)
Re: [EMAIL PROTECTED] Add hard link and V8.2 crtl support to VMS.
Jeremy Begg wrote: Hello John, This patch adds the ability to build Perl on 64 bit VMS V8.2 with support for hard links, and the newer CRTL features. For which version(s) of Perl is this suitable? 5.8.7 is the latest stable release; can the patch be used with that? I have not run that patch against 5.8.7, but the initial work that I did was on the 5.8.6 release. I just needed blead stable enough so that I could start merging in the changes with out the risk of breaking more things. For hard link support, the Perl build procedure needs hard links enabled on the build disk, and there is an additional patch that has previously been applied to blead similar to the one to s2p.pl. If you need any of the stuff for before OpenVMS 8.2, follow the comments in Configure.com. In most cases it is just a matter of enabling them for the version of VMS they appeared in, and then testing the edits to make sure that the configure and build runs correctly. And then submitting the fixes back here. -John [EMAIL PROTECTED] Personal Opinion Only
Re: bleadperl MakeMaker problems building DynaLoader
On Wed, Aug 24, 2005 at 01:11:36AM -0700, Yitzchak Scott-Thoennes wrote: I just tried to build bleadperl and got this: Is this still a problem? -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Ahh email, my old friend. Do you know that revenge is a dish that is best served cold? And it is very cold on the Internet!
Re: Upgrade MakeMaker in maint
Nicholas Clark wrote: On Mon, Sep 19, 2005 at 05:56:50PM -0700, Michael G Schwern wrote: Maint is still using MakeMaker 6.17 which is now TWO YEARS OLD! Last I checked there was some VMS failure or another possibly tied to File::Find but I don't have details. I really rather 5.8.8 not go out with 6.17 again, 6.30 is good and stable. Can we just take the plunge, put 6.30 into maintperl and work out the glitches? The last thing that I remember was that there was some fun with make distclean on VMS in blead and SDBM_File. No distclean target found in the main descrip.mms file. cleanlis : cleantest : tidy : cleanlis clean : tidy cleantest - @make_ext $(MINIPERL_EXE) $(MMS) clean - @extra_pods CLEAN realclean : clean - @make_ext $(MINIPERL_EXE) $(MMS) realclean cleansrc : clean Or at least something with SDBM_File I was going to look last week to see if you're most recent version had cured it, but it was the day after testdrive went down for 2 weeks. It is being moved to a new building, but I do not have any details. Is the current version happy on VMS with SDBM_File? I will confess that I have not explicitly tried all the targets. -John [EMAIL PROTECTED] Personal Opinion Only
Re: bleadperl MakeMaker problems building DynaLoader
On Tue, Sep 20, 2005 at 06:58:55PM -0700, Michael G Schwern wrote: On Wed, Aug 24, 2005 at 01:11:36AM -0700, Yitzchak Scott-Thoennes wrote: I just tried to build bleadperl and got this: Is this still a problem? No, it vanished as mysteriously as it arrived.
