From owner-freebsd-ports@FreeBSD.ORG Thu Apr 8 15:19:28 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5925616A4D0 for ; Thu, 8 Apr 2004 15:19:28 -0700 (PDT) Received: from seven.Alameda.net (seven.alameda.net [64.81.53.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D65243D39 for ; Thu, 8 Apr 2004 15:19:28 -0700 (PDT) (envelope-from ulf@Alameda.net) Received: by seven.Alameda.net (Postfix, from userid 1000) id E02AC3A201; Thu, 8 Apr 2004 15:19:27 -0700 (PDT) Date: Thu, 8 Apr 2004 15:19:27 -0700 From: Ulf Zimmermann To: ports@freebsd.org Message-ID: <20040408221927.GT89845@seven.alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 4.8-RELEASE-p5 Subject: Problems with 5.2.1-REL, ports and openssl X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ulf@Alameda.net List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Apr 2004 22:19:28 -0000 Hello, I have seen now a few times this problem and wonder whats going on. Right now I got two machines, installed with 5.2.1-RELENG, ports cvsup'ed early enough today to get for example 1.13 of bsd.openssl.mk and the other one later to have gotten bsd.openssl.mk version 1.15. But I am not sure if bsd.openssl.mk itself is the culprit, as I had another machine in the last 1-2 weeks which had the same problem and judging by the dates, it would have been bsd.openssl.mk 1.13 too. Now here is the problem itself: Machine one, bsd.openssl.mk I try to compile bind9 from ports. It finds (correctly) libcrypto.3 (in /usr/lib). Machine two, bsd.openssl.mk I try to compile bind9 from ports. It finds no /usr/local/lib/libcrypto.3 (which is correct, but it shouldn't have looked for libcrypto.3 in /usr/local/lib). /etc/make.conf has nothing set about openssl. on the other machine I had issues I fixed it by defining OPENSSLBASE in /etc/make.conf (I think it was OPENSSLBASE). Anyone have an idea whats going on that bsd.openssl.mk thinks it should be not be using the base openssl ? -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 You can find my resume at: http://seven.Alameda.net/~ulf/resume.html