For what it's worth, I'm attempting to compile PAR 0.76_99 on Windows 2000, and wanted to report back. I'm currently using ActivePerl 5.6.1.635 (for .exe building reasons).
Upon running the "perl Makefile.PL", it suggested I needed nmake and automatically began to download it (this is in contradiction of the
README.txt that says I'll be prompted with a choice). However, the
download failed with an error resolving "download.microsoft.com",
even though the URLs the error spit out were accessible in my
browser without a problem (no proxy, using firewall, perl.exe
has full privileges). Installing nmake went fine, and I threw
them into /perl/bin, as per the suggestion that the Makefile.pl
would do the same thing.
Next up, I was missing required versions of Archive::Zip and PAR::Dist, which the Makefile.pl prompted me to download and install - I chose "sure", and it launched a CPAN shell and not the desired PAR. Running "ppm3 install Archive::Zip" and "ppm3 install PAR::Dist" worked fine.
After that, everything went fine except for "nmake test", which skipped some tests for an unknown reason:
t/0-signature.......ok, 1/1 skipped: Next time around, consider install Module::Signature, so you can verify the integrity of this distribution.
t/1-basic...........ok, 1/8 skipped: unknown reason All tests successful, 2 subtests skipped.
Files=2, Tests=9, 2 wallclock secs ( 0.00 cusr + 0.00 csys = 0.00 CPU)
The "nmake install" worked fine. Running
pp -e "use utf8; /\x{100}/i;"
however, gave me the following error from parl.exe: "The dynamic link library MSVCR70.dll could not be found in the specified path", which it then listed a number of directories; no executable was created. That file is a Microsoft C Runtime Library [1], and only exists under my system under an OpenOffice.org directory. I suspect nmake required or binded that necessity to the newly generated PAR executables. Dragging the OOo version to /perl/bin/ (one of the directories in my PATH, and reported by the error) allowed the above command to run successfully. But, now, I worry: does this mean that my generated apps will be an additional 300k in size (being the size of the OOo version)?
With all the above out of the way, the a.exe (1,341,329k) created using nmake'd PAR 0.76_99, ActiveState 5.6.1.635, and an unmodified utf8_heavy.pl, ran fine from the command line with no complaints.
[1] http://www.liutilities.com/products/wintaskspro/dlllibrary/msvcr70/
-- Morbus Iff ( i put the demon back in codemonkey ) Culture: http://www.disobey.com/ and http://www.gamegrene.com/ Spidering Hacks: http://amazon.com/exec/obidos/ASIN/0596005776/disobeycom icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus
