Am 08.12.2010 17:44, schrieb Gregory Seidman:
I wound up solving the problem by setting up a VM for my dev environment
with nothing but what is required. Everything is now working. I expect it
was ActiveState Perl causing problems, but I depend on it for other things
on my workstation.
It's not convenient to use a VM for this purpose. You will have to keep
the VM/host directories in sync and so on.
When I have deduced that ActiveState Perl is suspicious, I would try to
setup a proper build environment on the host. This should have at least
no environment variable that includes anything from AS-perl (or any
other suspects). This should be possible with a short .bat file.
--
Andy