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?

[download]

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=");'

In reply to Re^2: Net::SSLeay on Ubuntu 18.04 with custom OpenSSL version by cavac
in thread Net::SSLeay on Ubuntu 18.04 with custom OpenSSL version by cavac

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.