On Sat, Apr 9, 2016 at 5:39 AM, Shlomi Fish <shlo...@shlomifish.org> wrote: > Hi Ken, > > welcome aboard. > > please reply to all recipients. > > On Fri, 8 Apr 2016 17:36:47 -0700 > Kenneth Wolcott <kennethwolc...@gmail.com> wrote: > >> Hi; >> >> How to install WWW::Salesforce::Simple on a Mac? cpanm refuses to >> install Crypt::SSLeay >> >> I need to use the WWW::Salesforce::Simple Perl module on an El Capitan Mac. >> >> I installed cpanm. >> >> I tried to install WWW::Salesforce::Simple, but cpanm bails out >> because of Crypt::SSLeay. >> > > What's the error? One should note that you should not mess with the system's > perl on Mac OS X. Instead - use perlbrew. See: > > * http://perl-begin.org/platforms/mac/ > > * http://perlbrew.pl/ > > Crypt::SSLeay may in addition require the development headers of OpenSSL or > whatever which you can install using a Mac-based package manager (e.g: > macports, > fink, or homebrew). > > Good luck! > > -- Shlomi Fish > >> Is there a way to convince cpanm to install other Perl modules that >> will perform the duties expected of Crypt::SSLeay? >> >> How do I get WWW::Salesforce::Simple to install on the Mac? >> >> Thanks, >> Ken Wolcott >>
Hi Shlomi; Apparently the Crypt::SSLeay module won't install for my protection (HeartBleed?), but it is still a required prerequisite for WWW::Salesforce. I tried to follow the hints provided which suggested installing other modules which would provide the required basis for WWW::Salesforce without using Crypt::SSLeay, but it appears that trying to install WWW::Salesforce using cpanm still requires Crypt::SSLeay. So, perhaps if I have alternatives installed that installing WWW::Salesforce using cpan or just directly installing it will now work? It would be nice if the prerequisites could some how be updated for WWW::Salesforce so that one can have the functionality needed without the risk of installing a known vulnerability. I'm also trying to grok why it might not be a good idea to use the Perl provided by the Mac OS (El Capitan) and use perlbrew instead. Using perlbrew itself won't solve the problem I have with WWW::Salesforce depending on a vulnerable module which I am unable to substitute because the prerequisites force it to be used but it won't install (endless circle of frustration here). A painful workaround is to ssh to a Linux (CentOS) system that has the WWWW::Salesforce Perl module already installed and in use for other things, call a routine at that location and bring the resultant data back to be used locally. Thanks, Ken Wolcott -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/