I just pushed to git a work-around for the File::Map bug which will allow the new mmap code to work with the File-Map-0.46 release. I've also gotten a message from the File::Map developer closing the ticket I opened with the problem so an official fix should be available shortly.
In the interest of more comprehensive testing of the new implementation, I have added File::Map 0.46 as a required dependency of PDL for CPAN Testers. This will only affect builds using automated tools. If you build by hand, and force the build, the legacy mmap code should be used and will work (if it was on a previously supported platform type---POSIX only!). Let me know if anything needs tweaking or add any notes or other updates you would like to see for a CPAN developers release. My plan is to push it to PAUSE/CPAN this Friday. --Chris On Wed, Apr 4, 2012 at 10:18 AM, Sisyphus <[email protected]> wrote: > > ----- Original Message ----- From: "chm" > > >>> I think the only other thing that Windows users (using other than >>> perl-5.12) would have to do is to force install PerlIO::Layers. I'll see >>> if I can improve on its Windows-handling capabilities. >> >> >> Ok. I'm not sure what the specfic requirement for the >> PerlIO::Layers for the implementation of File::Map. >> Maybe it could be made an optional one. In the meantime, >> I'm planning to work around the sys_map bug by adding a >> pdl_sys_map() internal to PDL for us to use until the >> fix is implemented in the File::Map distribution. > > > I've submitted a bug report about my PerlIO-Layers problems: > https://rt.cpan.org/Ticket/Display.html?id=76299&results=db599ee120c1f692a1d714ddd7a34a4d > > (Note that my earlier assertion in this thread that "On 5.14.0, 32-bit fails > its tests but 64-bit passes" was incorrect - it fails on both. > > I suspected the failures might be related to the version of PerlIO that was > installed. > 5.8.9 (with PerlIO-1.05) passes. > 5.10.0 (with PerlIO-1.04) fails tests 50, 55, 60 and 65 of 10-basics.t. > 5.12.0 (with PerlIO-1.06) passes. > 5.14.0 & 5.15.9 (both with PerlIO-1.07) both fail test 30 of 10-basics.t. > > So I spent some time hacking up a PerlIO-1.06 for my perl-5.14.0 ... but it > made no difference. (Coodabeen a bad hack, but ;-) > > Most of my day has been spent trying to restore my perl-5.10.0 that was > built using MSVC++ 7.0. > Somewhere along the way of installing/updating dependencies for File::Map it > got broken to the extent that @INC no longer includes perl/site/lib when > (and only when) I run 'nmake test'. > I got as far as establishing that running under Test::Harness was all that > was needed to create the problem, but couldn't find out why it was > happening. > In the end I just set PERL5LIB to perl/site/lib, and now it's back in @INC > for 'nmake test' :-) > > As regards how far back we want to go wrt to supporting older perl versions, > I suspect we can probably get away with 5.8.1 for a while. > I've struck more than one module that wants to 'use 5.008001;' but can't > recall any that 'use 5.008009;'. > My decision to move from 5.8.0 to 5.8.9 arises from not having any of the > intermediary perls installed. (I think perl-5.8 was unbuildable with MinGW > until about 5.8.8.) > On windows it's not such a big deal as the numbers of people using 5.8.8 or > earlier would be very small - and updating is not such a huge problem. > (Of course we do need to keep in mind the needs of the *nix crowd ... I'm > not all that well qualified in that area.) > > Cheers, > Rob > > > _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
