Thu Mar 08 21:06:15 2012: Request 75636 was acted upon. Transaction: Ticket created by dancec...@gmail.com Queue: PAR Subject: PAR::Packer Windows installation error (and suggested fix) Broken in: (no value) Severity: (no value) Owner: Nobody Requestors: dancec...@gmail.com Status: new Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=75636 >
To Whom It May Concern, First, let me say thanks for PAR::Packer, it's working great for me. I ran into a bit of a snag when I tried installing PAR::Packer on Windows via CPAN: windres -F pei-i386 -i winres\pp.rc -o winres\pp.res windres -o ppresource.coff winres\pp.res windres: unexpected version string length 68 != 32 + 8 dmake: Error code 129, while making 'ppresource.coff' dmake.EXE: Error code 255, while making 'subdirs' RSCHUPP/PAR-Packer-1.013.tar.gz C:\Devel\lib\strawberry\c\bin\dmake.EXE -- NOT OK Running make test Can't test without successful make Running make install Make had returned bad status, install seems impossible Failed during this command: RSCHUPP/PAR-Packer-1.013.tar.gz : make NO I'm running Windows 7 (32-bit) and Strawberry Perl 5.14.2.1, and I used "cpan" "install PAR::Packer" for attempting the installation. To fix the problem, I deleted the boilerplate from "pp.rc": VS_VERSION_INFO VERSIONINFO FILEVERSION 0,0,0,0 PRODUCTVERSION 0,0,0,0 FILEFLAGSMASK VS_FFI_FILEFLAGSMASK FILEFLAGS PP_MANIFEST_FILEFLAGS FILEOS VOS_NT_WINDOWS32 FILETYPE VFT_APP FILESUBTYPE VFT2_UNKNOWN BEGIN BLOCK "StringFileInfo" BEGIN BLOCK "000004B0" BEGIN VALUE "CompanyName", " \0" VALUE "FileDescription", " \0" VALUE "FileVersion", "0.0.0.0\0" VALUE "InternalName", " \0" VALUE "LegalCopyright", " \0" VALUE "LegalTrademarks", " \0" VALUE "OriginalFilename", " \0" VALUE "ProductName", " \0" VALUE "ProductVersion", "0.0.0.0\0" END END BLOCK "VarFileInfo" BEGIN VALUE "Translation", 0x00, 0x04B0 END END After that, I could run "dmake test" and "dmake install" without any problems, and packaging an application with "pp" worked very nicely. It's my first time using PAR::Packer, and I'm pleased to report that (besides the build issue) it's suits my needs well. Regards, Dan Cecile