On 7/8/2019 8:26 PM, Chris wrote:
Well,,, as usual,,, After all else fails and you send a msg to a email reflector in desperation,,,, I have it working..

All I really needed to do was pkg install openssl111.. This removed the 1.0.x version and then when I ./configure unbound it picked up the 1.1.1c without the need for a --with-ssl= config option..

So im good and working great on OpenSSL 1.1.1c and FreeBSD 12.0-RELEASE-p7

Thank you for trying to help.

So the method that works for anyone else who sees this is to pkg install openssl111 or whatever is current, *WHICH WILL UNINSTALL OPENSSL 1.0.x*. Then do a ./configure make install of Unbound.

Keep in mind this most likely might break something else however as it forces everything to 1.1.1 by removing 1.0.x..  AND of course everything else would need to be built again to the new Openssl. All im running tho is unbound on this box tho, so, im great and im back to the new TLS..

On 7/8/2019 7:21 PM, Pete Wright wrote:


On 7/8/19 6:40 PM, Chris via Unbound-users wrote:
The below issue occurs because of conflicts with libevent..

Removing --with-libevent produces all sorts of different errors.

I would think I could point to a Openssl and make this work. I cannot.

Seems simple enough, download 1.9.2,, go get OpenSSL 1.1.1c, config/make it. Then go config make Unbound with --with-ssl= pointing to the OpenSSL.. But this fails..

Ive spent hours on this and tried all the OpenSSL versions. I feel mighty stupid as this should work...

Please give me a hint on what to go do.

I can pkg install 1.9.2 and this is fine and shows openssl lib 1.1.1, but, I want --without-pthreads --without-solaris-threads and so, I need to compile.
one thing to note is that the ports tree uses the OpenSSL from base for building via the $OPENSSLBASE envvar, so it may be worth pointing config at that location.  here's how that's setup in the ports tree I believe:

# OPENSSLBASE           - "/usr" or ${LOCALBASE}


hope this helps,
-pete



Reply via email to