To be honest, no i didn't. But as far as i can determine, i'm not getting far enough in the build process for those bugs to become relevant.
I'm was failing at some very basic level for which i should have known (and tested) the solution after using Linux for 20 years:
$ OPENSSL_PREFIX=/home/cavac/bin/openssl LD_LIBRARY_PATH=/home/cavac/b
+in/openssl/lib:$LD_LIBRARY_PATH perl Makefile.PL
*** Found OpenSSL-1.1.1a installed in /home/cavac/bin/openssl
*** That's newer than what this module was tested with
You should consider checking if there is a newer release of this m
+odule
available. Everything will probably work OK, though.
*** Be sure to use the same compiler and options to compile your OpenS
+SL, perl,
and Net::SSLeay. Mixing and matching compilers is not supported.
Do you want to run external tests?
So, LD_LIBRARY_PATH did the trick. Not sure why Net::SSLeay doesn't set it automatically, though...
And now i have to look into testing with the Github version of Net::SSLeay, since the bugs are marked "patched".
perl -e 'use MIME::Base64; print decode_base64("4pmsIE5ldmVyIGdvbm5hIGdpdmUgeW91IHVwCiAgTmV2ZXIgZ29ubmEgbGV0IHlvdSBkb3duLi4uIOKZqwo=");'
-
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.
|
