From owner-freebsd-ports@freebsd.org Sat Jul 16 03:41:28 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60681B9AC1A for ; Sat, 16 Jul 2016 03:41:28 +0000 (UTC) (envelope-from euan@potensol.com) Received: from smtp.potensol.com (smtp.potensol.com [103.15.233.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.potensol.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E33181745 for ; Sat, 16 Jul 2016 03:41:27 +0000 (UTC) (envelope-from euan@potensol.com) Received: from smtp.potensol.com (smtp.potensol.com [103.15.233.195]) by smtp.potensol.com (Postfix) with ESMTP id ACF2944772; Sat, 16 Jul 2016 03:41:23 +0000 (UTC) Received: from webmail.potensol.com (webmail.potensol.com [192.168.10.5]) by smtp.potensol.com (Postfix) with ESMTP id 2525544771; Sat, 16 Jul 2016 03:41:23 +0000 (UTC) content-type: text/plain; charset="utf-8" in-reply-to: from: "Euan Thoms" X-Forward: 192.168.10.5 date: Sat, 16 Jul 2016 11:41:22 +0800 cc: "FreeBSD Ports Mailing List" to: "Jim Ohlstein" MIME-Version: 1.0 message-id: <7c8b-5789ad00-d-6b8b4580@127157337> subject: =?utf-8?q?Re=3A?= curl and nginx no longer build on same host User-Agent: SOGoMail 2.3.13 content-transfer-encoding: quoted-printable X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2016 03:41:28 -0000 On Saturday, July 16, 2016 10:21 SGT, Jim Ohlstein wrot= e: > Hello, > > > On Jul 15, 2016, at 10:03 PM, Euan Thoms wrote:= > > > > Bump > > > > Can anyone else install or update ftp/curl after installing nginx? = > > Yes, but I'm building packages using poudriere, not using portmaster.= Good point, it may be a portmaster issue. Next time I update, I'll try = to upgrade manually... eh, how do I do that again (scratches head). > > > > > The only way I'm able to update now is to uninstall openssl and ngi= nx, then update curl, then reinstall nginx (which pulls in openssl). Th= is was not required on several previous update cycles. > > If memory serves me correctly, nginx and curl both require openssl fr= om ports only if certain options are chosen (http2 being one), or at le= ast that was the case in the past. > > You may have option(s) selected for one that requires the version fro= m ports, and one that does not. > > Have you tried to force usage of openssl from ports in your /etc/make= .conf? > Yes. I've used ssl=3Dopenssl and ssl=3Dlibressl in make.conf, no luck w= ith either. The bottom line is ftp/curl with default port options does = not want to build against openssl or libressl from ports. And it doesn'= t want to try and use the base openssl either. Your point about the port options for http2 requiring the ports version= of openssl is valid. But this happens when the default options for bot= h ports are used. I could accept my manual workaround if I had changed = the default port options on either of the two ports. But default port o= ptions should build together. I suppose this has only come about on this upgrade cycle because nginx = port now has http2 on by default? > > > > > >> On Thursday, July 14, 2016 23:30 SGT, "Euan Thoms" wrote: > >> > >> I just tried to update my www/sogo2 jail and I now have ports brea= kage. > >> > >> The first thing that happened is that "portmaster -Rad" failed on = ftp/curl with the following message: > >> > >> """ > >> =3D=3D=3D> Cleaning for curl-7.49.1 > >> You have a /usr/local/lib/libcrypto.so file installed, but the fra= mework is unable > >> to determine what port it comes from. > >> Add DEFAULT=5FVERSIONS+=3Dssl=3D to your /et= c/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 > >> > >> =3D=3D=3D>>> make build failed for ftp/curl > >> =3D=3D=3D>>> Aborting update > >> > >> =3D=3D=3D>>> Update for curl-7.48.0=5F2 failed > >> =3D=3D=3D>>> Aborting update > >> """ > >> > >> It seems that ftp/curl can't build with openssl or libressl instal= led 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 s= et anything in /etc/make.conf, but even if I do set DEFAULT=5FVERSIONS+= =3Dssl=3Dssl 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 the= se days, until today. > >> > >> Why can't curl just use openssl from base, despite the port versio= n being installed? > >> > >> > >> > >> # uname -a > >> FreeBSD sogo.potensol.com 10.1-RELEASE-p16 FreeBSD 10.1-RELEASE-p1= 6 #0: Tue Jul 28 12:04:19 UTC 2015 root@amd64-builder.daemonology.n= et:/usr/obj/usr/src/sys/GENERIC amd64 > -- Regards, Euan Thoms