As far as I know we would really like to see you test the most recent development branch.
http://perl5.git.perl.org/perl.git/snapshot/ should give you a tar.gz suitable for building from that corresponds to the latest commit in blead. 5.8.x is *really* old, so test fails against it wont be very useful. On the other hand any information about how *blead* perl behaves is very useful. Thanks a lot for helping out! cheers, Yves On 14 February 2012 15:32, Phipps, Dan <[email protected]> wrote: > Ok, which build/package you want me to try? > > I was looking back at my notes, for a frame of reference, and see I tried > building 5.8.6 on z/OS in 2005. Checking CPAN/ports I see IBM has an > official version of 5.8.7 for z/OS, but there is also a reference to 5.8.1. > > Dan Phipps > Infrastructure Management Consultant > ITO Global Service Delivery > ACS, A Xerox Company > 10309 Wilson Blvd > Blythewood, SC 29016 > p 803-753-6547 > f 803-753-6794 > m 803-223-3770 > > > -----Original Message----- > From: Ricardo Signes [mailto:[email protected]] > Sent: Monday, February 13, 2012 6:31 PM > To: John Goodyear > Cc: Phipps, Dan; Nicholas Clark; [email protected]; [email protected] > Subject: Re: porters wanted: building, testing, patching on z/OS > > * John Goodyear <[email protected]> [2012-02-13T13:35:58] >> How many userids (1, 2) >> Memory required on the z/OS image >> Disk space required to support the perl source, build and testing >> activity >> CPU requirements. i:e: Assuming there isn't an I/O bottleneck, the >> build/test would consume how many processors for how long a period of >> time >> Times of day the development activity would occur. (They need to >> make sure resources are available for other commitments) > > Dan, maybe the first thing you could do for us would be to give some answers > to > the questions here that can be answered through a test build on your system. > > This has the excellent bonus feature of telling us how far a build even gets! > Can you give building a testing a go, and let us know what you can about > resource consumption -- and, of course, let us know how the build goes. > > Hopefully from there we can start figuring out what lies ahead. > > -- > rjbs -- perl -Mre=debug -e "/just|another|perl|hacker/"
