On 06/18/2015 09:01 AM, Atlas, Ze'Ev wrote:
Hi all
1. In the last few months, I see periodically, some email speaking
about 'smoke' tests. Some pass and some fail. It is not clear whether
Perl for z/OS is ready or not. Could somebody please shed some lite on
the situation. And if it is
I have made quite a few edits to perlebcdic (attached), hopefully
clarifying things, and bringing it up-to-date.
Further patches welcome.
perlebcdic.pod
Description: Perl program
: Karl Williamson; Yaroslav Kuzmin; Perl5 Porters; perl-mvs@perl.org; Ray
Mullins
Тема: Re: НА: OS/390 service discontinued 2004/09/30
Karl, etc,
From z/OS 2.1 man uname
The following options select the information to be displayed:
-aAll fields (equivalent to -mnrsv).
-IThe IBM
Could someone with a working v5.8 Perl, please run this one-liner on it,
and report back the output
perl -le 'my $a = pack(U, 65); print ord $a'
Thanks in advance
On 03/24/2015 06:27 AM, Karl Nordstrom wrote:
$ uname -I
z/OS
$ uname -Ia
z/OS IPO4 01.00 02 2818
$ uname -a
OS/390 IPO4 24.00 04 2818
I'm confused by all this. I think Yaroslav is pointing out that
internally his z/OS still uses os390, but Karl is saying his z/OS doesn't.
Please
On 03/26/2015 10:00 AM, Yaroslav Kuzmin wrote:
Automated smoke report for branch blead 5.21.11 patch
aab1202a8d4b691b16384fb41d2e2a06abf664e2 v5.21.10-19-gaab1202
It looks like you have now set up smoking to happen automatically Am I
right, and if so, how is this set up. Like, does it look
On 03/23/2015 06:11 PM, Ray Mullins wrote:
What would it take to have documentation, etc., updated to reflect the
current name of z/OS?
Most of the documentation doesn't mention os390. z/OS is not a
syntactically legal identifier name, so some things need to remain using
os390. But it
On 03/19/2015 06:34 AM, Yaroslav Kuzmin wrote:
Smoke log available at
https://drive.google.com/file/d/0B5PTttxwo7qAMHZmcFZic3RGU2c
Automated smoke report for branch ebcdic 5.21.10 patch
6b2c3d7cd9f45c0be3a892b77a571dc37e3ccc54 v5.21.9-306-g6b2c3d7
RS12: 2817 (2817/)
onos/390 -
On 03/16/2015 05:03 PM, Karl Williamson wrote:
On 03/15/2015 11:21 PM, Yaroslav Kuzmin wrote:
In file MANIFEST line
4185 lib/meta_notation.pmHelper for certain /lib .pm's
4186 lib/meta_notation.t See if meta_notation.t works
01:10) RS12 : PDKUZM | ~/ussport/perl/perl-build : ./Configure
...@rocketsoftware.com
Web: www.rocketsoftware.com
От: Karl Williamson pub...@khwilliamson.com
Отправлено: 15 марта 2015 г. 21:47
Кому: Yaroslav Kuzmin
Копия: perl-mvs@perl.org
Тема: New branch to test
This adds several more changes to the branch I posted late last week
This adds several more changes to the branch I posted late last week.
It includes your csect changes, instead of the previous mro.c changes.
We may or may not succeed in getting the file name changed before the
deadline, so we should make sure this works, as a backup.
As always, this has been
On 03/11/2015 11:59 PM, Yaroslav Kuzmin wrote:
Smoke log available at
https://drive.google.com/file/d/0B5PTttxwo7qAZU9fNUYxTHhkSkE
Ok, thanks. This test showed that dumper.t no longer fails. The single
test failure now, from a previously passing test, was because of a typo
on my part .
On 03/12/2015 02:56 AM, Yaroslav Kuzmin wrote:
I needed modules connect manually .
1 download *.tar.gz
2 copy on z/OS
3 translate ASCII EBCDIC
To do this translation you can use either the C program Yaroslav
created, and which is attached, or the perl script I created, also
attached.
I
On 03/10/2015 06:18 AM, Yaroslav Kuzmin wrote:
Smoke log available at
https://drive.google.com/file/d/0B5PTttxwo7qAS1I4c2dRRGhZTEk
dumper.t.log available at
https://drive.google.com/file/d/0B5PTttxwo7qAbXZoam5BRFlHV0E
Automated smoke report for branch ebcdic 5.21.10 patch
On 03/05/2015 11:56 PM, Yaroslav Kuzmin wrote:
So very good, When the plan to merge with a branch blead ? :)
This is still failing dumper.t. So I need an individual log file of
that to see what is wrong, as you've done before.
But I've added a new test to that file, and rebased to latest
On 03/03/2015 03:18 AM, Yaroslav Kuzmin wrote:
Smoke log available at
https://drive.google.com/file/d/0B5PTttxwo7qARlU5UHA4clBBUW8
dumper.t.log available at
https://drive.google.com/file/d/0B5PTttxwo7qAVUVJS1Y1dURfeEk
Thanks, That shows that Pod::Simple now works on EBCDIC. I've removed
On 03/03/2015 06:16 PM, Karl Williamson wrote:
On 03/03/2015 03:18 AM, Yaroslav Kuzmin wrote:
Smoke log available at
https://drive.google.com/file/d/0B5PTttxwo7qARlU5UHA4clBBUW8
dumper.t.log available at
https://drive.google.com/file/d/0B5PTttxwo7qAVUVJS1Y1dURfeEk
Thanks, That shows that Pod
On 03/01/2015 11:28 PM, Yaroslav Kuzmin wrote:
Smoke log available at
https://drive.google.com/file/d/0B5PTttxwo7qASk5aNU8zOEFrUms
dumper.t log available at
https://drive.google.com/file/d/0B5PTttxwo7qAdWhvMzRzLVE3ZFE
Thanks. That uncovered some newly introduced errors in blead. I
This contains an updated Pod::Simple that we want to make sure still
works on EBCDIC.
I've made some progress on fixing Data::Dumper and its tests, and want
to make sure I'm on the right track. Please run dumper.t by hand as
you've done before and send the log separately.
It now skips the
We are down to 7 failing tests in the Perl 5 core.
One of them, stat.t, should pass with the new version I just pushed.
Its failure appears due to a bug in os390 libc; it fails in a vanilla C
program (thanks to Jarkko Hietaniemi for suggesting to try that, and
Bram for reminding me) and has
On 02/16/2015 01:34 AM, Yaroslav Kuzmin wrote:
I have now pushed a new version for you to smoke which should fix the
new bom failure, and should skip the failing stat failure.
no new branch.
Sorry. I just pushed one, updated to latest blead as well
On 02/12/2015 12:42 AM, Yaroslav Kuzmin wrote:
Smoke logs available at
https://drive.google.com/file/d/0B5PTttxwo7qANm5DUzVCRjlIQmc
This didn't give some output I thought it would. So could you run this
test manually and email the output?
cd t
./perl -I../lib
On 02/12/2015 12:58 AM, Yaroslav Kuzmin wrote:
That file is attached. Please compile it and run it and post the results.
(02:46) RS12 : PDKUZM | ~/ussport/perl/test : c99
-qlanglvl=extended:extc89:extc99 -qlongname -qxplink -qdll -DOEMVS
-D_XOPEN_SOURCE_EXTENDED -D_ALL_SOURCE
On 02/10/2015 12:51 AM, Yaroslav Kuzmin wrote:
Smoke logs available at
https://drive.google.com/file/d/0B5PTttxwo7qAdkVaT2x0RUlkRm8
These warning messages come out consistently, but no tests actually
fail. I'm wondering what should be done about these, if anything?
dist/Exporter/t/warn
On 02/10/2015 12:50 AM, Yaroslav Kuzmin wrote:
Now I'm delving into the stat failure. Craig Berry made the following
suggestion to get started on that. Please run
./perl -Ilib Porting/expand-macro.pl
'PerlLIO_fstat(my_dirfd(IoDIRP(io)), PL_statcache)'
and post the one line output.
This smoke gave the results so that I think we now know how to fix the
locale test failure. I have pushed another branch which should tell.
I hope to have fixed dist/ExtUtils-CBuilder/t/04-base.t in this branch,
and got closer to the problem in dist/Data-Dumper/t/dumper.t.
There were no
There was progress in this smoke. I've added code to Cwd to work around
the $SYSNAME self-pointing symbolic link. But we get things like
'/RS12/TMP/_WVLFEWRL4/ALPHA/BETA/GAMMA/DELTA/EPSILON'
Can you explain what that /RS12 is?
The run/locale.t failure is due to getting an environment
This failure was caused by an unrelated issue on blead; it also broke
win32 builds. The latest version to test now has that fixed, and
rebased to the latest blead
On 02/03/2015 12:35 AM, Yaroslav Kuzmin wrote:
Smoke logs available at
This fixed some things, but we have a new failure due to a new blead
feature, in bop.t.
There's a new branch with some more development, and debugging info to test.
On 02/02/2015 06:23 AM, Yaroslav Kuzmin wrote:
Smoke logs available at
On 01/29/2015 03:53 AM, Yaroslav Kuzmin wrote:
Smoke logs available
athttps://drive.google.com/file/d/0B5PTttxwo7qAVExQbEc4MEZPX0U
Automated smoke report for branch ebcdic 5.21.9 patch
df452cddd0e4e613c2c3c30a2619e1de5bdaac74 v5.21.8-232-gdf452cd
RS12: 2817 (2817/)
onos/390 -
On 01/27/2015 01:57 AM, Yaroslav Kuzmin wrote:
Thanks for this.
I instrumented Cwd to see what the problems were. The test that
actually fails uses more levels than the system allows (8). I don't
know if that number, MAXSYMLINKS, is configurable or not.
But we have a bunch of places where
On 01/23/2015 12:08 AM, Yaroslav Kuzmin wrote:
It's not clear to me if you've tried changing the verbosity
configuration file and that's what you've sent us, and that the files
that are supposed to be generated by that option aren't getting
generated, or if you haven't gotten to that yet.
In
On 01/16/2015 12:45 AM, Yaroslav Kuzmin wrote:
Smoke logs available
athttps://drive.google.com/file/d/0B5PTttxwo7qAZk5faE1ic0w3OWs
(set verbose mode -v 2 Test::smoke, but file *.log *.out *.rpt not copy in dir
smoke/logs )
I think this didn't set the verbose mode properly. Further
On 01/15/2015 06:44 AM, Yaroslav Kuzmin wrote:
Concerning LC_ALL.
Do you have some initialization code for your
shell that sets the others? The point of LC_ALL is you can use it,
setting one thing instead of having to many.
In system z/OS USS, I do not do additional settings LC_ALL
But at a
I couldn't find anything on the internet that describes the purpose of
the EBCDIC controls that don't have ASCII equivalents, like EO, RNL,
RPT, etc. I'm wondering if someone can point me to a document that has
it. Supposedly they are described in IBM Corporate Standard, C-S
3-3220-002, but
On 12/30/2014 12:10 AM, Yaroslav Kuzmin wrote:
P.S. I am on vacation from 01.01.2015 to 12.01.2015
Have a good vacation
This would be a good time to update the current status. There are
currently 10 failing core tests, 99% pass rate. These last few are
proving somewhat intractable. I'll
On 12/25/2014 01:10 AM, Yaroslav Kuzmin wrote:
Smoke logs available at -
https://drive.google.com/file/d/0B5PTttxwo7qAakdfbkRDRklfWDA
Automated smoke report for branch ebcdic 5.21.7 patch
8f7949da3760661252f10651cd69851f92dc739f v5.21.6-755-g8f7949d
RS12: 2817 (2817/)
onos/390 -
, Karl Williamson wrote:
This Perl code in t/op/stat.t:
ok(opendir(DIR, .), 'Can open . dir') || diag Can't open '.':
$!;
use warnings;
ok(stat(DIR), stat() on dirhandle works);
ends up calling this code in pp_sys.c:
PL_laststatval = PerlLIO_fstat(my_dirfd(IoDIRP(io)), PL_statcache
On 12/17/2014 06:17 PM, Craig A. Berry wrote:
On Wed, Dec 17, 2014 at 5:56 PM, M. Ray Mullins m.ray.mull...@gmail.com wrote:
Finding out what the C runtime put in errno would be helpful.
Printing $! in the test script would likely do the trick, though I
don't see Perl_my_dirfd setting errno
This Perl code in t/op/stat.t:
ok(opendir(DIR, .), 'Can open . dir') || diag Can't open '.':
$!;
use warnings;
ok(stat(DIR), stat() on dirhandle works);
ends up calling this code in pp_sys.c:
PL_laststatval = PerlLIO_fstat(my_dirfd(IoDIRP(io)), PL_statcache);
I have pushed a new branch to be tested, incorporating today's blead. It
likely won't merge automatically.
It looks to me like you are getting close to being able to do this
completely automatically. I got the sense that the latest result was
emailed automatically.
Feel free to try out
Thanks for the latest smoke result. I see that you got DEBUGGING to work
in it. I have pushed a new branch to be tested. It likely won't merge
automatically.
But it includes a temporary patch to Configure to get your bash. That
should keep you from having to remove Policy.sh.
There is
On 12/16/2014 07:42 PM, Karl Williamson wrote:
Thanks for the latest smoke result. I see that you got DEBUGGING to work
in it. I have pushed a new branch to be tested. It likely won't merge
automatically.
But it includes a temporary patch to Configure to get your bash. That
should keep you
We still have the problem of the smoke not running DEBUGGING. Below is
extracted from the log file Yaroslav posted. I searched for the FSUM
error codes online, and found no extra detail beyond the text in the
accompanying messages.
Configuration: -Dusedevel -DDEBUGGING
On 12/07/2014 11:12 PM, Karl Williamson wrote:
I have pushed a new branch to be tested. I may have fixed just one more
test, but have added more debugging to track down some of the others.
The previous version had added a couple of tests that had been skipped
for a long time because
On 12/06/2014 11:16 PM, Father Chrysostomos wrote:
Karl Williamson wrote:
The test is attached in its entirety. I see no real difference betweeen
running it on Linux vs os390 with -DpTv. The file has been pared down
to 2 tests. In both, Linux says it is at EOF, and EBCDIC says line 2
Can't
On 12/07/2014 11:12 PM, Karl Williamson wrote:
The previous version fixed 6 of the 18 failing tests. This new version
adds some more debugging output in places, and adds a couple of tests
that had been skipped for a long time because the core code wasn't ready
to test them. Hopefully
On 12/07/2014 11:12 PM, Karl Williamson wrote:
We have found and changed a potential bug that could be causing some or
all of the parsing problems. I've cleaned up a couple of other tests.
This is rebased to the latest blead. It likely won't merge automatically.
Again, this should be run
On 12/08/2014 08:13 AM, Karl Williamson wrote:
On 12/07/2014 11:12 PM, Karl Williamson wrote:
We have found and changed a potential bug that could be causing some or
all of the parsing problems. I've cleaned up a couple of other tests.
This is rebased to the latest blead. It likely won't
We sometimes get this message:
dist/Data-Dumper/t/bugs ... #
Failed test 'GVs with UTF8 names (or not, depending on perl version)'
# at t/bugs.t line 116.
# got: 'GLOB(0x21185f60)'
# expected: 'GLOB(0x21201838)'
CEE0802C Heap storage control
We have found and changed a potential bug that could be causing some or
all of the parsing problems. I've cleaned up a couple of other tests.
This is rebased to the latest blead. It likely won't merge automatically.
Again, this should be run on a DEBUGGING perl.
the smoking code.
On 12/04/2014 04:57 PM, Karl Williamson wrote:
I had never looked at the end of the smoke reports we're getting until
today, but this is the error:
==
Configuration: -Dusedevel -DDEBUGGING
The test is attached in its entirety. I see no real difference betweeen
running it on Linux vs os390 with -DpTv. It's just that the on Linux,
it outputs EXECUTING... and succeeds, whereas it doesn't do either on
os390, and the test harness says
FAILED--expected 1 tests, saw 0.
I can't
The test is attached in its entirety. I see no real difference betweeen
running it on Linux vs os390 with -DpTv. The file has been pared down
to 2 tests. In both, Linux says it is at EOF, and EBCDIC says line 2
Can't declare do block in my at - line 2, at EOF
---
Can't declare do block
I have uploaded an html file to
https://www.dropbox.com/s/qii0stvgledw1yn/diff.out?dl=0
It's too large to send to this list.
It contains a 'diff' listing between running a test (with the -DpTv
option) that is failing on ebcdic and passing on linux
To avoid any ambiguity, I've placed the
On 12/05/2014 03:41 PM, Father Chrysostomos wrote:
Where things really start to go wrong is at line #8696. The linux is
looking at my ... and os390 is looking at \nmy ...
I'm doing this blindly. Is this the 'my' in the here-doc?
$WANT = 'EOT';
my $VAR1 = '42
';
EOT
Yes.
There are several fixes.
This is rebased to the latest blead. It likely won't merge automatically.
It would be really good to run this on a DEBUGGING perl, manually if
necessary, so we can look at that output. The smoker code you've been
using (as I showed in my message 6 hours ago) is not
As of today, we are down to 19 failures of the tests we run on os390,
EBCDIC. This is a 98% pass rate. I'll need help in squashing most of
the rest. I'm annotating them all here. Suggestions welcome. They are
grouped in categories.
The following Deparse failure is the most worrisome to
On 12/03/2014 01:29 PM, Father Chrysostomos wrote:
Karl Williamson wrote:
The following Deparse failure is the most worrisome to me of the
remaining issues This is because it's returning malformed UTF-8, and it
looks to me like there is a wild read or write. If the system had a
tool like
I hopefully have fixed a 3 or 4 more tests, and added more debugging
output for another one.
This is rebased to the latest blead. It likely won't merge automatically.
I hopefully have fixed a couple more tests, and added even more
debugging output to help find some of the others.
This is rebased to the latest blead. It likely won't merge automatically.
I hopefully have fixed some errors, and added debugging output to help
find some of the others.
This is rebased to the latest blead. It likely won't merge automatically.
On 11/26/2014 03:32 PM, Tony Cook wrote:
On Wed, Nov 26, 2014 at 02:39:52PM -0700, Karl Williamson wrote:
We're getting this failure on os390:
# Failed test 'S_IFMT()'
# at Fcntl/t/mode.t line 88.
# got: '4278190080'
# expected: '-16777216'
If you add those two numbers up
On 11/26/2014 03:32 PM, Tony Cook wrote:
I suspect the other S_I* constants should be unsigned too.
Me too, but I'm leaving that to someone else.
On 11/27/2014 05:09 AM, Yaroslav Kuzmin wrote:
Smoke logs available at -
https://drive.google.com/file/d/0B5PTttxwo7qAUnhnZHE5aUFFa2M
Automated smoke report for branch ? 5.21.7 patch
RS12: 2817 (2817/)
onos/390 - 23.00
using c99 version
smoketime 1 hour 17 minutes
We're getting this failure on os390:
# Failed test 'S_IFMT()'
# at Fcntl/t/mode.t line 88.
# got: '4278190080'
# expected: '-16777216'
If you add those two numbers up it becomes clear that this bug is merely
one of signed vs unsigned. Likely a constant is missing its trailing
This fixes (I hope) about 20% of the remaining failures. Some tests are
cut down so that later you can run them by hand without getting
extraneous stuff. But for now, just smoke it as usual
Thanks
Karl Williamson
On 11/24/2014 05:26 AM, Yaroslav Kuzmin wrote:
Smoke logs available at -
https://drive.google.com/file/d/0B5PTttxwo7qATVQybXJkRW1sa2c
Automated smoke report for branch ? 5.21.6 patch
RS12: 2817 (2817/)
onos/390 - 23.00
using c99 version
smoketime 1 hour 21
On 11/21/2014 03:03 AM, Yaroslav Kuzmin wrote:
I have no way of sending mails with mainframe. I take the report and log files
from the directory
logs/smokecurrent/
https://drive.google.com/file/d/0B5PTttxwo7qAM2Fuel84bzU0VXM
On mainframe no git tools. Therefore, the revision is substituted
This is great news! We finally have a smoke report for z/OS after an
absence of many years. Getting these regularly is the criteria for
keeping support for this platform going forward, and it appears it's
going to happen.
I will need access to logs in order to debug the failures.
On
On 11/19/2014 05:45 AM, Yaroslav Kuzmin wrote:
On z/OS in perl processing of script lib/sigtrap.pm it hangs
on string
107
s/([\N{U+80}-\N{U+FF}])/sprintf(M-%c,utf8::unicode_to_native(utf8::native_to_unicode(ord($1))0177))/eg;
in function S_regclass overflow occurs in a loop variable.
: +7.922.2.38.33.38
Email: ykuz...@rocketsoftware.com
Web: www.rocketsoftware.com
От: Karl Williamson pub...@khwilliamson.com
Отправлено: 13 ноября 2014 г. 10:19
Кому: Yaroslav Kuzmin
Копия: perl-mvs; Perl5 Porters
Тема: Re: НА: НА: updated EBCDIC porting status
...@rocketsoftware.com
Web: www.rocketsoftware.com
От: Karl Williamson pub...@khwilliamson.com
Отправлено: 9 ноября 2014 г. 23:00
Кому: Yaroslav Kuzmin
Тема: Re: НА: updated EBCDIC porting status
On 11/06/2014 05:41 AM, Yaroslav Kuzmin wrote:
I build project perl
On 11/09/2014 11:00 AM, Karl Williamson wrote:
On 11/06/2014 05:41 AM, Yaroslav Kuzmin wrote:
I build project perl-5.21.6 (git commit 70291a84)
: perl -v
This is perl 5, version 21, subversion 6 (v5.21.6) built for os390
https://drive.google.com/file/d/0B5PTttxwo7qANjkxdl8zREZfNTQ
On 10/24/2014 01:59 AM, Yaroslav Kuzmin wrote:
I build perl-5.21.6 (git commit 3e2d781a)
~/ussport/perl/perl-5.21.5 : ./perl -v
This is perl 5, version 21, subversion 6 (v5.21.6) built for os390
But to successfully compile I had to change two files. Makefile.SH and
ext/mro/mro.xs
On 10/22/2014 12:02 PM, Karl Williamson wrote:
On 10/21/2014 05:51 AM, Yaroslav Kuzmin wrote:
I build perl 5.21.5 (git commit e833c9b8, branch smoke-me/khw-ebcdic,
but I took a file hints/os390.sh from branch khw/ebcdic)
~/ussport/perl/perl-5.21.5 : ./Configure -DDEBUGGING ( without
module
On 10/21/2014 05:51 AM, Yaroslav Kuzmin wrote:
I build perl 5.21.5 (git commit e833c9b8, branch smoke-me/khw-ebcdic, but I
took a file hints/os390.sh from branch khw/ebcdic)
~/ussport/perl/perl-5.21.5 : ./Configure -DDEBUGGING ( without module mro)
- OK.
That branch was just to make
mro is currently split into mro.c and a module in ext/mro. This
arrangement isn't working in os390, EBCDIC, because of a loader issue.
The EBCDIC porter, Yaroslav Kuzmin, can get it to work in os390 by
adding the contents of ext/mro.c to ./mro.c, and making ext/mro.xs into
a dummy.
There are just a few problems left in the port of the Perl core to
os390. Most of them are test issues.
This turns out to be the case with the -DDEBUGGING option causing a huge
make test output to be generated. This was caused by a test turning on
tracing by setting $^D, which it avoids on
On 10/14/2014 06:58 AM, Ricardo Signes wrote:
* Yaroslav Kuzmin ykuz...@rocketsoftware.com [2014-10-14T05:03:10]
P.S. Last week I sent a email to Peter, but he has not written anything in
the mailing list.
Peter has been traveling overseas, so he may be experiencing a bit of delay. I
believe
On 10/14/2014 03:03 AM, Yaroslav Kuzmin wrote:
Number of passed tests increased to 94%.
Note that this result is not from the latest from me that Yaroslav had
tried, but from a previous version. The latest should up the percentage
passed to 95+%.
...@rocketsoftware.com
Web: www.rocketsoftware.com
От: Karl Williamson pub...@khwilliamson.com
Отправлено: 9 октября 2014 г. 23:56
Кому: Yaroslav Kuzmin; Peter Rabbitson; perl5-port...@perl.org;
perl-mvs@perl.org
Тема: Re: НА: НА: НА: Bug Report z/OS
On 10/09/2014 11:06
On 10/09/2014 07:18 AM, Yaroslav Kuzmin wrote:
I build perl with option DEBBUGGING.
git commit 5902e2e4
perl -v
This is perl 5, version 21, subversion 2 (v5.21.2) built for os390
Copyright 1987-2014, Larry Wall
MVS (OS390) port by Mortice Kern Systems, 1997-1999
log file in EBCDIC encoding.
.
Yaroslav Kuzmin
Developer C/C++ ,z/OS , Linux
3 Zhukovskiy Street · Miass, Chelyabinsk region 456318 · Russia
Tel: +7.922.2.38.33.38
Email: ykuz...@rocketsoftware.com
Web: www.rocketsoftware.com
От: Karl
Those logs showed me a fairly basic flaw which could be causing several
of the remaining failures. In the meantime, I have fixed other bugs
based on code reading, and looking at previous logs.
So there is a new version to try,
http://perl5.git.perl.org/perl.git/tree/refs/heads/khw/ebcdic
On 10/07/2014 04:29 AM, Peter Rabbitson wrote:
My main concerns is that the logs are written out in EBCDIC, and I am
not sure if you will be able to properly read them if they are gzip-ed
on the very same mainframe hardware. To clear this up I am attaching a
smaller test-log in the form of:
On 08/15/2014 03:09 AM, Yaroslav Kuzmin wrote:
git commit 09861a101b2aabfee2ad22840d97fd16e04c03f0
Author: Karl Williamson k...@cpan.org
Date: Tue Jul 29 20:47:15 2014 -0600
Make test
Yaroslav Kuzmin
On 08/15/2014 03:35 AM, Yaroslav Kuzmin wrote:
Hi gues,
A method of converting source project with a script
(translate_to_native.pl) , is not convenient, since it requires first
compile the project without the support of UTF-EBCDIC, and then convert
the source project with the aid of the script
On 07/24/2014 09:39 PM, Yaroslav Kuzmin wrote:
~/ussport/perl/perl-5.20 : ./perl -v
This is perl 5, version 21, subversion 2 (v5.21.2) built for os390
Thanks, this enabled me to find and fix some bugs, including one that
has repercussions in several places, and the next iteration should
On 07/07/2014 04:18 AM, Yaroslav Kuzmin wrote:
git commit 69c0f27f128a54f4769f18fa9e03e4b29f45aff2
~/ussport/perl/perl-5.20 : ./perl -v
This is perl 5, version 21, subversion 2 (v5.21.2) built for os390
Copyright 1987-2014, Larry Wall
MVS (OS390) port by Mortice Kern Systems, 1997-1999
files in the failure :
comp/*.t cmd/*.t run/*.t io/*.t re/*.t opbasic/*.t op/*.t uni/*.t
On 06/30/2014 03:12 AM, Yaroslav Kuzmin wrote:
git commit 168f82262ef7b8feb200e1c5d09f747414896cf0
Author: Karl Williamson k...@cpan.org
Date: Fri Jun 27 16:31:41 2014 -0600
~/ussport/perl/perl-5.20
On 06/30/2014 01:30 PM, Karl Williamson wrote:
The problem here is probably something simple, easy to fix once we find
it. This is an easy method that should find what the first bad regex
is, anyway:
cd t
./perl -Dr -Ilib TEST base/*.t /dev/tty
In the unlikely event that doesn't generate
On 06/26/2014 12:55 AM, Yaroslav Kuzmin wrote:
perl/perl-5.20.0 : ./perl -v
This is perl 5, version 19, subversion 12 (v5.19.12) built for os390
The version now in
http://perl5.git.perl.org/perl.git/shortlog/refs/heads/khw/ebcdic
has some fixes that should clean up these failures
От: Karl Williamson pub...@khwilliamson.com
Отправлено: 23 июня 2014 г. 10:19
Кому: Yaroslav Kuzmin; Ricardo Signes
Копия: carr...@nationwide.com; perl-mvs@perl.org
Тема: Re: НА: НА: НА: НА: [perl@rjbs.manxome.org: platform support]
On 06/20/2014 05:41 AM, Yaroslav
456318 · Russia
Tel: +7.922.2.38.33.38
Email: ykuz...@rocketsoftware.com
Web: www.rocketsoftware.com
От: Karl Williamson pub...@khwilliamson.com
Отправлено: 23 июня 2014 г. 10:19
Кому: Yaroslav Kuzmin; Ricardo Signes
Копия: carr...@nationwide.com; perl-mvs
On 06/20/2014 05:41 AM, Yaroslav Kuzmin wrote:
(07:39) RS12 : PDKUZM | ~/ussport/perl/perl-5.20 : perl -v
This is perl 5, version 19, subversion 12 (v5.19.12) built for os390
Ok. That is somewhat behind. There have been several fixes that should
improve things. The latest is at
On 06/19/2014 04:38 AM, Yaroslav Kuzmin wrote:
On z/OS v1r13 using the compiler XLC .
Perl-5.20 build without module mro.
P.S. The company I work not only with perl, but also entry for other projects.
Yaroslav Kuzmin
On 06/19/2014 11:14 AM, Karl Williamson wrote:
On 06/19/2014 04:38 AM, Yaroslav Kuzmin wrote:
On z/OS v1r13 using the compiler XLC .
Perl-5.20 build without module mro.
P.S. The company I work not only with perl, but also entry for other
projects
On 06/10/2014 01:23 AM, Yaroslav Kuzmin wrote:
P.S. Why such an attachment to the system smoke ?
test logs and so I can provide.
I don't understand this question. Hopefully it was addressed to someone
else.
driven from a Linux server with linux
and git access
It should work
Sandra
The new branch, rebased off of blead, at
http://perl5.git.perl.org/perl.git/shortlog/refs/heads/khw/ebcdic
should fix the build problem your log shows.
From: Yaroslav Kuzmin ykuz...@rocketsoftware.com
To: Karl Williamson
101 - 200 of 226 matches
Mail list logo
