Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Jul 2016 03:45:43 +0800
From:      "Euan Thoms" <euan@potensol.com>
To:        "Jim Ohlstein" <jim@ohlste.in>
Cc:        "FreeBSD Ports Mailing List" <freebsd-ports@freebsd.org>
Subject:   =?utf-8?q?Re=3A?= curl and nginx no longer build on same host
Message-ID:  <7c85-578d3200-1d-6b8b4580@130332282>
In-Reply-To: <e7b59cb6-d52d-b558-0bc0-f3f0610841a9@ohlste.in>

next in thread | previous in thread | raw e-mail | index | archive | help
 
On Saturday, July 16, 2016 20:43 SGT, Jim Ohlstein <jim@ohlste.in> wrot=
e: 
 
> Hello,
> 
> On 7/15/16 11:41 PM, Euan Thoms wrote:
> >
> > Yes. I've used ssl=3Dopenssl and ssl=3Dlibressl in make.conf, no lu=
ck with either. The bottom line is ftp/curl with default port options d=
oes not want to build against openssl or libressl from ports. And it do=
esn't want to try and use the base openssl either.
> >
> > Your point about the port options for http2 requiring the ports ver=
sion 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 chan=
ged the default port options on either of the two ports. But default po=
rt options should build together.
> >
> > I suppose this has only come about on this upgrade cycle because ng=
inx 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 defa=
ult 
> for ftp/curl:
> 
> OPTIONS=5FDEFAULT=3D    CA=5FBUNDLE COOKIES OPENSSL PROXY RESOLV 
> THREADED=5FRESOLVER TLS=5FSRP
> 
> My /etc/make.conf has the following:
> 
> WITH=5FOPENSSL=5FPORT=3Dyes
> 
> 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 ha=
ve more consistency. I just feel that we shouldn't need anything in /et=
c/make.conf unless we are exerting some extra control and using non-def=
ault options. I've managed to get away without anything in /etc/make.co=
nf on all my jails, collectively they install quite a range of software=
 types.

Are you sure that WITH=5FOPENSSL=5FPORT isn't deprecated. I got some wa=
rnings to that effect. So I've been using USES+=3Dssl=3Dopenssl 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 





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7c85-578d3200-1d-6b8b4580>