From owner-freebsd-ports@FreeBSD.ORG Sun Oct 5 22:56:18 2003 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 21CB816A4B3 for ; Sun, 5 Oct 2003 22:56:18 -0700 (PDT) Received: from cowbert.2y.net (d46h180.public.uconn.edu [137.99.46.180]) by mx1.FreeBSD.org (Postfix) with SMTP id A8FCE43FD7 for ; Sun, 5 Oct 2003 22:56:16 -0700 (PDT) (envelope-from sirmoo@cowbert.2y.net) Received: (qmail 7054 invoked by uid 1001); 6 Oct 2003 05:56:15 -0000 Date: Mon, 6 Oct 2003 01:56:15 -0400 From: "Peter C. Lai" To: freebsd-ports@freebsd.org Message-ID: <20031006055615.GA6660@cowbert.2y.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: mod_php4-4.3.4.r1,1 broken with OpenSSL 0.9.7a X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: peter.lai@uconn.edu List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Oct 2003 05:56:18 -0000 the libphp4.so resulting from a port build of mod_php4-4.3.3.r1,1 will fail to load when openssl >= 0.9.7 is being dynamically linked to as it will either result in unkresolved symbol pointing to the new macro OpenSSL_add_all_algorithms_noconf() (this is with -with-openssl enabled) or complain about the unresolved symbol to an EVP macro (no openssl config specified; still needs openssl for the other hashing algorithms however). THere are numerous reports of this problem on google. I fixed it by importing openssl 0.9.6[a-z] from another box; but that's hardly a fix. It's obviously an issue with the PHP folks but it would be nice to notify the port maintainer also). -- Peter C. Lai University of Connecticut Dept. of Molecular and Cell Biology Yale University School of Medicine SenseLab | Research Assistant http://cowbert.2y.net/