From owner-freebsd-ports@freebsd.org Mon Jul 18 20:03:40 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 8BF74B9D7D5 for ; Mon, 18 Jul 2016 20:03:40 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 541EF1E6A for ; Mon, 18 Jul 2016 20:03:40 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-it0-x22f.google.com with SMTP id j124so688349ith.1 for ; Mon, 18 Jul 2016 13:03:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=doRI4GvqjAugMEPKvD2Qg0HNyg4utHy+PwjN6yGv0Q8=; b=scYfKbY16EqSYGDkuF9gwqlcBWIbdXKYIOrHpIPMQeIxhzXVNh3+vX7kJivZW/ltxY 6KJ/f0ZbQk4rwcHRw55a/dzC+7qCNs7pwZyFVWh+olknAMqyYAh+lVB0k7EIg8mrRfOo r4+8nJdVjAHuJ27sSBr1OpNFB8fnBv30AIPcUC/l5X/8HnFbrGcml/+efnblRKP9OxYF Y+IZTmsk82InoyNurPL/I/plHDDhshHPf/4p3DQqorXANn+Avuw4XSwcJPqOTGB8MY8y 9jBw4Jug6IpHWHoTq1/Tl5I1PgHcYzizRNMcG2Ez7HJ8mgFWBRZ3/XHMgFk/Ma9fpBrp Xp4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=doRI4GvqjAugMEPKvD2Qg0HNyg4utHy+PwjN6yGv0Q8=; b=KZeXsQUiRZvOV590cM+q2RKk0kXUK8q7E4P/wDG4fKeLq6gmD0Xs2+Nn4EP4GGSXrQ nPPuUyH3FGQCAonGxuvnCNcdxNS7MSKC+gaw1uzcW/BYWvvY6PcaQUMoAWKjFgnd3EFT E92ppcFVhIWQuBuT4mkPk+koqjKJCuiY9RICQtJQNHqlB17HthbEkQwZZh8Jx4Bm6286 Mrf1Sw76xr9yvszFYwa9UYJgInaqiFxqfu0gct/RDqtyQt4XAsgeOX7DM1JWd5FDpVut PGh5doz/5Rj3df/SYVTFUs3QyxPZb09CaJC3OvxiR62h+pmJ3dMPB5rMkrPlIHtdx3qn GWig== X-Gm-Message-State: ALyK8tJpmd1nzklgawLaMri6Ekml4dxrfAwF89dR8xIgDI2aufN7x5G169Dt8YwUbDiZsffA+3B9867uYJJb0Q== X-Received: by 10.36.39.195 with SMTP id g186mr172103ita.53.1468872219749; Mon, 18 Jul 2016 13:03:39 -0700 (PDT) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.79.78.213 with HTTP; Mon, 18 Jul 2016 13:03:39 -0700 (PDT) In-Reply-To: <7c85-578d3200-1d-6b8b4580@130332282> References: <7c85-578d3200-1d-6b8b4580@130332282> From: Kevin Oberman Date: Mon, 18 Jul 2016 13:03:39 -0700 X-Google-Sender-Auth: BJHtADvsMbZ7s2h6cvYlmaYI8fQ Message-ID: Subject: Re: curl and nginx no longer build on same host To: Euan Thoms Cc: Jim Ohlstein , FreeBSD Ports Mailing List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 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:03:40 -0000 On Mon, Jul 18, 2016 at 12:45 PM, Euan Thoms wrote: > > On Saturday, July 16, 2016 20:43 SGT, Jim Ohlstein wrote: > > > Hello, > > > > On 7/15/16 11:41 PM, Euan Thoms wrote: > > > > > > Yes. I've used ssl=openssl and ssl=libressl in make.conf, no luck with > 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 > both 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 > options should build together. > > > > > > I suppose this has only come about on this upgrade cycle because nginx > port now has http2 on by default? > > > > As of version 1.10.0 it appears http2 is selected by default. It has > > been the default in www/nginx-devel for some time. it is not the default > > for ftp/curl: > > > > OPTIONS_DEFAULT= CA_BUNDLE COOKIES OPENSSL PROXY RESOLV > > THREADED_RESOLVER TLS_SRP > > > > My /etc/make.conf has the following: > > > > WITH_OPENSSL_PORT=yes > > > > That will force ftp/curl (and all ports) to build against the openssl > > port. If I understand correctly, that is about to become the default > > behavior for all ports at some time in the not so distant future, or at > > least it has been proposed. > > > > OK, I understand. And I'm glad we're heading somewhere where we will 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 range of > software types. > > Are you sure that WITH_OPENSSL_PORT isn't deprecated. I got some warnings > to that effect. So I've been using USES+=ssl=openssl instead. Perhaps > 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. > > -- > Regards, Euan Thoms > Yes and no. WITH_OPENSSL_PORT in make,conf has been deprecated. It should still work, but you should update to the new syntax. If you do use it, you should see the following: "Using WITH_OPENSSL_PORT in make.conf is deprecated, replace it with DEFAULT_VERSIONS+=ssl=openssl in your make.conf" To avoid conflicting SSL libraries in different ports, it is bast to put the "DEFAULT_VERSIONS+=ssl=openssl" in /etc/make.conf. If you use base OpsnSSL in some ports that create shareable libraries and the ports version in others, you will eventually hit an executable, possibly from a third port, that is linked to both and those programs will not run. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683