I just tried to update my www/sogo2 jail and I now have ports breakage. The first thing that happened is that "portmaster -Rad" failed on ftp/curl with the following message:
""" ===> Cleaning for curl-7.49.1 You have a /usr/local/lib/libcrypto.so file installed, but the framework is unable to determine what port it comes from. Add DEFAULT_VERSIONS+=ssl=<openssl package name> to your /etc/make.conf and try again. *** Error code 1 Stop. make[1]: stopped in /usr/ports/ftp/curl *** Error code 1 Stop. make: stopped in /usr/ports/ftp/curl ===>>> make build failed for ftp/curl ===>>> Aborting update ===>>> Update for curl-7.48.0_2 failed ===>>> Aborting update """ It seems that ftp/curl can't build with openssl or libressl installed from ports. And www/nginx will only build with openssl or libresll installed from ports. So basically nginx and curl can't co-exist on the same host/jail. My port options are almost all the defaults, and I don't want to set anything in /etc/make.conf, but even if I do set DEFAULT_VERSIONS+=ssl=<???>ssl I can't get curl to build. I've been updating this jail regulary for a while now without any issue. This reminds me hair-pulling in the past with the Kerberos fork issues (MIT vs Heimdal). And I was finding ports management so easy these days, until today. Why can't curl just use openssl from base, despite the port version being installed? # uname -a FreeBSD sogo.potensol.com 10.1-RELEASE-p16 FreeBSD 10.1-RELEASE-p16 #0: Tue Jul 28 12:04:19 UTC 2015 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 -- Regards, Euan Thoms _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
