From pryrt:
When I look at an example from the testers, like this one, I do notice that it says "Output from 'C:\Strawberry\c\bin\gmake.exe test':" -- that is, I don't think that the automated testers necessarily do the gmake install -- they might just do the gmake test ... in which case, they wouldn't see the gmake install failure, and thus wouldn't report that failure.
I will just echo that this is a fine job of investigating, good clear thinking and asking the right questions. I didn't occur to me that testers don't send in data on the results of (g)make install, so I was left puzzling about what was uniquely wrong with my setup.
One question now remained for me: where does create-modulino.pl come from? In other words, we've seen that the postamble shell code won't work on a MSWin box, but how does it work on Linux/Unix? So, I tried it out, and it's b0rken on Linux too, because create-modulino.pl doesn't exist:
destdir=; \
test -n "$destdir" && destdir="-d $destdir"; \
create-modulino.pl -m Module::ScanDeps::FindRequires \
-a find-requires $destdir -b /usr/local/bin
/bin/sh: 3: create-modulino.pl: not found
make: *** Makefile:1007: install Error 127
— Soren
Sep 27, 2025 at 17:33 UTC
In reply to Re^5: create-modulino.pl appears in a CPAN module Makefile.PL, and nukes the install retval
by Intrepid
in thread create-modulino.pl appears in a CPAN module Makefile.PL, and nukes the install retval
by Intrepid
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |