From owner-freebsd-ports@FreeBSD.ORG Fri Feb 14 20:03:48 2014 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 69D1135B for ; Fri, 14 Feb 2014 20:03:48 +0000 (UTC) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 55F3B1157 for ; Fri, 14 Feb 2014 20:03:48 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id s1EK3lKM018910 for ; Fri, 14 Feb 2014 12:03:47 -0800 (PST) (envelope-from yuri@rawbw.com) Message-ID: <52FE76A3.8020607@rawbw.com> Date: Fri, 14 Feb 2014 12:03:47 -0800 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "ports@FreeBSD.org" Subject: Conflicts between libcrypto.so.8 from port vs. libcrypto.so.6 from the base Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Fri, 14 Feb 2014 20:03:48 -0000 While tracking down the crash in libssl on 9.2, I found that it was due to this conflict. First problem is that curl that I build always links with libcrypto.so.8 installed by openssl-1.0.1_9, and curl coming from the repository comes built with libcrypto.so.6 from the base system. There is also the warning during curl build: /usr/bin/ld: warning: libcrypto.so.6, needed by /usr/lib/libheimntlm.so, may conflict with libcrypto.so.8 openssl is installed because a bunch of other ports depend on it. So one problem is this ftp/curl build volatility (it links to libcrypto.so.8, when security/openssl is installed even though it doesn't depend on it). The second problem is that the program that depends on two ports, one of which is built with security/openssl, and another one depends on the base openssl, will always crash due to this conflict. And some packages are built with USE_OPENSSL and some aren't. Shouldn't every port that needs libcrypto/libssl always depend on security/openssl to avoid such problems? Yuri