Re^13: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003

Replies are listed 'Best First'.
Re^14: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003 by BrowserUk (Patriarch) on Mar 29, 2008 at 13:24 UTC
Could the problem lie with all that additional "gui." gunk that you're getting ?* Not as far as I can tell. That's just because I typed "ppm" at a command prompt once and it started the gui. I quit straight away, but I guess it stored some config somewhere in the interim. I'm almost certain the problems arise because I have two versions of active state installed. 5.8.6 as my main installation, and 5.10.0 whilst I work out how to build all the things I have in the 5.8.6. I speculate that when you install AS builds, they secrete away some config in the registry somewhere and then go fetch that to decide what build/architecture you have. And even though I being very judicious in ensuring that nothing in my envoronment points to the 5.8.6 installation before running PPM, their script is fetching something from the registry somewhere and making the decision based upon that. If people would add a bit of trace information, __FILE__ & __LINE__ when issuing error messages, or at least some useful information like say: `ppm install failed: The PPD does not provide code to install for this +platform [MSWin32-xyz-pqr]` [download] tracking down and solving these problems would be so much simpler. Which is exactly why I stopped using PPM3. And that was before they complicated the existing issues with the great bob ball of (OO) string by adding the gui. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply] [d/l]
Re^14: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003 by BrowserUk (Patriarch) on Mar 29, 2008 at 18:18 UTC
Well. I finally tracked down what architecture PPM thinks it should be installing for: `c:\Perl510\bin> perl -MActivePerl::PPM::Client -wle"print ActivePerl::PPM::Client->new()->arch" MSWin32-x86-multi-thread-118.53` [download] Now from where do you think it came up with that? Because I've searched my entire bloody filesystem and registry and that string doesn't seem to appear anywhere! Gah! If Gavin hadn't just installed 1002 and encountered the same failure, I might assume that the reason 1002 was released so soon after 1000, was to correct this...but that still doesn't explain where it comes from. The absence of the string anywhere on my system suggests it must be constructed at runtime. Why? Does it change from run to run? Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply] [d/l]
Re^15: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003 by Gavin (Archbishop) on Mar 29, 2008 at 20:52 UTC
The problem seems to come from as BrowserUk suspected from running more than one version i.e. 5.8 and 5.10 on the same system there must be a conflict in the registry that stops the install Removing both 5.8 and 5.10 from my system then deleting all the following files and folders in the registry. HKEY_LOCAL_MACHINE/Software/ActiveState/ActivePerl HKEY_LOCAL_MACHINE/Software/ActiveState/PerlScript HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/Uninstall/ActivePerl Reinstalling 5.10 and then Crypt-SSLeay installs correctly, this may not be what you wanted to hear. It may be possible to make the necessary changes in the registry to allow the install but as always it comes with risks!	[reply]
Re^15: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003 by BrowserUk (Patriarch) on Mar 29, 2008 at 23:59 UTC
And the answer to my own question is on line 41 of `/perl510/lib/ActivePerl/PPM/Client.pm`: `$arch .= sprintf "-%vd", substr($^V, 0, 2) if $] >= 5.008;` [download] Which produces: `C:\Perl510>perl -wle"print $]; print $^V; printf qq[-%vd], substr($^V, + 0, 2)" 5.010000 v5.10.0 -118.53` [download] A few further questions arise: What is that sprintf trying to do? (What is pattern `%vd` besides the obvious:) How come other some other peoples copies aren't afflicted? Can anyone confirm their version of AS1000/1002 has the above line? Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply] [d/l] [select]
Re^16: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003 by syphilis (Archbishop) on Mar 30, 2008 at 00:33 UTC
I think you've found it. My ActivePerl/PPM/Client.pm (AS build 1002) is slightly different: `39: unless ($arch) { 40: $arch = $Config{archname}; 41: if ($] >= 5.008) { 42: my $vstring = sprintf "%vd", $^V; 43: $vstring =~ s/\.\d+$//; 44: $arch .= "-$vstring"; 45: } 46: }` [download] When I run the code that's inside that unless block it sets $arch to `MSWin32-x86-multi-thread-5.10` yet I get the same as you when I run the one liner you presented. And `$arch .= sprintf "-%vd", substr($^V, 0, 2) if $] >= 5.008;` definitely appends `-118.53` to $arch. But how come the difference betwen my PPM installation and your PPM installation ? (This should probably be raised on the PPM mailing list. I'm subscribed to that list but I don't recall seeing anything like this reported.) Cheers, Rob UPDATE: I've just unzipped ActivePerl-5.10.0.1002-MSWin32-x86-283697.zip to make sure that my Client.pm is the same as the Client.pm that ships with that source - and it is. It's therefore rather baffling that some others end up with a dfferent version of Client.pm when they install build 1002.	[reply] [d/l] [select]
Re^17: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003 by BrowserUk (Patriarch) on Mar 30, 2008 at 01:14 UTC
Re^18: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003 by yeah (Novice) on Mar 31, 2008 at 03:06 UTC
Re^18: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003 by yeah (Novice) on Mar 30, 2008 at 10:00 UTC
Some notes below your chosen depth have not been shown here
Re^17: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003 by BrowserUk (Patriarch) on Mar 30, 2008 at 03:11 UTC
Re^18: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003 by yeah (Novice) on Apr 01, 2008 at 12:30 UTC
Some notes below your chosen depth have not been shown here
Re^14: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003 by BrowserUk (Patriarch) on Mar 29, 2008 at 13:39 UTC
Could the problem lie with all that additional "gui." gunk that you're getting ?* Not as far as I can tell. That's just because I typed "ppm" at a command prompt once and it started the gui. I quit straight away, but I guess it stored some config somewhere in the interim. I'm almost certain the problems arise because I have two versions of active state installed. 5.8.6 as my main installation, and 5.10.0 whilst I work out how to build all the things I have in the 5.8.6. I speculate that when you install AS builds, they secrete away some config in the registry somewhere and then go fetch that to decide what build/architecture you have. And even though I'm being very judicious in ensuring that nothing in my environment points to the 5.8.6 installation before running PPM, their script is fetching something from the registry somewhere and making the decision based upon that. If people would add a bit of trace information, __FILE__ & __LINE__ when issuing error messages, or at least some useful information like say: `ppm install failed: The PPD does not provide code to install for this +platform [MSWin32-xyz-pqr]` [download] tracking down and solving these problems would be so much simpler. Which is exactly why I stopped using PPM3. And that was before they complicated the existing issues with the great big ball of (OO) string by adding the gui. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply] [d/l]
Re^15: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003 by syphilis (Archbishop) on Mar 29, 2008 at 13:59 UTC
I speculate that when you install AS builds, they secrete away some config in the registry I think that's possibly the case with the msi packages, but I don't think you'll strike such an issue if you install from the zip packages. I have 3 ActiveState builds on this box (806, 822 and 1002), all of which were installed from the zip packages, and I don't get any grief from that. I think the msi packages offer an "uninstall" capability - and I think that dictates that the registry is going to be messed with. The zip packages don't have an uninstall capability and don't (afaik) screw with the registry in any way - even if one does let the installation process modify the path (which I don't allow). I personally wouldn't recommend the msi packages under any circumstances. Cheers, Rob	[reply]
Re^16: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003 by BrowserUk (Patriarch) on Mar 29, 2008 at 14:18 UTC
It is quite possible that I installed 5.8.6 (the first time, a long time ago now) using the msi. I've re-installed it over several times since using the zip to correct various horrors (like early build(s) of 5.8.8), but I doubt I did an uninstall for fear of it removing all the packages I had installed and having to start from scratch. I definitely used the zip for 5.10 (we live and learn :) Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]