[squid-dev] squid master build with alternate openssl fails

Francesco Chemolli gkinkie at gmail.com
Fri May 8 21:11:44 UTC 2020


On Fri, May 8, 2020 at 3:58 PM Alex Rousskov <
rousskov at measurement-factory.com> wrote:

> On 5/8/20 10:12 AM, Christos Tsantilas wrote:
>
> > Squid master 699ade2d fails to build with an alternate OpenSsl, when the
> > "--with-openssl=/path/to/openssl" is used.
>
> Francesco, builds with custom OpenSSL paths are not that uncommon,
> especially among SslBump admins. Would you be able to test that kind of
> configuration in one of the Jenkins tests? It can be even combined with
> other custom-path tests. Or is this too custom/special to warrant an
> automated test in your opinion?


The most complicated part is to prep and keep uptodate a test environment
with openssl in a nonstandard location; I rebuild our docker images once a
month to ensure they're fresh with what's in the wild.
To decide how much effort to invest, how prevalent is this situation? On
Linux I'd expect this to be pretty much a corner case by now, is it not?

-- 
    Francesco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-dev/attachments/20200508/052462ac/attachment.html>


More information about the squid-dev mailing list