in reply to Re^6: win32 thread version (oops)
in thread win32 thread version

Hi there, I'm back on the case

There are two errno.pm files (and cygwin has a third) but

c:/Perl/site/lib/Errno.pm
... "$Config{'archname'}-$Config{'osvers'}" eq "MSWin32-x86-multi-thread-4.0" or die "Errno architecture (MSWin32-x86-multi-thread-4.0) does not ma +tch executable architecture ($Config{'archname'}-$Config{'osvers'})";

c:/Perl/lib/Errno.pm

"$Config{'archname'}-$Config{'osvers'}" eq "MSWin32-x86-multi-thread-5.00" or die "Errno architecture (MSWin32-x86-multi-thread-5.00) does not m +atch executable architecture ($Config{'archname'}-$Config{'osvers'})" +;

Replies are listed 'Best First'.
Re^8: win32 thread version (oops)
by syphilis (Archbishop) on Jan 07, 2008 at 18:03 UTC
    Try renaming C:/perl/site/lib/Errno.pm to Errno_hide.pm (so it can't be found). Does that fix the problem ?

    Cheers,
    Rob
      Rob, your test

      perl -MErrno -e "print \"ok\""
      returns "ok" with no error. The memcached sample code is now also able to run...
      It seems to work, then thank you.. what exactly is going on that lead to the original error, do you know?
      Cheers,
      TDG
        Credit where credit's due ... it was actually tye's observation that led to this solution.

        I don't know what caused the original error. It's unusual for there to be 2 versions of Errno.pm in an ActivePerl installation. I still can't get a handle on how the problem has come about. At some stage during the 5.8.x releases ActiveState started putting their non-CORE (default) modules in perl/lib. Previously, those modules would have been in perl/site/lib. At the same time, they changed @INC to put perl/site/lib ahead of perl/lib. I think you must have done an upgrade during that "changeover" phase, and that's what's stuffed things up ... but I still can't get a handle on the exact nature of the problem ... and i wonder if there aren't other modules that are similarly affected.

        Cheers,
        Rob