I searched CPAN and 75% of tests of the module fail
Speaking with my Crypt-SSLeay maintainer hat here, I wouldn't be too worried about those errors. When I took over maintenance, there were no tests at all.
I added some tests, and some of them fail, such as if port 443 is already in use on localhost, or if the machine is firewalled off from the internet. I need to allow the tests to fail with grace :)
As a general rule, if the modules compiles without error, and the XS component can be loaded, the module will be just fine. That is, all is well if perl -MNet::SSL -e 1 produces no error message.
The documentation does say, and I cite:
Windows
Crypt::SSLeay builds correctly with Strawberry Perl.
For Activestate users, the ActiveState company does not have a permit from the Canadian Federal Government to distribute cryptographic software. This prevents Crypt::SSLeay from being distributed as a PPM package from their repository. See http://aspn.activestate.com/ASPN/docs/ActivePerl/5.8/faq/ActivePerl-faq2.html#crypto_packages for more information on this issue.
You may download it from Randy Kobes's PPM repository by using the following command ...
• another intruder with the mooring in the heart of the Perl
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
