From owner-freebsd-ports@freebsd.org Mon Jul 18 20:37:04 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 0DE8AB9B488 for ; Mon, 18 Jul 2016 20:37:04 +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 C68261D81 for ; Mon, 18 Jul 2016 20:37:03 +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 4A70444F52; Mon, 18 Jul 2016 20:37:01 +0000 (UTC) Received: from webmail.potensol.com (webmail.potensol.com [192.168.10.5]) by smtp.potensol.com (Postfix) with ESMTP id C9C7F44F51; Mon, 18 Jul 2016 20:37:00 +0000 (UTC) content-type: text/plain; charset="utf-8" in-reply-to: from: "Euan Thoms" X-Forward: 192.168.10.5 date: Tue, 19 Jul 2016 04:37:00 +0800 cc: "Jim Ohlstein" , "FreeBSD Ports Mailing List" to: "Kevin Oberman" MIME-Version: 1.0 message-id: <7c8b-578d3e00-15-6b8b4580@127158756> 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: Mon, 18 Jul 2016 20:37:04 -0000 On Tuesday, July 19, 2016 04:03 SGT, Kevin Oberman wrote: > On Mon, Jul 18, 2016 at 12:45 PM, Euan Thoms wrot= e: > > > > > On Saturday, July 16, 2016 20:43 SGT, Jim Ohlstein = wrote: > > > > OK, I understand. And I'm glad we're heading somewhere where we wil= l have > > more consistency. I just feel that we shouldn't need anything in > > /etc/make.conf unless we are exerting some extra control and using = > > non-default options. I've managed to get away without anything in > > /etc/make.conf on all my jails, collectively they install quite a r= ange of > > software types. > > > > Are you sure that WITH=5FOPENSSL=5FPORT isn't deprecated. I got som= e warnings > > to that effect. So I've been using USES+=3Dssl=3Dopenssl instead. P= erhaps > > that's part of the problem, maybe the ftp/curl port is still using = the > > older make.conf flag. I'll try it next time I update. > > > > Thanks Jim. > > > > Yes and no. WITH=5FOPENSSL=5FPORT in make,conf has been deprecated. I= t should > still work, but you should update to the new syntax. If you do use it= , you > should see the following: > "Using WITH=5FOPENSSL=5FPORT in make.conf is deprecated, replace it w= ith > DEFAULT=5FVERSIONS+=3Dssl=3Dopenssl in your make.conf" > > To avoid conflicting SSL libraries in different ports, it is bast to = put > the "DEFAULT=5FVERSIONS+=3Dssl=3Dopenssl" in /etc/make.conf. If you u= se base > OpsnSSL in some ports that create shareable libraries and the ports v= ersion > in others, you will eventually hit an executable, possibly from a thi= rd > port, that is linked to both and those programs will not run. OK, I'm clear about the make.conf options and what they mean. But I sti= ll have a problem in that even if I use DEFAULT=5FVERSIONS+=3Dssl=3Dope= nssl, ftp/curl will not build, certainly not with portmaster and I thin= k I tried building it manually from inside it's ports directory. /usr/ports/ftp/curl]# make =3D=3D=3D> curl-7.49.1 GSSAPI=5FBASE is not compatible with OpenSSL fr= om ports. Use other GSSAPI options or OpenSSL from base system. *** Error code 1 Stop. make: stopped in /usr/ports/ftp/curl So basically, I'd have to change one of the GSSAPI options in ftp/curl.= Except I haven't got a clue on the ramifications of this. Do I need GS= SAPI? If so, should I use Heimdal or MIT? So you see my point, it's not friendly on new FreeBSD users. I'm a fair= ly experienced FreeBSD sys-adimin and I don't know what to do in this c= ase. At least I now know that there is a good reason to not have on port bui= lt against base openssl and another built against ports openssl. -- Regards, Euan Thoms