Hi Autrijus: Good going, I like the concept of PAR. I have not been able to make it work with any of my platforms though (RH 7.x, 8.x, 9.0) and a modified perl (with 64 bit ints).
With 0.70, the install depends upon CPANPLUS which seems to have its own issues. I had to install Module::Signature by hand, as the CPANPLUS bit kept looping over it, saying it wasn't installed, compiling it, and then failing somewhere. A "by-hand" compilation worked, and I installed it. The problem/bug arises now that I have all the pre-requisites in, I do a make against PAR 0.70. [EMAIL PROTECTED] PAR-0.70]# perl Makefile.PL *** ExtUtils::AutoInstall version 0.52 *** Checking for dependencies... [Core Features] - File::Temp ...loaded. (0.13) - Compress::Zlib ...loaded. (1.22 >= 1.14) - Archive::Zip ...loaded. (1.05 >= 1) - Module::ScanDeps ...loaded. (0.19 >= 0.19) - PAR::Dist ...loaded. (0.03 >= 0.03) [Digital signature support] - Module::Signature ...loaded. (0.27 >= 0.25) *** ExtUtils::AutoInstall configuration finished. Writing META.yml Checking if your kit is complete... Looks good Writing Makefile for the par program Writing Makefile for PAR [EMAIL PROTECTED] PAR-0.70]# make cp lib/App/Packer/PAR.pm blib/lib/App/Packer/PAR.pm cp lib/PAR/Heavy.pm blib/lib/PAR/Heavy.pm cp lib/PAR.pm blib/lib/PAR.pm cp lib/PAR/Intro.pod blib/lib/PAR/Intro.pod make[1]: Entering directory `/home/landman/PAR-0.70/myldr' cc -c -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -I/usr/local/lib/perl5/5.8.0/i686-linux-thread-multi-64all/CORE main.c In file included from main.c:14: mktmpdir.c: In function `par_rmtmpdir': mktmpdir.c:169: `my_perl' undeclared (first use in this function) mktmpdir.c:169: (Each undeclared identifier is reported only once mktmpdir.c:169: for each function it appears in.) main.c: At top level: main.c:24: `my_perl' used prior to declaration make[1]: *** [main.o] Error 1 make[1]: Leaving directory `/home/landman/PAR-0.70/myldr' make: *** [subdirs] Error 2 Is this pilot error or a real bug? -- Joseph Landman <[EMAIL PROTECTED]>
