Rolf wrote:

I remember that you were running two Perl installations in parallel on the same system and the ENV pointed to both.
Is that still the case?

That isn't exactly pertinent to the question I asked here, Rolf, but I'll overlook that. I've got my ENV tightly controlled now, with only CygwinPerl or StrawberryPerl, and all the tools and ENV settings associated with each, invoked at any one time. I'm miles ahead of where I was back then (a few weeks ago). I'm using berrybrew (for now) with StrawberryPerl(s) and I even went so far as to brutally do rm -rf C:/Perl to my old StrawberryPerl (the one I wrote about destroying by trying to install an update .msi over it).

I still use the vendor supplied (system) Perl in Cygwin. Several of our fellow monks have noted that they ignore that Perl, and only use Perls they've built on-site. I am not sure where the disdain for the Cygwin-supplied Perl comes from. Maybe some of these monks will read this and write about 'why the strong preference.'

One more thing that might be a bit controversial. I run my Strawberry (Windows) operations in a bash shell. I just cannot abide the CMD / PS Terminal even if they did add CTRL-C and CTRL-V to it. I hate it. What I do is possible by having /usr/bin at the very end of my Cygwin bash $PATH. It's working very well, whether using cpan clients like cpanm or cpan or cpanp, or dropping into a new shell session to run perl Makefile.PL and trace everything that's happening in the build of a non-trivial module (there's almost never anything broken, I just like to watch the scrolling text, it's relaxing ;-)