| [reply] |
latest attempt at cpan install PAR::PACKER
[32mCPAN: Term::ANSIColor loaded ok (v4.02)[0m
[32mCPAN: Win32::Console::ANSI loaded ok (v1.06)[0m
[32mCPAN: Storable loaded ok (v2.45)[0m
[32mReading 'C:\Users\U357750\AppData\Local\.cpan\Metadata'[0m
[32m Database was generated on Thu, 31 Jul 2014 12:06:24 GMT[0m
[32mRunning install for module 'PAR::Packer'[0m
[32mCPAN: Digest::SHA loaded ok (v5.85)[0m
[32mCPAN: Compress::Zlib loaded ok (v2.063)[0m
[32mChecksum for C:\Users\U357750\AppData\Local\.cpan\sources\authors
+\id\R\RS\RSCHUPP\PAR-Packer-1.019.tar.gz ok[0m
[32mCPAN: Archive::Tar loaded ok (v1.96)[0m
[32mCPAN: File::Temp loaded ok (v0.2304)[0m
[32mCPAN: YAML::XS loaded ok (v0.41)[0m
[32mCPAN: Parse::CPAN::Meta loaded ok (v1.4409)[0m
[32mCPAN: CPAN::Meta loaded ok (v2.132830)[0m
[32mCPAN: Module::CoreList loaded ok (v3.03)[0m
[32mConfiguring R/RS/RSCHUPP/PAR-Packer-1.019.tar.gz with Makefile.PL
+[0m
Checking if your kit is complete...
Looks good
Generating a dmake-style Makefile
Writing Makefile for par.exe
Writing MYMETA.yml and MYMETA.json
Generating a dmake-style Makefile
Writing Makefile for PAR::Packer
Writing MYMETA.yml and MYMETA.json
[32m RSCHUPP/PAR-Packer-1.019.tar.gz
C:\Perl64\bin\perl.exe Makefile.PL INSTALLDIRS=site -- OK[0m
[32mRunning make for R/RS/RSCHUPP/PAR-Packer-1.019.tar.gz[0m
cp lib/PAR/StrippedPARL/Base.pm blib\lib\PAR\StrippedPARL\Base.pm
cp lib/PAR/Filter/Bleach.pm blib\lib\PAR\Filter\Bleach.pm
cp lib/PAR/Filter/PodStrip.pm blib\lib\PAR\Filter\PodStrip.pm
cp lib/PAR/Filter/PatchContent.pm blib\lib\PAR\Filter\PatchContent.pm
cp lib/PAR/Filter/Obfuscate.pm blib\lib\PAR\Filter\Obfuscate.pm
cp lib/App/Packer/PAR.pm blib\lib\App\Packer\PAR.pm
cp lib/PAR/Filter.pm blib\lib\PAR\Filter.pm
cp lib/PAR/Packer.pm blib\lib\PAR\Packer.pm
cp lib/PAR/Filter/Bytecode.pm blib\lib\PAR\Filter\Bytecode.pm
cp lib/pp.pm blib\lib\pp.pm
C:\Perl64\bin\perl.exe par_pl2c.pl my_par_pl < ..\script\par.pl > my_p
+ar_pl.c
C:\Perl64\bin\perl.exe sha1.c.PL
gcc -c -s -O2 -DWIN32 -DWIN64 -DCONSERVATIVE -DPERL_TEXTMODE_SCRIPTS -
+DUSE_SITECUSTOMIZE -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -DUSE_
+PERLIO -fno-strict-aliasing -mms-bitfields -I"C:\Perl64\lib\CORE" -
+DPARL_EXE=\"parl.exe\" -s -O2 main.c
windres -i winres/pp.rc -o ppresource.coff --input-format=rc --output-
+format=coff --target=pe-x86-64
[32m RSCHUPP/PAR-Packer-1.019.tar.gz[0m
[31m C:\Perl64\site\bin\dmake.exe -- NOT OK
thanks for your help | [reply] [d/l] |
However cpan is configured on your system there is not much here to go on, a manual install may be different. Here is the result of cpan PAR::Packer on my one of my Windows systems:
I recently outlined part of the reason why I gave up on ActiveState Perl. In short, if you're developing Perl on Microsoft Windows make life easy for yourself and use Strawberry Perl. You won't regret it. You'll note that the same advice comes from many other people in their responses to several of your module installation threads.
| [reply] [d/l] [select] |
| [reply] |
I had previously tried to install Win32::Exe both through ppm and CPAN with no success.
| [reply] |
| [reply] |
If you're having problems installing Win32::Exe on Activestate via PPM, I would postulate that your install is broken. Weather this is the fault of ActiveState or something on your machine is still to be determined.
Also, 64B Activestate perl is... well, last time I messed with it "goofy" would be a generous description. Getting the compiler and such to work with it was beyond my patience to sort out. I've resigned to use 32B ActiveState until I make the jump to 5.20, at which point I'll probably switch to Strawberry. 32B ActiveState perl has given me no trouble generating packaged executeables once I sorted out installing Par::Packer, which I still think required some hoop-jumping as I recall. This was a couple of years ago though, as I updated to 5.16 shortly after it came out, and haven't moved since.
I say this as someone who has used ActiveState for the past 5 years or so. While I freely admit that more may have considerably more time with it, I like to think I'm not speaking from a place of ignorance.
| [reply] |