Re: problems installing PAR::Packer (pp) on Windows 7

[dasgar]

in reply to problems installing PAR::Packer (pp) on Windows 7

Use the PPM utility to install MinGW and dmake from ActiveState's repository. Without these, you'll only be able to install those modules from CPAN that are pure Perl code. Any modules that need to be compiled (such as those using XS) will require that you have a compiler and make utility.

If you're using a 64-bit version of ActivePerl, I think that there might be a few more steps needed, but I'm not 100% sure about that.

[marto]

There's no 64bit MinGW available from Active State: http://code.activestate.com/ppm/MinGW/. Another reason why Strawberry Perl (reason being it comes with all this and more as standard) is the perl I choose for Windows.

[Discipulus]

hi marto, i had switched to strawberry perl as default, i'm very pleased with it.
But me too i'm haveing trouble with the pp: PAR::Packer was installed only with the force install command and pp too.
Then pp result as not properly run anyway.
I found some article but i'm not sure if there is a solution.

I'll post here any progress.

L*

[marto]

Strange, I run Strawberry Perl and had no problems installing pp or running the generated packages. Perhaps more details would help.

[evgen-i]

I am trying to install using strawberry perl, no success so far. Here is the message I get:

pl2bat.bat blib\script\scandeps.pl
Can't execute /cygdrive/c/strawberry/perl/bin/pl2bat.bat.
dmake.exe:  Error code 129, while making 'blib\script\scandeps.pl'

I am running this in the standard shell, not in cygwin, so I don't get where /cygdrive comes from.

[Anonymous Monk]

For 64-bit ActivePerl you need http://sourceforge.net/projects/perlmingw/#Citrus GCC (mingw-w64) for Perl or make utility and C compiler on 64-bit Windows ( see How to install CPAN modules into ActivePerl )

I don't know why ActiveState doesn't make available http://mingw-w64.sourceforge.net/ via ppm

[tobias_hofer]

Hello,

compiling the GNU compiler sources for 64-bit is not that easy, the same is for compiling as a cross-compiler 32bit/64bit.
It took me a few days and finally I gave up.
I took the binary version for testing: http://tdm-gcc.tdragon.net.
Using a 64bit compiler lead to much trouble as I forgot that a 64bit compiler comes with different size of types :-)

However, I am compiling perl modules for perl on Windows 7 (64bit system) with a 32bit compiler and didn't faced any problems so far.
I have also tested 64bit perl versions and I have come to the point
that there are not as much perl modules available as in the standard installation.
In example the Win32::SerilPort module was not available for 64bit (at that time).
Compiling modules designed for 32bit with 64bit compiler is also leading to an shouting compiler.

So is a 64bit compiler really needed?
Yet I have not tested the Microsoft nmake tool chain with 64bit option, might by worth giving a try.

IMHO modules are best installed with the given maintenance tools of ActiveState or Strawberry.
By manual installation you have to take care for version dependencies for yourself - this is no fun ;-)

[gmock]

I found a solution to this problem which worked for me. I'll share it here in case it helps anyone else.

My OS is 64-bit Windows 7. I installed 32-bit Perl v5.16.3 from ActiveState. I managed to get PAR::Packer installed in the following manner.

% cpan PAR::Packer

The MinGW compiler and dmake utility installed correctly. Several other packages installed correctly. But Win32::Exe failed to install. So, I did this ...

% ppm install Win32::Exe

That gets Win32:Exe installed correctly. Next ...

% cpan PAR::Packer

Now I can use the pp command normally. Hope this is useful.

-George