I can build and fixing problems, give full log "make test".
The main difference with z/OS the encoding EBCDIC and not full support of POSIX. Many of the tests are created without considering the peculiarities EBCDIC. example: $x = "A"; ok( $x == chr(65) ," Test : A" ); test incorrect for EBCDIC . or test sort priority EBCDIC ASCII a..z 0..9 A..Z A..Z 0..9 a..z all test sort incorrect. P.S. I work with the source perl directly on the mainframe, but I do not use scripts perl )). ------------------------------------------------------------------------ Yaroslav Kuzmin Developer C/C++ ,z/OS , Linux 3 Zhukovskiy Street · Miass, Chelyabinsk region 456318 · Russia Tel: +7.922.2.38.33.38 Email: [email protected] Web: www.rocketsoftware.com ________________________________________ От: [email protected] <[email protected]> от имени Jarkko Hietaniemi <[email protected]> Отправлено: 10 апреля 2014 г. 2:18 Кому: demerphq; Yaroslav Kuzmin Копия: [email protected]; [email protected]; Perl5 Porters Тема: Re: Fwd: Re: USSP-37: Info Request for Perl Fwd: EBCDIC support is onthe chopping block On Wednesday-201404-09, 13:53, demerphq wrote: > On 9 April 2014 19:09, Yaroslav Kuzmin <[email protected]> wrote: >> Perl-5.16 correctly configured, compiled. All Testes - 75 % - successful. > > Hi Yaroslav, thanks a lot. But... We really need to see the failures. > > Also is rocketsoftware able to set up a smoker for us? If we got > regular smoke reports from an automated build process then we would be > a lot less reluctant to continue support. > > Yves > To elaborate... there are different levels/ways you can help: Level 1: build and send us the full "make test" output. Level 2: build and try yourself fixing some problems, and send the fixes to perl5-porters. Level 3: like Level 2 but actively involve perl5-porters. As the name says... Level 4: set up an automatic periodic build ("a smoker") that periodically pulls the latest perl5 source, and attempts building it (possibly across different build configurations), and the build reports are emailed to perl5-porters. Again, perl5-porters can advise in the "smoke setup".
