Re^4: PAR::Packer fails to install

[syphilis]

C:\Perl\site\lib\auto\MinGW\bin\windres.exe

I don't think that's Strawberry's windres.exe.
I expect that the correct windres.exe is in C:/STRAWB~1/c/bin.

You should be seeing:

supported targets: pe-x86-64 pei-x86-64 pe-bigobj-x86-64 elf64-x86-64 
+elf64-l1om elf64-k1om pe-i386 pei-i386 elf32-i386 elf32-iamcu elf64-l
+ittle elf64-big elf32-little elf32-big plugin srec symbolsrec verilog
+ tekhex binary ihex

In fact, it may well be that the compiler in use is C:\Perl\site\lib\auto\MinGW\bin\gcc.exe - which might explain the other issues with inline.h.
(You might need to fiddle with your PATH ;-)

Cheers,
Rob

[BernieC]

First, I don't have a c:\perl. Second, I ran windres directly out of the Strawberry\c\bin directory and got:

windres: supported targets: pe-x86-64 pei-x86-64 pe-bigobj-x86-64 elf6
+4-x86-64 elf64-l1om elf64-k1om pe-i386 pei-i386 elf32-i386 elf32-iamc
+u elf64-little elf64-big elf32-little elf32-big plugin srec symbolsre
+c verilog tekhex binary ihex
Report bugs to <http://www.sourceware.org/bugzilla/>

and my PATH is

C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\WINDOWS\sy
+stem32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\Window
+sPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;D:\BIN;;C:\Program Fil
+es (x86)\Bitvise SSH Client;C:\Program Files (x86)\Intel\Intel(R) Man
+agement Engine Components\DAL;C:\Program Files\Intel\Intel(R) Managem
+ent Engine Components\DAL;C:\Strawberry\c\bin;C:\Strawberry\perl\site
+\bin;C:\Strawberry\perl\bin;C:\Users\win10\AppData\Local\Microsoft\Wi
+ndowsApps;d:\perl;D:\Perl\rcs\bin\win32;D:\LaTeX\texlive\2019\bin\win
+32;C:\Program Files (x86)\EaseUS\Todo Backup\bin\x64\

I'm not sure where this leaves me but I have a strange/amazing result. I tried, as recommended, "cpanm -v PAR::Packer" and look at what I got:

Successfully installed PAR-Packer-1.050
Installing C:\STRAWB~1\perl\site\lib\MSWin32-x64-multi-thread\.meta\PA
+R-Packer-1.050\install.json
Installing C:\STRAWB~1\perl\site\lib\MSWin32-x64-multi-thread\.meta\PA
+R-Packer-1.050\MYMETA.json
1 distribution installed

and confirmed with:

C:\Strawberry\c\bin>perldoc PAR::Packer
NAME
    PAR::Packer - PAR Packager

DESCRIPTION
    This module implements the App::Packer::Backend interface, for
    generating stand-alone executables, perl scripts and PAR files.

    Currently, this module is used by the command line tool pp interna
+lly,
    as well as by the contributed contrib/gui_pp/gpp program.

    Since version 0.97 of PAR, this module and its related tools such 
+as
    "pp" have been stripped from the PAR distribution and are now
    distributed as the "PAR-Packer" distribution so that PAR users nee
+d not
    necessarily have a C compiler.
....

I wonder what cpanm does that plain old cpan didn't??

[syphilis]

First, I don't have a c:\perl

You are right.
The post to which you have replied was in response to GrandFather's issue - which was a totally separate issue to the one that you (and I) experienced.

I wonder what cpanm does that plain old cpan didn't??

Interesting that cpanm gets the job done. It works for me, too.
I don't know how it avoids the problem that the cpan utility encounters, and I couldn't spot any bug reports that seemed relevant.
I was thinking that it must be a bug in the cpan utility, but that is NOT so - because when I try to build PAR-Packer-1.050 the ol' fashioned manual way (without using the cpan utiity) I get the same 6 test failures.
It's a bug in PAR::Packer's t/20-pp.t script, and the use of the cpanm utility is currently the only way of working around that bug.

This bug in PAR-Packer should be reported.
We know that it's limited to Windows 10. At least we know it doesn't afflict Windows 7.
We probably ought to determine the earliest version of PAR::Packer that exhibits the bug.
I don't have time for this right now ... perhaps I will later on ... or perhaps someone else can follow this through.

Cheers,
Rob