Front page | perl.perl5.porters |
Postings from February 2014
Re: perl on z/OS
Thread Previous
|
Thread Next
From:
Craig A. Berry
Date:
February 23, 2014 22:04
Subject:
Re: perl on z/OS
Message ID:
CA+vYcVwfsSoj4i=3kMD1DcSXdBnJk-LnCc_tduNEJ-fwK7+WGQ@mail.gmail.com
On Fri, Feb 21, 2014 at 6:05 PM, James E Keenan <jkeen@verizon.net> wrote:
> On 2/21/14 1:16 PM, Kevin Shaw wrote:
>>
>> Hi Craig,
>>
>> Perl changes are attached. Please let me know if I should post them
>> somewhere.
>
>
>>
>> Kevin Shaw
>> Managing Director, R&D
>> Rocket Software
>> 77 4th Avenue, Suite 100 EURO Waltham, MA 02451 EURO USA
>> t: +1.781.684.2150 EURO e: kevin.shaw@rocketsoftware.com EURO w:
>> www.rocketsoftware.com
>>
>>
>>> On 10/29/2013 11:53 AM, Kevin Shaw wrote:
>>>>
>>>>
>>>> We have Perl 5.16.2 ported and tested on z/OS.
>>>> What are my next steps to getting our source back into the tree?
>
>
> For research purposes and (some definition of) fun, I created a branch from
> origin/maint-5.16 and applied Kevin Shaw's patches thereto. I then tried to
> configure and build as follows:
>
> sh ./Configure -des -Dusedevel
> make
>
> The build did not succeed. I am attaching gzipped output of 'script' for
> each process. Note that I don't claim my approach is optimal or even valid.
Thanks for doing that, James. I was thinking about taking a swing at
that very thing but I'm quite glad you beat me to it. I had a brief
look at applying the patches to blead and the first 4 I tried don't
apply at all.
In case it's not obvious, both of the following things would need to
happen for these patches to get into the Perl core:
1.) They need updating to apply to blead, the development stream
currently leading up to 5.20. A snapshot of the latest development
release is at <http://perl5.git.perl.org/perl.git/snapshot/bcbcbdda9f0fca0bc4a9c9c2263f499fbe2386a3.tar.gz>.
2.) The build and test must still work on ASCII systems; maintaining a
separate fork that only works on z/OS is something that could be done
by someone else somewhere else, but I can't imagine anyone interested
in trying to do that as part of Perl core development.
No one is obligated to do these things, but doing so would be one
visible sign that people interested in continued EBCDIC support in the
core are actually doing something about it. It would only be first
steps, as ongoing signs of testing would still need to materialize. A
perfectly reasonable alternative is that people can simply rely on the
Rocket Software port of 5.16.2 indefinitely and have another decade or
two of good Perl work on z/OS ahead of them.
Thread Previous
|
Thread Next