[nsd-users] nsd and own openssl

[Ondřej Surý]

JFTR As openssl 1.1.0 has a different SOVERSION, it would not clash with
system OpenSSL (that would probably stay on 1.0.x for a while). So
uninstalling -dev headers for system openssl and installing OpenSSL
1.1.0 into /usr/local (or even using backported package to install
libopenssl-dev 1.1.0 into /usr) would just work[*].

* - Depends on the system used and the packaging crazyness it uses (100%
for Debian/Ubuntu, can't say for sure for other systems)

Cheers,
-- 
Ondřej Surý <ondrej at sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu

On Tue, Sep 20, 2016, at 10:45, A. Schulze wrote:
> 
> Hi,
> 
> currently I try to compile openssl-1.1.x as own package for my usual  
> platforms.
> Viktor Dukhovni suggested a way this build can coexist without symbol  
> conflict with
> the real OpenSSL in /usr
> 
> So my includes are now also in /usr/include/openssl but the libraries  
> are named
> /usr/lib/libcrypto-opt.so.1.1 and /usr/lib/libssl-opt.so.1.1
> 
> That work for other projects like postfix or nginx.
> But it fail for nsd. Configure tries to check some stuff and uses  
> "libssl" and "libcrypto" as fixed names.
> - checking if libssl needs libdl
> - checking if libcrypto needs -pthread
> - checking for HMAC_Update in -lcrypto
> 
> Can I tell configure to use my libraries?
> 
> Andreas
> 
> _______________________________________________
> nsd-users mailing list
> nsd-users at NLnetLabs.nl
> https://open.nlnetlabs.nl/mailman/listinfo/nsd-users