You haven't been here for a while, welcome back! :)

So you know

> likely deeper issues at play

Multiple conflicting Perl installations and messed up environment variables are a recurring theme in many posts of this particular monk.

Compare last 2 years of threads by this OP (click search)

Rolf wrote:

Multiple conflicting Perl installations and messed up environment variables are a recurring theme in many posts of this particular monk.

That's not entirely valid and really a bit unfair. Your characterization might lead to other monks ignoring my posts, and that's a pretty negative effect in my view of how perlmonks should be.

I am capable of learning from past mistakes and absorbing advice from the monks, thus the frequency of these "weird problems" has dropped drastically.

What's accurate and true is that my Windows systems are (mostly) working fine and I am aware of and in control of all env vars*, $PATH, etc. I've stopped using StrawberryPerl entirely and am focused completely on CygPerl at present. I also use Gnu/Linux systems and usually compare problems when they come up to see if I can reproduce the difficulty on Linux.

* My CPAN module helps me with that.

    – Soren
May 02, 2026 at 16:52 UTC

I also use Gnu/Linux systems and usually compare problems when they come up to see if I can reproduce the difficulty on Linux.

Did you do that for the problem in the OP? What was the conclusion?

---

🦛

> I am capable of learning from past mistakes

Well, actions speak louder than words. 🤷🏻‍♂️

Maybe convince us by replying to those who are still trying to help you?

Cheers Rolf
_{(addicted to the Perl Programming Language :)
see Wikisyntax for the Monastery}

I think part of it is the use of --self-contained, while also not having the core modules available maybe due to overriding PERL5LIB and Perl itself not supplying the correct path, maybe due to running a Win32 Perl while expecting a Cygwin Perl.