in reply to Problems with activeperl build 631

I've had things like this happen when upgrading ActivePerl. Uninstalling the initial version and then installing seems to take care of it. It's also caused assorted memory leaks & BSOD issues when I tried using some win32 modules. Yes, it's weak advice, but there it is.
  • Comment on Re: Problems with activeperl build 631 (boo)

Replies are listed 'Best First'.
Re: Re: Problems with activeperl build 631 (boo)
by grep (Monsignor) on Jan 17, 2002 at 13:37 UTC
    Another thing to watch for is an old 500 series build. A 600 series build will not upgrade a 500 series correctly (this is documented on the Activestate website). I know this because we upgraded an early 600 series to 631 without noticing an old 500 series build that was never unistalled. I can't tell you how many strange error we ended up getting from this lovely little problem. We ended up removing all installations of perl and removing any registry entries with the word perl in them to fix it.

    It is such an improvement to keep your critial setup information in a obfuscated hack of a database, than easily read and searched flat files

    grep
    grep> cd pub
    grep> more beer