having trouble installing the Finance Quote update app

[John Ralls]

> On Jan 15, 2015, at 3:56 PM, David Richards <drichardsms at btinternet.com> wrote:

[SNIP]

> This is the Crypt::Leasy build report you requested
> 
>    Do you really need Crypt::SSLeay?
> 
>    Starting with version 6.02 of LWP, https support was unbundled into
>    LWP::Protocol::https. This module specifies as one of its prerequisites
>    IO::Socket::SSL which is automatically used by LWP::UserAgent unless
>    this preference is overridden separately. IO::Socket::SSL is a more
>    complete implementation, and, crucially, it allows hostname
>    verification. Crypt::SSLeay does not support this. At this point,
>    Crypt::SSLeay is maintained to support existing software that already
>    depends on it.
> 
>    However, it is possible that your software does not really depend on
>    Crypt::SSLeay, only on the ability of LWP::UserAgent class to
>    communicate with sites over SSL/TLS.
> 
>    If are using version LWP 6.02 or later, and therefore have installed
>    LWP::Protocol::https and its dependencies, and do not explicitly use
>    Net::SSL before loading LWP::UserAgent, or override the default socket
>    class, you are probably using IO::Socket::SSL and do not really need
>    Crypt::SSLeay.
> 
>    Before installing Crypt::SSLeay, you may want to try specifying a
>    dependency on LWP::Protocol::https.
> 
> Failed to build and link a simple executable using OpenSSL

Thanks. There are two issues there. One is that F::Q might not need SSLeay any more, and that's why I've put
Erik Coulson as the "To" addressee.

The other is that bit about failing to link OpenSSL, which is why SSLeay is failing to build. Even though it would be reasonable for SSLeay to require a late-2014 version of OpenSSL to ensure that the several serious security issues are fixed,
its documentation (http://search.cpan.org/dist/Crypt-SSLeay/SSLeay.pm) says that anything newer than 2000 is OK, and SnowLeopard's is much newer than that. Since the OpenSSL headers and library are normally in /usr on pre-Mavericks versions of OSX, that means that your include path or library path is messed up. You can try the Verify Disk option in Disk Utilities to see if it will restore the paths and perhaps the libraries or headers. Failing that you'll need help from an expert to whom you can give access to your machine. You can try the Genius Bar, but I don't think they support that old an OS version. A local Mac User Group might provide some leads.

Regards,
John Ralls