From owner-freebsd-ports@FreeBSD.ORG Sun Mar 9 18:42:11 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5C153A6D for ; Sun, 9 Mar 2014 18:42:11 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 17C8D8BE for ; Sun, 9 Mar 2014 18:42:10 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WMifo-0006pH-Gy for freebsd-ports@freebsd.org; Sun, 09 Mar 2014 19:42:08 +0100 Received: from a91-154-115-217.elisa-laajakaista.fi ([91.154.115.217]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 09 Mar 2014 19:42:08 +0100 Received: from rakuco by a91-154-115-217.elisa-laajakaista.fi with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 09 Mar 2014 19:42:08 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-ports@freebsd.org From: Raphael Kubo da Costa Subject: Re: Anyone having problems with CMake 2.8.12.1_3 and ftp/curl? Date: Sun, 09 Mar 2014 20:41:55 +0200 Lines: 10 Message-ID: <86lhwjdxjg.fsf@orwell.Elisa> References: <86eh2bfsvg.fsf@orwell.Elisa> <8661nnfpgc.fsf@orwell.Elisa> Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: a91-154-115-217.elisa-laajakaista.fi User-Agent: Gnus/5.13001 (Ma Gnus v0.10) Emacs/24.3 (berkeley-unix) Cancel-Lock: sha1:mp/xzEiqWjLyG7xrUMF79oUlT6E= X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Mar 2014 18:42:11 -0000 Raphael Kubo da Costa writes: > Raphael Kubo da Costa writes: > >> Has anyone else experienced the same issue? > > I've finally managed to reproduce the issue locally by installing > security/openssl. Thanks everyone, this should be fixed by r347674.